Category: LANSA

The LANSA template language is a simple “tag” language that relies on branch type logic. It is not a sophisticated programming language. All commands conform to the normal LANSA command conventions. For instance, positional or keyword parameter specification can be used, lists must be enclosed in brackets, etc. The template language is not compiled. It is an interpretive language.

Note: In the lists below, ‘*’ indicates user input requested.

List Commands

@@CLR_LST	Clear/define a work list
@@MAK_LSTS	Make a list of selected fields from another list(s)*
@@MRG_LSTS	Merge a list(s) with another list(s)

File Commands

@@GET_FILS	Get the files to be used in this template*
@@RTV_FLDS	Retrieve the fields in a file
@@RTV_KEYS	Retrieve the keys of a file
@@RTV_RELN	Retrieve the relationship between two files

Control Command

@@GOTO	Pass control to a label
@@IF	Test a condition and pass control to a label
@@LABEL	A label which is the subject of another command
@@CMP_IDX	Compare an index value
@@DEC_IDX	Decrement an index value
@@INC_IDX	Increment an index value
@@SET_IDX	Set an index value

Other Commands

@@COMMENT	Add a comment line to the generated RDML code
@@QUESTION	Ask a question and receive a reply*

 

FUNCTION OPTIONS(*DIRECT)
*
DEFINE FIELD(#W_SERVICE) TYPE(*CHAR) LENGTH(30)
DEFINE FIELD(#W_STS) TYPE(*CHAR) LENGTH(20)
DEFINE FIELD(#W_MSG) TYPE(*CHAR) LENGTH(80)
DEF_LIST NAME(#LICENSE) FIELDS(#W_SERVICE) TYPE(*WORKING)
DEF_LIST NAME(#DLICENSE) FIELDS(#W_SERVICE #W_STS #W_MSG)
*
CLR_LIST NAMED(#LICENSE)
CLR_LIST NAMED(#DLICENSE)
*
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘XMLCLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘FTPCLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘POPCLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘SMTPCLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘HTTPCLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘HTTPIXMLCLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘HTTPOXMLCLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘HTTPIEDICLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘HTTPOEDICLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘HTTPISVCLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘SQLCLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘MQCLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘CECLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘FILECLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘SVFILECLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘EDICLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘RFICLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘SOAPCLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘AS2CERT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘AS2SERVER’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘AS2CLIENT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘AS2RECEIPT’)
EXECUTE SUBROUTINE(ADD) WITH_PARMS(‘UCCNETCLIENT’)
*
*
* DEFINE FIELD(#JSMSTS) TYPE(*CHAR) LENGTH(20)
* DEFINE FIELD(#JSMMSG) TYPE(*CHAR) LENGTH(255)
* DEFINE FIELD(#JSMCMD) TYPE(*CHAR) LENGTH(255)
* INPUT_ATR(LC)
*
* Load and Each Service
*
SELECTLIST NAMED(#LICENSE)
EXECUTE SUBROUTINE(TEST) WITH_PARMS(#W_SERVICE)
ENDSELECT
*
* Close
*
DISPLAY BROWSELIST(#DLICENSE)
RETURN
*
* Build Service List
SUBROUTINE NAME(ADD) PARMS(#W_SERVICE)
ADD_ENTRY TO_LIST(#LICENSE)
ENDROUTINE
* Test Each Service
SUBROUTINE NAME(TEST) PARMS(#W_SERVICE)
*
USE BUILTIN(JSM_OPEN) TO_GET(#JSMSTS #JSMMSG)
*
USE BUILTIN(TCONCAT) WITH_ARGS(‘SERVICE_LOAD SERVICE(‘ #W_SERVICE ‘)’) TO_GET(#JSMCMD)
USE BUILTIN(JSM_COMMAND) WITH_ARGS(#JSMCMD) TO_GET(#JSMSTS #JSMMSG)
CHANGE FIELD(#W_STS) TO(#JSMSTS)
CHANGE FIELD(#W_MSG) TO(#JSMMSG)
ADD_ENTRY TO_LIST(#DLICENSE)
USE BUILTIN(JSM_COMMAND) WITH_ARGS(‘SERVICE_UNLOAD’) TO_GET(#JSMSTS #JSMMSG)
*
USE BUILTIN(JSM_CLOSE) TO_GET(#JSMSTS #JSMMSG)
*
ENDROUTINE

Cart	See Shopping Cart.
Confirmed Order	Once a Shopping Cart has been checked out, the cart becomes a Confirmed Order with an assigned Order Number. Do not confuse Confirmed Orders with Saved Cart (sometimes called a Saved Order) or Pending Carts (sometimes called Pending Orders).
Check Out	Check Out is the process by which a Shopping Cart is converted to a Confirmed Order.
Customer	A Customer is someone who is placing an Order for your Products. Customers must have a valid Web user profile to access the System.
Customer Account	The B2C Customer Account information includes the contact, billing and shipping details. For B2B Customer Accounts, only the Contact information is stored in the Commerce Edition database. The remaining B2B information comes from the back-end files.
Order	The term “Order” can be used in a number of ways. To be specific, Commerce Edition creates Shopping Carts, Pending Carts and Confirmed Orders. When a Customer places an “Order”, the customer may be using any of these three specific types of Business Objects. Only Confirmed Orders will have any meaning to your existing application database.
Pending Cart	A Pending Cart (sometimes called a Pending Order) is a Shopping Cart which was not completed during a previous session by the Customer. If a Customer leaves the Web site with Products in the Shopping Cart (or if the Web site connection is lost), the Shopping Cart is automatically converted into a Pending Cart. When the Customer next logs onto your site, a list of Pending Carts is displayed. The user may select one of these Pending Carts or the user can save or delete these Pending Carts.
Personal Catalog	A Personal Catalog is a subset of the Product Catalog. It is a Customer specific list of Products which are frequently ordered. The Customer can add or delete products in their own Personal Catalog. This catalog is maintained as a file in the Commerce Edition database.
Product	A Product is any item which the Customer orders. Products are based on your existing back-end Product file(s).
Product Catalog	The Product Catalog is a listing of the Products which a customer may order. The Product Catalog is based on your existing back-end Product files. There is no separate Product Catalog file in the Commerce Edition database.
Promotion	A Promotion is a special offer which is advertised on the Web site. Promotions are simply text. There is no processing logic associated with a promotion.
Saved Cart	A Saved Cart (sometimes called a Saved Order), is simply a saved list of products. A Shopping Cart can be saved so that the Products may be easily reordered. Saved Carts can be added to the active Shopping Cart.
Session ID	A Session ID (sometimes called a Web Session ID), is a unique number assigned when a Web user logs on to the system and creates a Shopping Cart. A Session ID is assigned to a Shopping Cart and is stored as part of the definition of a Pending Cart. After a Shopping Cart is checked out, a new Session ID is assigned for the new Shopping Cart.
Ship-To Address	The Ship-To address is the location where the Products will be delivered. For B2C Customers, the Ship-To information is stored in the Commerce Edition database. For B2B Customers, the Ship-To information is stored in the back-end files.
Shopping Cart	A Shopping Cart is simply a list of products which the Customer may wish to purchase. Each Shopping Cart is associated with a unique Session ID.
Up-Selling	The means by which suggested or accessorial products are listed when browsing the Product Catalog, the Personal Catalog or the Shopping Cart.
Web User	A Web user is any Customer who has logged on to the system. Each Web user has an unique user profile/ID and password. For B2C, a Customer and Web user are the same, as each Customer has just one Web user profile. For B2B, a single Web user profile can be associated to more than one Customer account. Your system administrator can create associations between Web users and your B2B Customer accounts. (Note: A Customer Account can have only one Web user associated with it, but a Web user can be associated with more than one Customer Account.)

There are many industry definitions for Business-to-Business (B2B) and Business-to-Consumer (B2C) applications. To develop your application with Commerce Edition, you must understand a basic distinction between B2B and B2C from a Commerce Edition application business model perspective.

Both B2B and B2C applications allow Customers to place Orders for Products. The main difference between B2B and B2C is the definition of the Customer.

In a B2B application, a Customer is a predefined Business Partner. You have a predefined business relationship with the Customer before they access your e-business application. Your existing applications will already contain data for this Customer. You will probably set up the Web user accounts for the Business Partner in advance. Customer Numbers are already defined and can be validated against your existing database.

In a B2C application, a Customer is any Web user or the general public consumer. You do not know anything about the Customer until they place their first order. The Customer must register or set up their own account in order to place orders. You have no information for the Customer in your existing database. A Customer may register to place only one order.

This distinction will help you understand the Commerce Edition data model and basic rules for validation and processing. The Commerce Edition database has been designed to support both B2B and B2C applications. If you are implementing only a B2C application, you may not require some files and fields created specifically for B2B applications. If you are implementing only a B2B application, you may not require some files and fields created specifically for B2C applications.

The Commerce Edition database will also support a combined B2B and B2C application. A combined application allows you to create one Web site, which allows your existing Customers (B2B) and new Web users (B2C) to order products. Depending on whether the Customer is B2B or B2C, Commerce Edition will perform the appropriate processing logic and will use the appropriate database files.

The LANSA for the Web Commerce Edition is a set of tools, which enables LANSA for the Web developers to rapidly deploy Business-to-Consumer (B2C) and Business-to-Business (B2B) applications that integrate with existing back-end or legacy systems. Commerce Edition provides an application framework which extends the power of LANSA for the Web specifically for B2C and B2B development.

Commerce Edition includes a customizable application database for your B2B and B2C applications. Using Business Objects, you create the framework for your application. Without any manual coding by your developers, Commerce Edition can deliver anywhere from 60% to 85% of your finished application.

Commerce Edition uses the LANSA for the Web e-Business Framework Wizard, which allows you to quickly and easily customize the presentation of your LANSA Web application. The Wizard is not used to create your LANSA functions. It is used to alter their appearance, by using Web-based functions executing from your browser. The Wizard removes the need to manually define graphical variables and Web components. You can change the user navigation within your application and you can change the look-and-feel of your applications without having to recompile any of the functions in your application.

LANSA for the Web allows you to build Web applications quickly and easily. It is a toolkit that integrates seamlessly with the LANSA Integrated Development Environment (either Visual LANSA or LANSA for the iSeries). You can use graphical HTML forms or XML based applications using the same Repository and RDML skill set used to build your iSeries and Windows applications. In fact, a LANSA program can be deployed to the iSeries, Windows or the Web using a single RDML program definition.LANSA for the Web allows you to build dynamic data retrieval applications for the Web. It also allows you to deploy the applications across a number of combinations of platforms including the iSeries and Windows NT. Each of these platforms can be used as the Application/Data Server or the Web Server. In other words, you can choose to deploy your applications in a multi-tiered architecture.LANSA for the Web incorporates a Transaction Server, which provides your user sessions with a persistent connection between their browser and your Data Server. Persistent connections are not available in the HyperText Transfer Protocol (HTTP), the protocol used in serving the Web.LANSA for the Web shields you from the technologies you have to learn to deploy Web-enabled applications. You do not need to have a thorough knowledge of CGI or Java Servlet programming, HTML or JavaScript or XML. You do not need to learn code-intensive HTML or CGI to build dynamic Web applications. All you have to do is use LANSA’s repository-based 4GL environment to build your application definition. LANSA will automatically generate the HTML or XML pages for you. LANSA for the Web allows the developer to work at the 4GL level, without the need for any skills in HTML, CGI or any other Internet programming interfaces. LANSA for the Web hides the complexity of HTML/XML and CGI programming from you.There is no client side code to develop or maintain with LANSA for the Web. You do not have to be concerned about the operating systems of the client. All the client machines require is a browser that is capable of supporting the HTML generated by LANSA for the Web. Once you have indicated that you want your LANSA application Web-enabled, LANSA will automatically take care of the effort to Web-enable the application for you.The huge growth and demand for Internet access to businesses has prompted LANSA to extend its offering beyond the traditional application development environment. LANSA now offers a set of application specific frameworks to help companies deploy their e-business solutions at an even more astounding rate. The LANSA e-Business Framework Wizard and Commerce Edition are part of the natural evolution of the LANSA product family. Along with LANSA’s powerful application development environment, Web developers will benefit from Commerce Edition (which includes the Database Adaptor and Business Objects) and the e-Business Framework Wizard to help accelerate Business-to-Consumer (B2C) and Business-to-Business (B2B) application development.

Mark Mason is looking for LANSA WorkLANSA is an integrated family of highly productive design, development and maintenance products for multi-platform host and network applications. This family of products provides an extremely flexible application development environment where a developer can use a single skill set to build and deploy applications for the iSeries, Windows or Internet environments.LANSA’s powerful Repository-based 4GL has enabled developers to quickly deploy applications across computing boundaries and across computing paradigms. A simple recompile can transform a host-centric iSeries application using RPG/ILE into a client/server Windows application using C/C++ or a browser-based, Internet application using HTML and Java servlets. Developer productivity and ease-of-use are LANSA trademarks. For years, developers have enjoyed the benefits of LANSA’s Rapid Development and Maintenance Language (RDML) which insulated them from low-level languages and platform complexities. RDML can build iSeries applications, graphic event-driven Windows applications and Web applications. The LANSA Active-Object Repository provides a centralized application definition and platform independent database architecture. This powerful combination has protected companies’ information technology investments for over 10 years.LANSA was the first iSeries development tool to fully embrace the Internet and Web technology. LANSA for the Web has allowed developers to construct Internet, Intranet and Extranet applications. Today, there are hundreds of thousands of people using LANSA Web-based applications in retail, health care, insurance, manufacturing, government, communications and in many other industry sectors.

Candidate must be willing to work and be responsible for entire project (start to finish).  Good problem analysis skills and smart.   We want someone who is looking for a career and not just a job.  We are a small company (13 people with only 4 in development).  Our current developers are RPG and we are looking for a quality person to come in and lead us in our rewrite in plums using the Lansa framework.

CAll 877 526 7220 or email resume to lansa@yahoo.com

FUNCTION OPTIONS(*DIRECT *WEBEVENT)
GROUP_BY NAME(#PRMTBLGRP) FIELDS(#MPRMCTG #MPRMCOD #MPRMDSC)
DEF_LIST NAME(#ARRAY_LST) FIELDS(#Z_DATA) COUNTER(#Z_COUNT) TYPE(*WORKING) ENTRYS(500)
DEF_LIST NAME(#X1BL01LST) FIELDS(#X1ALPLONG) ENTRYS(1000)

DEFINE FIELD(#ZZCOUNT) TYPE(*DEC) LENGTH(2) DECIMALS(2)
DEFINE FIELD(#ZZCOUNTC) TYPE(*CHAR) LENGTH(2)

DEFINE FIELD(#ZFNAMEMMM) TYPE(*CHAR) LENGTH(25)
DEFINE FIELD(#ZLNAMEMMM) TYPE(*CHAR) LENGTH(25)
DEFINE FIELD(#ZSSNUMMMM) TYPE(*CHAR) LENGTH(25)

* =======================================================
* Moving Respective HTML Pages to Components
* =======================================================

CHANGE FIELD(#DCTONLCMP) TO(*NULL)
CHANGE FIELD(#DCTHEDCMP) TO(PAG_RPARRHED)
CHANGE FIELD(#DCTHDRCMP) TO(*NULL)
CHANGE FIELD(#DCTLFTCMP) TO(*NULL)
CHANGE FIELD(#DCTPAGCMP) TO(PAG_RPARRAY)
* =======================================================
* Process according to Button clicked
* =======================================================

CASE OF_FIELD(#STDRENTRY)
WHEN VALUE_IS(‘*EQ N’)
* do logic here to validate if you want to
REQUEST FIELDS(#ZFNAMEMMM #ZLNAMEMMM) EXIT_KEY(*NO) MENU_KEY(*NO)
WHEN VALUE_IS(‘*EQ *BLANKS’)
CHANGE FIELD(#MPRMCTG) TO(PENDC)
CHANGE FIELD(#MPRMCOD) TO(”’RPARRAY1”’)
CLR_LIST NAMED(#ARRAY_LST)
CLR_LIST NAMED(#X1BL01LST)

SELECT FIELDS(#PRMTBLGRP) FROM_FILE(M@PRMTBL) WITH_KEY(#MPRMCTG #MPRMCOD) GENERIC(*YES)
EXECUTE SUBROUTINE(LISTENTRY) WITH_PARMS(#MPRMDSC)
ENDSELECT

* Build List for Javascript Array
CHANGE FIELD(#ZZCOUNT) TO(0)
SELECTLIST NAMED(#ARRAY_LST)
CHANGE FIELD(#X1ALPLONG) TO(#Z_DATA)
ADD_ENTRY TO_LIST(#X1BL01LST)
ENDSELECT
OTHERWISE
MESSAGE MSGTXT(‘STDRENTRY not Programmed for’)
ENDCASE

REQUEST FIELDS((#STDNEXT *HIDE) (#STDRENTRY *HIDE)) EXIT_KEY(*NO) MENU_KEY(*NO) PROMPT_KEY(*NO)
REQUEST BROWSELIST(#X1BL01LST) EXIT_KEY(*NO) MENU_KEY(*NO)

* =======================================================
* Subroutine ….: LISTENTRY
* Description….: Add Entries to List
* =======================================================
SUBROUTINE NAME(LISTENTRY) PARMS(#Z_DATA)
IF_NULL FIELD(#Z_DATA)
ELSE
ADD_ENTRY TO_LIST(#ARRAY_LST)
ENDIF
ENDROUTINE