gtps2m1cACF/SNA Data Communications Reference

Generating the Side Information Table for Mapped Conversations

The side information table offline program (CHQI) runs under MVS or CMS to generate either a tape or a general data set that can be loaded to a TPF system. The generated data set contains commands and data for modifying the side information table. Data from the side information table is retrieved whenever an application transaction program issues the mapped conversation initialize conversation (cminit) function.

Note:
Before generating the side information table, be sure that you have defined the #CMSIT fixed file records at system generation time. These are the 4K records used to hold the side information table.

Figure 53 shows the process for generating a side information table.

Figure 53. Generating the Side Information Table


The steps required for generating a side information table are as follows:

  1. On MVS or CMS, create an input file for CHQI.

    The input to CHQI is an EBCDIC file of fixed-length 80-byte records, consisting of statements that specify the function to be performed. You can also include comments and blank lines to improve readability. See Creating the Input File for details.

  2. On MVS or CMS, run CHQI against the input file.

    CHQI creates 2 output files:

    See Running CHQI and Side Information Table Offline Program Output for details.

  3. Use the listing file to correct any errors in the input file.
  4. Repeat steps 2 and 3 until there are no errors in the input file.
  5. Mount the tape or general data set on the TPF system.
  6. If the side information table is not initialized, issue the ZNSID INITIALIZE command.
    Note:
    Initializing the side information table erases any existing information in it.
  7. Load the side information data set to the TPF system using the ZNSID LOAD command.

    Steps 5, 6, and 7 are described in more detail in Loading the Side Information Data Set to TPF.

In the following discussion, the phrase side information table refers to the online side information table residing on TPF. The phrase side information data set refers to the data set that is generated offline by CHQI and contains the entries for the online side information table.

Creating the Input File

The following describes the basic steps for creating the input file for CHQI. Additional details on the syntax requirements for the statements are described in the following section, Statement Syntax.

  1. Create a file with a logical record length of 80 (LRECL=80) and a fixed record format (RECFM=FB).
  2. You can code comments (lines with an asterisk in column 1) and blank lines (containing only spaces) anywhere in the file.
  3. If the side information data set must be loaded to a specific subsystem, code:
    LOAD SS-subsystem

    where subsystem is the 1- to 4-character name of the subsystem on which the data is to be loaded. If you specify a subsystem, the side information data set must be loaded to that subsystem. If you do not code a LOAD statement, the side information data set can be loaded to any subsystem. After the side information data set is loaded, the symbolic destination names defined by that data set are available to transaction programs running in the specified subsystem. You can specify only 1 subsystem for a side information data set; that is, only 1 LOAD statement can be included in the input file. This statement, if included, must precede all other statements.

  4. If you want to display text on the TPF operator console while loading the side information data set, for each line of text to be displayed code:
    DESCR text

    where text is the line of text to be displayed. The text is displayed as a response to the ZNSID LOAD command.

  5. If you want to add an entry to the side information table, for each entry code:
    ADD NAME-sdn TP-tpn LU-lunMODE-mode

    where sdn is the symbolic destination name of the new entry, tpn is the corresponding remote transaction program name, lun is the corresponding partner LU name, and mode is the corresponding mode. If an entry with the identical symbolic destination name already exists in the side information table, it is changed by the entry in the side information data set. If 2 or more entries with the same symbolic destination name are included in the same side information data set, the entries are loaded in the order that they are specified in the input file. After the load is complete, the side information table entry for the duplicated symbolic destination name contains the data specified for the last entry loaded.

  6. If you want to remove entries from the side information table, for each entry to be removed code:
    REMOVE NAME-sdn

    where sdn is the symbolic destination name of the entry to be removed. If no entry with the specified symbolic destination name exists in the table, the entry in the side information data set is ignored.

Statement Syntax

The CHQI input syntax consists of the following elements:

Comments
Any record beginning with an asterisk in column 1 is a comment. The text in columns 2-80 is not parsed. You can code a comment line anywhere in the file.

