gtpd2m0n | Data Communications Services Reference |
Sixteen FSCs are supported, each of which can be referenced by number (1-16) and/or name. Valid FSC names are maintained in the RTCEQ macro. Currently, 7 FSC names are supported: RO, PRC, TAPE, DASD, COMM, AUDT, and RDB. See Functional Support Consoles for further information. The user can customize this support to fit installation requirements by adding to the list of FSC names. If your system uses an automation gateway, new FSC names may be defined to support additional LAN function console types. To add to the list of FSC names:
The new FSC name is now available for use. Note that it is imperative that the new RTCDxxxx equate and the new &CHECQ value occupy the same relative positions.
Example:
To add a new FSC named SERR, update as follows:
Table 3. Update to Add a New FSC to RTCEQ
1. Add new equate | RTCDSERR | EQU | X'0200' |
2. Add new name | &CHECQ(7) | SETC | 'SERR' |
3. Update &NCODES | &NCODES | SETA | 23 |
4. Update &COUNTC | &COUNTC | SETA | 7 |
After reassembling and loading segments CVAH, CVAI, CVFO, CVH1, CVPF, CAPJ, CAPN, CAPP, and CVP1, the new FSC name is available for use. This means that RTCD-SERR and REST-SERR is accepted by the ZACRS command editor, and that ROUT=SERR is accepted on the WTOPC macro. Also, the new FSC can now be associated with commands through the use of ZFMSG with the SER keyword. Note that the same function can be accomplished by using the FSC number (7 in the above example) without any code change. That is, RTCD-7, REST-7, and ROUT=7 are legal values for these parameters.
The command editor tables are program and fixed file records that control the destination of command input and related output. The base definitions, for commands, are contained in program records and consist of the following segments:
The base definitions in the released code are generalized in nature. It is suggested that these definitions be studied carefully to ensure they are compatible with specific installation requirements. The tables may be modified when necessary via source update and program reassembly.
Additions and modifications to the base definitions can also be made dynamically during online operation via the ZFMSG command. These changes are maintained in a fixed file record and do not affect the base program records.
Of particular importance is the command input indicators and FSC output routing codes. The command input indicators define the message's processing characteristics. The user can modify these indicators but must be aware that modification may adversely affect the operation of the system. The FSC output routing codes indicate the FSC(s) to receive a copy of the input message and any associated output. The user can modify these routing codes in any way. For assistance in the initial definition of these tables, see Installation Information.
To modify the base definitions use the following procedure:
Example:
The existing entry for the ZACRS command in segment CVAB is coded as follows:
DC AL2(RTCDBSS+RTCDSSD) Input Indicators DC AL2(RTCDCOM+RTCDAUD) FSC Routing DC AL1(PAI_ENTDC) Activate by ENTDC DC AL1(0) Additional indicators DC C'ACRS' Secondary action code DC C'CVHZ' Name of program to enter
This entry specifies the following:
To change this entry to define the ZACRS command as a restricted message (RTCDRST), and to assign the PRC FSC routing code (RTCDPRC) to it, the entry should be coded as follows:
DC AL2(RTCDBSS+RTCDSSD+RTCDRST) Input Indicators DC AL2(RTCDCOM+RTCDAUD+RTCDPRC) FSC Routing DC AL1(PAI_ENTDC) Activate by ENTDC DC AL1(0) Additional indicators DC C'ACRS' Secondary action code DC C'CVHZ' Name of program to enter
The new entry takes effect after reassembling and loading segment CVAB. Since the message is now restricted, only terminals that are authorized to input PRC, COMM, and/or AUDT messages are permitted to input the ZACRS message.
The previously illustrated example can be accomplished online by entering the following command:
ZFMSG CHANGE ZACRS RST PRC