Generating HTML for Non-CA 2E Display Files › Identification Instructions › Extended example

Extended example

A*. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7
*#W2E#D001 CSTINQKEY     Customer inquiry key screen
*#W2E#F001 RCDFMT1     YY Key screen
*#W2E#I001 0031          Select customer
*
*#W2E#D002 CSTINQDTL1    Customer details screen
*#W2E#F002 SFLCTL1    NY Subfile control
*#W2E#I002 0032          Customer details
*#W2E#F002 SFLRCD1    NN Subfile record
*#W2E#F002 CMDKEYS    YN Command keys
*
*#W2E#D003 CSTINQDTL2    Customer address screen
*#W2E#F003 SFLCTL2    NY Subfile control
*#W2E#I003 0102          Customer address
*#W2E#F003 SFLRCD2    NN Subfile record
*#W2E#F003 CMDKEYS    YN Command keys
*

The above lines define to the HTML generator to generate the following skeletons:

1. A skeleton called CSTINQKEY, which contains a single record format (RCDFMT1). The generator creates a screen cross-reference record for the skeleton showing that the skeleton is uniquely identified by the text 'Select customer' at offset 31 and that it contains command key text on it, which should be parsed to determine the command key button names to generate.
2. A skeleton called CSTINQDTL1, which contains three record formats:
   • SFLCTL1 - the controlling record format and can uniquely be identified at runtime by the text 'Customer details' at offset 32
   • SFLRCD1
   • CMDKEYS - record format parsed by the HTML generator for command key text to place on the command key buttons
3. A skeleton called CSTINQDTL2, which contains three record formats
   • SFLCTL2 - the controlling record format and can uniquely be identified at runtime by the text 'Customer address' at offset 102
   • SFLRCD1
   • CMDKEYS - record format is parsed by the HTML generator for command key text to place on the command key buttons

Note that more than one skeleton can include the same record format (in the example above, the CMDKEYS record format is used in both the CSTINQDLT1 and CSTINQDTL2 skeletons).