Verbs
Each statement begins with a verb, and each type of statement requires a different set of parameters following the verb. There are no abbreviations for the verbs; you must code each 1 in full. CHQI recognizes 4 verb statements: LOAD, DESCR, ADD, and REMOVE.

Parameters
The DESCR verb takes a positional parameter (the text that follows it); the other verbs all take keyword parameters. Keyword parameters consist of the keyword, followed immediately by either a single dash or by a single equal sign, followed by the value. There can be 1 or more spaces between the dash or equal sign and the value, as long as the value is in the same record as the keyword. There must not be any spaces between the keyword and the dash or equal sign.

The input file is free format in that you do not have to code verbs and parameters on a particular line or in a particular column. Blank lines can be inserted at any point to improve readability. Exceptions to this free format include the following:

CHQI's parser scans the input file, strips out comments, and parses the remaining text into tokens. A token is any string of characters that is delimited by a space, null character, comma3, dash, equal sign, or logical end of record and that does not contain a space, null character, dash, equal sign or logical end of record4.

Tokens are classified as verbs, parameter keywords, and parameter values. Each verb begins a new statement, and each statement consists of the verb that initiates it and any following parameters up to the next verb or the end of file. The statements are checked for errors. Any statement containing no error messages or only attention messages is written to the side information data set in the proper format to be read by the TPF side information data loader. Statements containing 1 or more errors are not written to the side information data set.

The following shows the format of the statements and describes the verbs and parameters.

LOAD SS-subsystem

LOAD
Must be the first statement in the file, if used. If the LOAD statement occurs following any other statement, the LOAD statement is flagged with an error. The LOAD statement requires the SS parameter; if SS is omitted, the LOAD statement is flagged with an error.

SS-subsystem
Specifies the subsystem on which the generated side information data must be loaded. SS can be abbreviated to S.

The SS parameter value is any string from 1 to 4 characters long. The subsystem name is copied to the header of the first record in the side information data set.

DESCR text

DESCR
Can be coded anywhere except before a LOAD statement.

text
Represents a positional parameter that consists of the text between the DESCR verb and the next logical end of record, stripped of any leading or trailing blanks. There are no restrictions on the characters or strings that you can use, assuming the characters you use can be handled by your console.

ADD NAME-sdn TP-tpn LU-lun MODE-mode

ADD
Can be coded anywhere except before a LOAD statement. Each ADD statement takes 4 keyword parameters: NAME, TP, LU, and MODE. You can code these parameters in any order. If the NAME parameter is omitted, the statement is flagged with an error. If the TP, LU, or MODE parameter is omitted, the statement is flagged as requiring attention and the corresponding field in the side information entry is set to a null value.
Note:
Transaction programs referring to an entry containing a null field must set valid values for the mode_name, mode_name_length, partner_LU_name, partner_LU_name_length, TP_name, and TP_name_length conversation characteristics before successfully allocating a conversation. See the cmsmn, cmspln, and cmstpn functions in the TPF C/C++ Language Support User's Guide for additional information.

If any of these parameters is repeated in a single ADD statement, it is flagged as an error. (Successive TP parameters, which are concatenated, are treated as a single instance of the TP parameter.)

NAME-sdn
Specifies the symbolic destination name of the new side information table entry. NAME can be abbreviated to NAM, NA, or N.

The NAME parameter value is any string from 1- to 8-characters long, consisting of any characters except token delimiters (dash, equal sign, comma, or blank) and lowercase letters. The symbolic name written to the side information data set is an 8-byte field consisting of the NAME parameter value padded to the right with space characters.

TP-tpn
Specifies the remote transaction program name associated with the symbolic destination name. TP can be abbreviated to T.

SNA allows transaction program names to include unprintable characters. To allow entry of such names, the TP parameter value can include substrings that are translated to unprintable characters in the output side information entry. The generated transaction program name is a variable-length field from 1 to 64 bytes long with no padding.

The dollar sign ($, X'5B') is used to delimit substrings of TP parameter values that are to be interpreted as hexadecimal values, according to the following rules:

To accommodate the possibility of a TP parameter value being too long to fit into 1 80-byte record, the values of adjacent TP parameters are concatenated. Each of the parameter values must conform to the rules stated previously, and the total length of all the concatenated converted strings must be less than or equal to 64. No other parameters can be coded between 2 concatenated TP parameters.

