Previous Topic: Virtual Terminal Setup

Next Topic: Identifying Application Screens

Sign On Page Setup

Certain special processing occurs within the Web Option runtime when the sign on screen is displayed. Therefore, it is important that Web Option is able to correctly recognize the sign on screen when it appears.

As shipped, Web Option includes an HTML skeleton that matches the default IBM Sign On screen:

Sign On System . . . . . : SYSTEM01 Subsystem . . . . : QINTER Display . . . . . : QPADEV0001 User . . . . . . . . . . . . . . ___________________ Password . . . . . . . . . . . . ___________________ Program/procedure . . . . . . . . ___________________ Menu . . . . . . . . . . . . . . ___________________ Current library . . . . . . . . . ___________________ (C) COPYRIGHT IBM CORP. 1980, 2007.

Web Option recognizes this screen because of the 7-character string on row 1, column 36 with a value of Sign On. If you modified your IBM Sign On screen, you need to modify the screen cross-reference file or the shipped YSIGNON skeleton to ensure that Web Option correctly recognizes it.

If your IBM Sign On screen does not include the text Sign On text at row 1, column 36, perform the following steps:

To update your Sign On text

  1. Determine an alternate piece of text on your screen that uniquely identifies it.

    For example, in the following sign on screen, the 13-byte string One C A Plaza at row 2, column 34 could be used:

    System: SYSTEM01 One C A Plaza Subsystem: QINTER Islandia, New York 11749 Display: QPADEV0001 ccccccccc aaaaaaaaaaa cccccccccccccc aaaaaaaaaaaaaaaa ccccccccccccccccc aaaaaaaaaaaaaaaaa User . . . . . . . ___________ cccccccccccccccccccc aaaaaaaaaaaaaaaaa Password . . . . . ___________ ccccccc ccccccc aa aaaaaaaaa Program/Procedure . ___________ ccccccc cccccc a aaaaaaaa Menu . . . . . . . ___________ ccccccc aaaaaaaa Current library . . ___________ ccccccc aaaaaaaa ccccccc aaaaaaaaaa ccccccc aaaaaaaaaaaaaaa ccccccc aaaaaaaaa aaaa ccccccc aaaaaaaa aaaaa ccccccc c aaaaaaa aaaaaa ccccccc ccc aaaaaa aaaaaaa cccccccccccccccc aaaaaa aaaaaaaaa cccccccccccccccc aaaaaaaaaaaaaaaaaaaaa cccccccccccccc aaaaaaaaaa aaaaaaa cccccccccc aaaaaaa aaaaaaa (C) COPYRIGHT IBM CORP. 1980, 2007.

  2. Use the YCVTRCO (Convert between row/col/offset) command in Y2WEBVENG to convert the row/column of the identifying text into an offset value:
    YCVTRCO ROWCOL(02 034)
    

    In this case, YCVTRCO returns a value of 0114.

  3. Use the YWRKF (Work with Database File) command to edit the YSCRXRFP Screen cross-reference file in Y2WEBVENG:
    YWRKF FILE(Y2WEBVENG/YSCRXRFP)
    
  4. Change the record which has a SID value of SYS0000001 so that the Screen ID offset (SIDOFF), Screen ID data (SIDDATA) and Screen ID length (SIDLEN) fields match the new screen identification data:
    Screen ID offset: 0114
    Screen ID data: One C A Plaza
    Screen ID length: 13
    

Note: On the default signon screen, the USERID and PASSWRD fields are at row 6, column 53 (offset 0453) and row 7, column 53 (offset 0533) respectively. If your changed signon screen has these fields at different positions, you must modify the YSIGNON skeleton to match these new positions.

To modify the skeleton

  1. Determine the correct row/column to use for the two fields. To do this, from a green screen session, place your cursor in the first position of each field and note the row/column numbers displayed in the bottom right corner of the display.
  2. Use the YCVTRCO command to convert the row/column values for the USERID and PASSWRD fields on your changed signon screen to offset values.
  3. Use WRKMBRPDM on YMLSSRC in Y2WEB to modify the member YSIGNON (an HTML skeleton for the Sign On screen). Find the source lines for the following html:
    <input type=”text” name=”_F0453U” size=”10” value=”(_v0453)”>
    <input type=”password” name=”_F0533U” size=”10”>
    
  4. Modify the 2E tags, indicated in bold, to match the offsets of the USERID and PASSWRD fields.

Web Option Running Apache HTTP Server DBCS

In order for Web Option to function correctly with the Apache HTTP Server and DBCS, the following directive must be added at the top of the HTTP server instance configuration file:

CGIDbcsOptimization Off

Note: This server directive is not documented in the IBM documentation.

Non-English Web Option LDO libraries

If you are using a non-English Web Option LDO library, use the YWRKF command to display the contents of the record in YSCRXRFP where Screen ID (SID) is SYS0000013 and Sequence number (SEQ) is 2:

YWRKF FILE(Y2WEBVENG/YSCRXRFP)

The Screen ID data (SIDDATA) field must match the value of the CAE0103 message in the QCPFMSG message file. This record links the YAUTSBM skeleton to the Display Program Messages screen. The record also ensures this skeleton is displayed only when the message being displayed is a warning message about multiple users signing on using the same user profile. If it does not match, change the Screen ID data (SIDDATA) and Screen ID length (SIDLEN) fields to match the CAE0103 value.

CA 2E Model Changes

For any CA 2E models where you need to generate skeletons, change the model library list to include the Web Option environment library, Web Option LDO library, and Web Option product library using the YADDLLE (Add Library List Entry) command. Also, ensure all three libraries exist in the library list for the Job Description specified for the YCRTJOBD model value (normally this is the QBATCH job description in the model library):

YADDLLE LIB(Y2WEB) POSITION(*LAST) LIBLST(MYMDL) UPDJOBD(*YES)
YADDLLE LIB(Y2WEBVENG) POSITION(*BEFORE Y2WEB) LIBLST(MYMDL) UPDJOBD(*YES)
YADDLLE LIB(MYWEBENV) POSITION(*BEFORE Y2WEBVENG) LIBLST(MYMDL) UPDJOBD(*YES)
CHGJOBD JOBD(MYMDL/QBATCH)