Identifying Application Screens › Manually Identifying a Screen

Manually Identifying a Screen

If you cannot use the new *STD SCREEN HEADINGS(MLS) header/footer and cannot add the *SCREEN ID field to another header/footer that you use with your CA 2E display file functions, you must manually identify your CA 2E screens to Web Option before you can generate skeletons. You can also manually identify non-CA 2E screens and generate skeletons for them (if you have the source for the display file) or write your own skeleton by hand.

Manual identification requires selecting a piece of text that always appears on the screen each time the program is called, such as the screen title. Use the Work with Screen Cross-references (YWRKSCRXRF) command to manually identify this piece of text as the virtual SID and create an entry in the screen cross-reference file. Even though a SID is not actually generated into the source member, the generator can access the screen cross-reference file to determine whether this screen has been identified.

For example, if you have a CA 2E display file that does not contain the *SCREEN ID field, perhaps because it was originally generated prior to you installing Web Option, and you do not wish to regenerate it, you must use the YWRKSCRXRF command to create the screen cross-reference record before you generate the HTML skeleton using the YGENMLS command. The HTML generator automatically uses the cross-reference record you have just created to determine the name of the skeleton to generate.

Alternatively, you may have an IBM menu screen that you want to display in the browser. Even though the menu does not have a DDS source member, you can still create a SID to identify the menu, then manually create your own HTML skeleton for it (using an HTML editing tool).

The YWRKSCRXRF command allows you to create both a record in the screen cross-reference file YSCRXRFP and a record in the Markup Language skeleton cross-reference file YMLSXRFP. The screen cross-reference file holds data that links an identified screen with its SID. The markup language cross-reference holds data that links a SID with a generated skeleton name.