Note:
N1 of the other keyword parameters are concatenated in this way.

The following example shows adjacent TP parameters that are concatenated to produce 1 transaction program name value for the generated entry:

   **************************************************
   * ADD STATEMENT WITH CONCATENATED TP PARAMETERS. *
   * THE GENERATED TRANSACTION PROGRAM NAME IS:     *
   *     HEX    : C2C5C7C9 D5010203 5BC5D5C4        *
   *     EBCDIC : B E G I  N . . .  $ E N D         *
   **************************************************
   ADD    N-CONCAT
          T-BEGIN
          T-$010203$
          T-$$
          T-END
          ...

LU-lun
Specifies the partner LU name associated with a symbolic destination name. LU can be abbreviated to L.

The LU parameter value is a string from 1 to 17 characters long, consisting of an LU name and an optional network ID. If the network ID is included, it must precede the LU name and be separated from it with a period. If you only include the LU name, a period is not required.5 Both the network ID and the LU name must be from 1 to 8 characters long, must contain only capital letters (A-Z) and numeric digits (0-9), and must begin with a capital letter. Any LU parameter that does not satisfy these requirements is flagged as an error. The following are examples of valid LU parameter values:

    NETID.LUNAME
    LUNMONLY
    N112358D.L1234567
    N.L
    LU62MAPD

The partner LU name field written to the side information data set is a variable-length field from 1 to 17 bytes long. The LU parameter value is copied to it without conversion or padding.

MODE-mode
Specifies the mode associated with a symbolic destination name. MODE can be abbreviated to MOD, MO, or M.

The MODE parameter value is a string from 1 to 8 characters long. It must contain only capital letters (A-Z) and numeric digits (0-9), and must begin with a capital letter. Any MODE parameter value that does not satisfy these requirements is flagged as an error. The mode field written to the side information data set is a variable-length field from 1 to 8 bytes long. The MODE parameter value is copied to it without conversion or padding.

REMOVE NAME-sdn

REMOVE
Can be coded anywhere except before a LOAD statement. Each REMOVE statement requires the NAME parameter. If the NAME parameter is omitted or repeated in the REMOVE statement, the statement is flagged with an error. The TP, LU, and MODE parameters are not required for this statement. Each occurrence of 1 of these parameters is flagged as requiring attention, and the parameter value is ignored.

NAME-sdn
Specifies the symbolic destination name of the side information table entry to be removed. Refer to the ADD statement parameter description for additional information about this parameter.

CHQI Input File Example

Figure 54 shows an example of a CHQI input file.

Figure 54. Example of an Input File for CHQI


********************************************************************************
* THIS CHQI INPUT FILE GENERATES A TPF-LOADABLE SIDE INFORMATION DATA SET THAT *
* REMOVES SOME OBSOLETE SIDE INFORMATION TABLE ENTRIES AND ADDS SOME NEW 1S. *
********************************************************************************
 
LOAD S-BSS
 
********************************************************************************
* IF CODED, THE LOAD STATEMENT MUST BE THE FIRST STATEMENT IN THE INPUT FILE.  *
* COMMENTS AND BLANK LINES CAN PRECEDE THE LOAD STATEMENT.                     *
********************************************************************************
 
DESCR  ==============================================
DESCR  = REVISIONS TO SIDE INFORMATION TABLE        =
DESCR  = CREATED 01/30/91                           =
DESCR  ==============================================
 
**********************************************************
* THE FOLLOWING ENTRIES ARE OBSOLETE AND WILL BE REMOVED *
**********************************************************
REMOVE N-OBSDEST1
REMOVE N-OBSDEST2
REMOVE N-OBSDEST3
 
 
DESCR  ==============================================
DESCR  = OBSOLETE ENTRIES HAVE BEEN DELETED         =
DESCR  ==============================================
 
*******************************************
* THE FOLLOWING NEW ENTRIES WILL BE ADDED *
*******************************************
ADD    N-NEWDEST1   T-TPNAME1   L-SNANET.LU62MAP1   M-MODE1
ADD    N-NEWDEST2   T-TPNAME2   L-SNANET.LU62MAP2   M-MODE2
ADD    N-NEWDEST3   T-TPNAME3   L-SNANET.LU62MAP3   M-MODE3
 
 
DESCR  ==============================================
DESCR  = NEW ENTRIES HAVE BEEN ADDED                =
DESCR  ==============================================

Figure 55 shows how the TPF operator console looks after loading the side information data set generated from Figure 54.

Figure 55. TPF Console Display. This shows the result of loading the side information data set generated using the input in Figure 54.

+--------------------------------------------------------------------------------+
|NSID0017I 01:23:45 USER TEXT FROM SIDE INFORMATION GDS                          |
|==============================================                                  |
|= REVISIONS TO SIDE INFORMATION TABLE        =                                  |
|= CREATED 01/30/91                           =                                  |
|==============================================                                  |
|--- END OF DESCRIPTION ---                                                      |
|                                                                                |
|NSID0017I 01:23:45 USER TEXT FROM SIDE INFORMATION GDS                          |
|==============================================                                  |
|= OBSOLETE ENTRIES HAVE BEEN DELETED         =                                  |
|==============================================                                  |
|--- END OF DESCRIPTION ---                                                      |
|                                                                                |
|NSID0017I 01:23:46 USER TEXT FROM SIDE INFORMATION GDS                          |
|==============================================                                  |
|= NEW ENTRIES HAVE BEEN ADDED                =                                  |
|==============================================                                  |
|--- END OF DESCRIPTION ---                                                      |
|                                                                                |
|NSID0005I 01.23.46 NEW SIDE INFORMATION TABLE ENTRIES LOADED                    |
|ENTRIES PROCESSED  - 6                                                          |
|ENTRIES ADDED      - 3                                                          |
|ENTRIES CHANGED    - 0                                                          |
|ENTRIES REMOVED    - 3                                                          |
|ERRORS DURING LOAD - 0                                                          |
|                                                                                |
+--------------------------------------------------------------------------------+

CHQI Input Statements and ZNSID Commands

The syntax of the CHQI input file is similar to the syntax of the ZNSID command. The main differences between CHQI input statements and ZNSID commands are as follows:

Running CHQI

CHQI consists of a single CSECT that can be assembled, link-edited, and run under either MVS or CMS. There are no runtime parameters for CHQI, but you must define the following 3 data sets:

Input file
Is the file discussed previously in Creating the Input File. The DD name for this file must be CHQIIN.

Side information data set
Is the standard labeled tape or general data set created by CHQI, which can be loaded online by TPF. The DD name for this file must be SIDOUT.
Note:
If you are writing the data set to tape be sure to include IBM standard labels. For MVS, code the LABEL = (,SL) parameter on the SIDOUT DD card. For CMS, include the SL parameter on the FILEDEF SIDOUT command.

The side information data set is described further in Side Information Data Set.

The output listing
is a printable file containing ANSI printer control characters. It includes a listing of the input file with attention messages and errors flagged, and a summary of the processing. The DD name for this file must be CHQILIST.

The contents of the output listing is described in CHQI Output Listing.

The following is a list of the possible return codes from CHQI.

Code
Meaning

0
Processing completed normally; no error messages or attention messages are found.

4
Processing completed; attention messages were found, but no error messages.

8
Processing completed; errors were found.

12
CHQI was not able to open the input file.

16
CHQI was not able to open the output side information data set.

20
CHQI was not able to open the output listing file.

Sample JCL for CHQI

The following is a sample of the JCL to create a tape under MVS:

   //* Your JOB card here
   //**************************
   //* Execute CHQI           *
   //**************************
   //CHQIRUN  EXEC  PGM=CHQI41
   //STEPLIB  DD    DSN=TPF.BASE.RLSE.LK,DISP=SHR
   //SYSUDUMP DD    SYSOUT=*
   //CHQIIN   DD    DSN=TPF.BASE.SIDINPUT(NEWSID),DISP=SHR
   //CHQILIST DD    SYSOUT=*
   //SIDOUT   DD    UNIT=(TAPE,,DEFER),DISP=(NEW,KEEP),LABEL=(,SL),
   //         DSN=SIDTAPE,VOL=SER=xxxxx
   /*
Note:
Modify the data set names and volume serial number as appropriate.

The following is a sample of the commands to create a tape under CMS:

  FILEDEF CHQIIN DISK SIDTAPE INPUT A
  FILEDEF CHQILIST DISK SID LISTING A
  FILEDEF SIDOUT TAP SL
  CHQI
Note:
Modify the file names as appropriate.

Side Information Table Offline Program Output

As stated earlier, CHQI generates 2 output files: a side information data set that can be loaded online by TPF and an output listing describing the results of the conversion of the input file to the side information data set.

Side Information Data Set

A side information data set consists of entries containing data to be added to or removed from the side information table, or descriptive text to be displayed during the load. The entries are grouped into TPF 4K (4095-byte) records.

Each record consists of an 80-byte header and forty 100-byte entries. The byte following the last entry is used as an end-of-data indicator. The 14 remaining bytes at the end of the record are not used and are set to binary zeros. The data format in the record header and the entries is defined by the ISIDE data macro.

CHQI Output Listing

The CHQI output listing is a file of fixed-length 95-byte records. The first byte of each record is an ANSI printer control character. The listing echoes the input file with each line numbered and with attention or error messages interspersed among the input lines. The last page of the listing is a summary of the number of entries written to the side information data set and a summary of error and attention messages.

Attention messages
Attention messages are issued when valid but extraneous parameters are coded in REMOVE statements and when not all parameters are coded in ADD statements. When an attention message is issued, the ADD or REMOVE statement is still formatted into an entry and written to the side information data set (if there are no errors in the statement). Missing ADD parameters are set to null values in the generated entry; extraneous REMOVE parameters are ignored. If there are attention messages but no error messages, CHQI ends with a return code of 4.

Error messages
When an error message is issued, CHQI does not format the error statement into an entry on the side information data set. When there are errors, CHQI ends with a return code of 8.

File error messages
CHQI issues a file error message when a file (other than the listing) cannot be opened. Summary information is written to the listing file and processing ends without reading from the input file or writing to the side information output data set.

All attention and error messages begin with the prefix CHQI and are fully described in Messages (System Error and Offline) and Messages (Online).

The last page of the listing is a short summary of the processing that took place. There are 3 sections to the summary.

The first section describes the entries that were written to the side information data set. It includes a message telling which subsystem the data must be loaded to, or that the data can be loaded to any subsystem, the number of ADD entries generated, the number of REMOVE entries generated, and the number of lines of descriptive text generated.

The second section summarizes any error or attention messages that were flagged during processing. If any error or attention messages were flagged, the lines that were flagged are also listed.

The third section contains the return code issued to the operating system when CHQI ended.

Figure 56 shows an example of a listing with a number of error and attention messages.

Figure 56. Example CHQI Output Listing


TPF SIDE INFORMATION TABLE OFFLINE PROGRAM                                       PAGE     1
 
LINE #   |....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8|
---------+--------------------------------------------------------------------------------+
000001   |**********************************************************************          |
000002   |*                                                                    *          |
000003   |*   SIDE INFORMATION INPUT -- A PLETHORA OF ERRORS.                  *          |
000004   |*                                                                    *          |
000005   |**********************************************************************          |
000006   |                                                                                |
000007   |LOAD        NAME=NEWINFO                                                        |
----------------------A--------------------------------------------------------------------
A.  CHQI0009E  INVALID LOAD PARAMETER
000008   |                                                                                |
000009   |DESCR  THIS TEXT WILL GET PRINTED ON THE OPERATOR'S CONSOLE                     |
----------A--------------------------------------------------------------------------------
A.  CHQI0015E  LOAD STATEMENT BEGINNING IN LINE 000007 ENDS WITHOUT SPECIFYING SS
000010   |DESCR  WHEN THE OFFLINE DATA SET GETS LOADED.                                   |
000011   |                                                                                |
000012   |MODE-BATCH                                                                      |
----------A--------------------------------------------------------------------------------
A.  CHQI0030E  NO VERB WAS SPECIFIED FOR THIS PARAMETER
000013   |                                                                                |
000014   |ADD    LOAD       DATA                                                          |
-----------------A----------B--------------------------------------------------------------
A.  CHQI0007E  ADD STATEMENT BEGINNING IN LINE 000014 ENDS WITHOUT SPECIFYING NAME
A.  CHQI0003W  ADD STATEMENT BEGINNING IN LINE 000014 ENDS WITHOUT SPECIFYING TP
A.  CHQI0001W  ADD STATEMENT BEGINNING IN LINE 000014 ENDS WITHOUT SPECIFYING LU
A.  CHQI0002W  ADD STATEMENT BEGINNING IN LINE 000014 ENDS WITHOUT SPECIFYING MODE
A.  CHQI0014E  LOAD MUST BE THE FIRST STATEMENT
B.  CHQI0015E  LOAD STATEMENT BEGINNING IN LINE 000014 ENDS WITHOUT SPECIFYING SS
B.  CHQI0013E  INVALID VERB
000015   |                                                                                |
000016   |REMOVE ALL--EVERY                                                               |
-----------------A---B---------------------------------------------------------------------
A.  CHQI0012E  INVALID REMOVE PARAMETER
B.  CHQI0011E  INVALID PARAMETER SYNTAX
000017   |                                                                                |
000018   |ADD    N=M=EXPEDITE L=LU.62 T-ABC$123$                                          |
----------A--------B---------------C-----------D-------------------------------------------
A.  CHQI0032E  REMOVE STATEMENT BEGINNING IN LINE 000016 ENDS WITHOUT SPECIFYING NAME
B.  CHQI0031E  PARAMETER KEYWORD FOLLOWED BY PARAMETER KEYWORD
C.  CHQI0019E  LU NAME MUST BEGIN WITH AN UPPERCASE LETTER
D.  CHQI0039E  TP NAME CONTAINS HEX SUBSTRING WITH ODD NUMBER OF DIGITS
000019   |                                                                                |
000020   |REMOVE  NAME-SAME  MODE-SLOW  LU-SLOWNET.LU62  TP-ZAPMAP                        |
-----------------------------A----------B----------------C---------------------------------
A.  CHQI0005W  MODE PARAMETER IS IGNORED IN REMOVE STATEMENT
B.  CHQI0004W  LU PARAMETER IS IGNORED IN REMOVE STATEMENT
C.  CHQI0006W  TP PARAMETER IS IGNORED IN REMOVE STATEMENT
000021   |                                                                                |
000022   |ADD     N-3_DOG_NIGHT  L-NET@NY.LU62MAPPED  T-BLANK$40$SPACE  M-1SECRESP        |
----------------------------A---------B-----------C-----------D-----------E----------------
A.  CHQI0035E  SYMBOLIC DESTINATION NAME IS LONGER THAN 8 CHARACTERS
B.  CHQI0026E  Network ID CONTAINS INVALID CHARACTER
TPF SIDE INFORMATION TABLE OFFLINE PROGRAM                                       PAGE     2
 
LINE #   |....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8|
---------+--------------------------------------------------------------------------------+
C.  CHQI0018E  LU NAME IS LONGER THAN 8 CHARACTERS
D.  CHQI0038E  TP NAME CONTAINS AN EMBEDDED SPACE CHARACTER
E.  CHQI0024E  MODE MUST BEGIN WITH AN UPPERCASE LETTER
000023   |                                                                                |
000024   |ADD  N-MY        M-DOG       L-HAS                T-FLEAS                       |
000025   |     N-EVERY     M-GOOD      L-BOY.DOES           T-FINE                        |
---------------A-----------B-----------C--------------------D------------------------------
A.  CHQI0025E  NAME IS ALREADY DEFINED FOR THIS STATEMENT
B.  CHQI0022E  MODE IS ALREADY DEFINED FOR THIS STATEMENT
C.  CHQI0016E  LU IS ALREADY DEFINED FOR THIS STATEMENT
D.  CHQI0036E  TP IS ALREADY DEFINED FOR THIS STATEMENT
000026   |                                                                                |
000027   |ADD     N-DEST0001  M-MODEMAP1  L-TPFNET1.MAPLU1  T-RECEIVER1                   |
000028   |ADD     N-DEST0002  M-MODEMAP2  L-TPFNET2.MAPLU2  T-RECEIVER2                   |
000029   |ADD     N-DEST0003  M-MODEMAP3  L-TPFNET3.MAPLU3  T-RECEIVER3                   |
000030   |ADD     N-DEST0004  M-MODEMAP4  L-TPFNET4.MAPLU4  T-RECEIVER4                   |
000031   |ADD     N-DEST0005  M-MODEMAP5  L-TPFNET5.MAPLU5  T-RECEIVER5                   |
000032   |                                                                                |
000033   |REMOVE  N-OBSDEST1                                                              |
000034   |REMOVE  N-OBSDEST2                                                              |
000035   |REMOVE  N-OBSDEST3                                                              |
000036   |                                                                                |
000037   |END                                                                             |
----------A--------------------------------------------------------------------------------
A.  CHQI0013E  INVALID VERB
 
 
 
 
TPF SIDE INFORMATION TABLE OFFLINE PROGRAM                                       PAGE     3
 
SUMMARY
 
SIDE INFORMATION DATA FOR ANY SUBSYSTEM
5 ADD ENTRIES WERE GENERATED
4 REMOVE ENTRIES WERE GENERATED
2 LINES OF DESCRIPTIVE TEXT WERE GENERATED
 
23 ERRORS WERE FLAGGED
6 WARNINGS WERE FLAGGED
 
THE FOLLOWING LINES WERE FLAGGED:
 
     7 9 12 14 16 18 20 22 25 37
 
RETURN CODE = 8

Loading the Side Information Data Set to TPF

After you have the side information data set generated and free of errors, you can move on to steps 5, 6, and 7 listed in the beginning of Generating the Side Information Table for Mapped Conversations.

The following description refers to Figure 57, which shows a TPF console during the mounting of an offline generated side information tape, initialization of the online side information table, and loading of the tape to the side information table.

  1. The ZTVAR command activates the subchannel address of the tape drive on which the tape is mounted.
  2. The 2 ZTLBL commands create a TPF internal label (SID) matching the IBM standard label on the offline generated tape, and make the internal label usable so that the tape can be mounted.
  3. The ZTMNT command defines the tape drive at subchannel address 580 as the active SID tape. At this point the tape is accessible to a TPF online process.
  4. The side information table has not been initialized, so the ZNSID INITIALIZE function message is entered.
    Note:
    The side information table must be initialized before any data can be added to it. Initialization sets up the structure of the side information table and clears any data that previously existed online. The side information table must be initialized only when a new TPF system is brought online, or when the entire table is to be replaced. If you attempt to load the side information data set when the online table is not initialized, the following response is returned to the operator console:
      NSID0016E RECORD ID CHECK FAILURE, CHECK SIDE INFORMATION
                TABLE INITIALIZATION
    
  5. The ZNSID LOAD command loads the tape into the newly initialized side information table.
  6. ZNSID D displays 1 of the newly loaded side information entries.

Figure 57. Loading a Side Information Offline Generated Tape

+--------------------------------------------------------------------------------+
|User:   ZTVAR A 580                                                             |
|System: CSMP0097I 11.48.39 CPU-B SS-BSS  SSU-HPN  IS-01                         |
|COTU0101I 11.48.39 TVAR BSS    PROT ENTRY ACQUIRED FOR DEVICE 580               |
|                       BY THIS PROCESSOR                                        |
|CSMP0097I 11.48.39 CPU-B SS-BSS  SSU-HPN  IS-01                                 |
|COTE0001I 11.48.39 TVAR      - TAPE STATUS                                      |
|                                                                                |
|ADDRESS   TPNAME  SSUNAME  STATUS  TPIND  VOLSER  DENS  #BLOCKS LDR             |
|                                                                                |
| 580       AVAIL                                                                |
|                                                                                |
|User:   ZTLBL SID C LSL F$SIDOUT$ I G                                           |
|System: CSMP0097I 11.48.39 CPU-B SS-BSS  SSU-HPN  IS-01                         |
|COTL0001I 11.48.39 DTLB HPN  - TAPE LABEL INFORMATION                           |
|     SID - NOT USABLE         I/O-INPUT   L-SL   D-ALL  NOCOMP                  |
|     NOBLK                    T  - 000                                          |
|     F-SIDOUT                 G  -        S-0001                                |
|     RETENTION PERIOD      -  00007                                             |
|     LAST MOUNTED          -                                                    |
|     LAST FILE SERIAL NO   -                                                    |
|                                                                                |
|User:   ZTLBL SID U                                                             |
|System: CSMP0097I 11.48.39 CPU-B SS-BSS  SSU-HPN  IS-01                         |
|COTJ0044I 11.48.39 TLBL HPN    COMPLETE                                         |
|                                                                                |
|User:   ZTMNT SID 580 AI                                                        |
|System: CSMP0097I 11.48.39 CPU-B SS-BSS  SSU-HPN  IS-01                         |
|COTM0046I 11.48.39 TMNT HPN    TAPE SID MOUNTED ON DEVICE 580                   |
|                       VSN A00112 G     S0001 D38K   SL  NOBLK                  |
+--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+
|User:   ZNSID INITIALIZE                                                        |
|System: CSMP0097I 11.48.39 CPU-B SS-BSS  SSU-HPN  IS-01                         |
|NSID0004I 11.48.39 SIDE INFORMATION TABLE INITIALIZED                           |
|                                                                                |
|User:   ZNSID LOAD T-SID                                                        |
|System: CSMP0097I 11.48.39 CPU-B SS-BSS  SSU-HPN  IS-01                         |
|NSID0037I 11.48.39 LOADING SIDE INFORMATION DATA                                |
|CSMP0097I 11.48.39 CPU-B SS-BSS  SSU-HPN  IS-01                                 |
|NSID0017I 11.48.39 USER TEXT FROM SIDE INFORMATION TAPE                         |
|ADDING 100 ENTRIES TO SIDE INFORMATION TABLE                                    |
|--- END OF DESCRIPTION ---                                                      |
|CSMP0097I 11.48.39 CPU-B SS-BSS  SSU-HPN  IS-01                                 |
|NSID0005I 11.48.39 NEW SIDE INFORMATION TABLE ENTRIES LOADED                    |
|ENTRIES PROCESSED  -        100                                                 |
|ENTRIES ADDED      -        100                                                 |
|ENTRIES CHANGED    -          0                                                 |
|ENTRIES REMOVED    -          0                                                 |
|ERRORS DURING LOAD -          0                                                 |
|CSMP0097I 11.48.39 CPU-B SS-BSS  SSU-HPN  IS-01                                 |
|COTC0087A 11.48.39 TCLS HPN    REMOVE SID FROM DEVICE 580                       |
|                       VSN A00112  NOBLK                                        |
|User:   ZNSID D N-NAME100                                                       |
|System: CSMP0097I 11.48.39 CPU-B SS-BSS  SSU-HPN  IS-01                         |
|NSID0002I 11.48.39 SIDE INFORMATION ENTRY DISPLAY                               |
|     NAME- NAME100                                                              |
|       TP- TP100                                                                |
|       LU- LU100                                                                |
|     MODE- MODE100                                                              |
+--------------------------------------------------------------------------------+

Footnotes:

3
Commas have no meaning other than to separate tokens and are exactly equivalent to blank characters.

4
The parameter for the DESCR verb is an exception to this. DESCR's parameter begins with the first nonblank character following the verb and continues to the last nonblank character before the next logical end of record. If there is no nonblank character between the DESCR verb and the next end of record, the parameter is a null string.

5
For consistency with TPF commands, LU parameters specified as .luname; that is, no network ID but a leading period before the LU name are accepted. The leading period is not included in the side information data set or in the online side information table.