I I I
I I AS I ID=59, DEGROUP= (GROUP1, 3) (TOTAL OF 3 2795' S) IGROUP1 ITGROUP ITC=lATTENDNC,TC2=SETUP,TC3=PRODN,... (2795'S)
I I 1
1* DEFINING TRANSACTION GROUP FOR 2797 AND DU~MY TRANSACTION GROUP FOR 2795 AND 2796
I I I
I lAS IID=59,DEGROUP=(GROUP1,3) (TOTAL OF 3 2797'S) IGROUP1 ITGROUP I TC1=MESSAGE (DUMMY TABLE FOR 2795'S)
I GROUP 2 ITGROUP I TC1=MESSAGE (DUMMY TABLE FOR 2796'S)
I GROUP 3 ITGROUP ITC1=MESSAGE,TC2=RECEIPT,TC3=ISSUE, ••• (2797'S)
L ________ ~ ___ • ______ ~ ___________________________________________________________________ _
Figure 40. Examples of Defining Transaction Group Tables for Data Entry Units
the DEU-INDEX table corresponding to this area station are then defined with a value indicating there are no DEUs. The DEGROUP parameter must be coded for the 2793.
GDUAS (Guidance Display Unit Area Station) Macro Instruction
The GDU Area Station macro instruction is used to ,build an entry in the GDU Area Sta-tion Table. The position of the entry to be built rel,ati ve to the beginning of the table is det,ermined from the 10 operand.
Each GDUAS macro requires 2 bytes of 2715 storage. Tbe format of the GDUAS macro is:
r---T--·---T---,
1 Name IOperationlOperand I
t---t--·---+---~
I (symbolllGDUAS IID=absexp, I
I I I GDUNUMB=absexp I
L ________ ~ _________ ~ ______________________ J
symbol
ID
the name field of this macro is optional.
each area station with attached 2798 GDUs is aSSigned a specific address
(X'80' - X'E3') at system installation time, and the value of 'absexp' is the decimal representation of that address (see Figure 38). ID is used to deter-mine the position of an entry in the GDUAS 'I'able. The value of the ID operand must be from 0 to 99. The GDUAS macros must be in ascending
sequence by ID. A GDUAS macro found to be out of sequence or in error ter-minates the assembly of this macro instruction.
GDUNUMB
this operand specifies the number of GDUs on this area station. The value of this operand can be from 1 to 16 for a 2793 and from 1 to 12 for a 2791 Model 3.
Note: The GDUAS macro should only be coded for an Area station with 2798 GDUs
attached. The GDUAS macro must be coded once for every area station with 2798 GDUs attached.
TGROUP (Transaction Group) Macro Instruction
The TGROUP (Transaction Group) macro defines entries in a TGROUP Table. Each keyword operand associates a transaction list with a transaction code. The maximum number of TGROUP macros allowed is 63. The TGROUP macro instructions must follow the
last AS macro instruction coded. A macro sequence error occurs if they do not. Each TGROUP macro requires 18 bytes of 2715 storage.
The three types of data entry units (2795, 2796, and 2797) require separate transaction groups, one for all 2795s con-nected to an area station, followed by one for all 2796s connected to the same area station, and immediately followed by one
IBM 2790 Data Communication System -- Programming Considerations 165
for all 2791s connected to the same area
IName IOperationlOperand I
~---+---+---~ defined. When using the transaction 166 OS/VS BTAM SRL be identical. Transaction expansion must be used when generating the tran-saction list in which message routing is to be specified. A transaction expansion entry must not refer to another transaction expansion entry.
ASCTR (Area Station Counter) Macro
counter level control. Schedule readout and count testing are performed at the individual counter level.
This macro also allows routing specifi-cation to be specified for counter overflo~
The macro is coded once for each area sta-tion with pulse counters. The maximum num-ber of ASCTR IllIacros that can be coded is 100.
symbol ID
the name field is optional.
specifies the decimal representation of the address of the area station on which pulse counters are available.
The 1D operand is not required for all area sta1tions, but the ID operands must be in ascending sequence. An ID operand lout of sequence causes an in-valid taible assembly. The ID operand may have values from 0 to 99.
HIGHCTR
specifies the number of the highest counter ion this area station that scheduled readout or count testing may be perfo:rmed on. Values for the
HIGHCTR operand may range from 0 to 63, sinc'e only 63 counters are allowed on any given area station. A value of
o
indica'tes that no area station coun-ters use scheduled readout or count testing.ROUTE
CPU
DISK
LOG
specifies the destination of counter overflow and count test response mes-sages. At least one destination must be specified, and if only one is spec-ified, the parenthesis are not coded.
The CPU and DISK suboperands are mutu-ally exclusive.
specifies that counter overflow and count test response messages should be routed directly to the CPU.
specifies that counter overflow and count test response messages should be routed to the 2715 integral disk.
specifies that counter overflow and count test response messages should be routed to the 2740 attached to the 2715.
AS LOG
specifies that counter overflow and count test response messages should be routed to the area station 1053 print-er from which the ovprint-erflow was
initiated.
EXTALRM
specifies that counter overflow and count test response messages should be routed to the 1053 printer on the area station from which the overflow was initiated, and that the external alarm contact closure at the area station should be activated.
The above suboperands specifying routing information for counter overflow and count test res~onse messages need not be coded in any given order.
NEXTAS
specifies the decimal representation of the address of the next higher area station with pulse counters on which count testing or readout functions may be scheduled. The NEXTAS operand may have values from 0 to 99. This
operand must be coded when HIGHCTR=O is coded, but is not necessary for any other HIGHCTR value. NEXTAS=O must be coded if there is no higher area sta-tion that has pulse counters on which count testing or readout functions may be scheduled. Unless NEXTAS=O is coded, the NEXTAS operand must be greater than the ID operand for this ASCTR macro. If the NEXTAS operand is greater than 0, the ASCTR macro
referred to by the value of the NEXTAS operand must have a HIGHCT~ operand value greater than O.
CTRGROUP (Counter Group) Macro Instruction The CTRGROUP macro is used to generate the Counter Table. The macro must be coded once for each counter in the system on which schedule readout or count test func-tions are to be performed. A CTRGROUP uacro must be coded for the counter whose value was specified in the HIGHCTR o~erand
of the ASCTR macro instruction for this area station. The counter Table is organized on a group basis. Each group consists of the highest counter with sche-duled readout or testing and all counters
(whether scheduled or unscheduled) below it cn the same area station. Each group is truncated at the highest counter scheduled for readout or testing, with a maximum of 63 counters allowed per area station. The Counter Table consists of two bytes of con-trol information for each of these counters
(scheduled and unscheduled) plus two addi-tional bytes at the end of the table. Up to 504 counters may be scheduled for the entire system. Each CTRGROUP macro defines two bytes of control information for a par-ticular counter.
The format of the CTRGROUP macro in-struction is:
IBM 2790 Data Communication System -- programming considerations 167
r---T---T---,
I Name IOperationlOperand I
~---+---+---~
l[symbolllCTRGROUP Ictrno, I
I I I [s roJ, I
L ________ ~ _________ ~ ______________________ J
symbol in ascending sequence.
indicates which readout schedule is to CTRSCHED macro instruction.
specifies the decimal representation of the address of the area station on SROENAB=NO indicates that schedule readout is not to be automatically SROENAB=NO is assumed.
CTINIT
specifies an initial count test condi-tion that is to be started by the 2715 after an ICPL for this counter. Cod-ing CTINIT=UNASP indicates that unas-signed production testing is to be started by the 2715. Coding CTINIT=
NCT indicates that no-count testing is to be started by the 2715. Coding CTINIT=NULL indicates that neither unassigned nor no-count testing is to
CTRSCHED (Counter Schedule) Macro Instruction Instruction CTRSCHED macro instruction is:
r---T---T---,
I Name I Operation I Operand I
~---+---+---~
I [symbolllCTRSCHED Isched,... I
L ________ ~ _________ ~ _______________________ J
symbol
GDUTRANS (Guidance Display Unit Transaction) Macro Instruction
The GDU Transaction macro is used to build
two bytes of 2715 storage. The format of
L ________ .1 ___ , ______ .1 ______________________ J
symbol
the name field of this macro is optional.
TRCOOE
this operand is the value of a tran-saction code. Each transaction code is associated with a particular GOU transaction list (TRLIST) referred to by 'symboln' is associated with the TRCOOE operand.
PARAMNUM (Parameter List Number) Macro Instruction
L ________ .1-__ . ______ .1 ______________________ J
symbol
PLN
the namE! field of this macro is optional.
this opE!rand specifies the parameter list number that is to be associated
PARMLIST (Parameter List) . Macro Instruction The PARMLIST macro is used to generate an Parameter List Number Table. Every PARM-LIST macro must be referred to by a PARMLST
symbol PARMLIST (CKLNGTH=(length-absexp, I
errguidance-absexp,···)]1
NO I
(,CKMONKY= YES ] I
(, CKMODll= (length-absexp, I position-absexp,t
L______ ---______
~_____________________________
JIBM 2790 Data Communication System -- Programming Considerations 169
symbol the length specified.
length
this suboperand specifies the length of the data entry and its value may be
this suboperand specifies the error guidance that is returned to the 2798
this operand indicates whether the 2715 will check to determine if the 2798 Monitor key is on. If CKMONKY=
YES is coded, the 2715 checks that the Monitor key is on. If a Monitor key error is encountered when CKMONKY=YES, the error guidance, as specified by character. A detailed description of modulus 11 checking can be found in
170 OS/VS BTAM SRL
ComFonent Description: IBM 2790 Data Communication System, GA27-3015.
length
this suboperand specifies the length of the modulus 11 check field. The value of this suboperand may be from 1 to 15. The length does not include the self-check character.
position
this suboperand specifies the starting position of the modulus 11 check
field. The value of this suboperand may be between 2 and 16.
errguidance
this suboperand specifies the error guidance that is returned to the ~798
Example: CKMOD11=(6,2,2,10,14) will result in a modulus 11 check of a 7
this suboperand specifies the starting position of the field for which the range check is performed. The value may be from 2 to 17.
position2
this suboperand specifies the last position of the field for which the
2715 will check that the test position is indeed that digit.
Example: CKRANGE=(8,10,91,80,63) will cause thE~ 2715 to check for a 3 digit
Example: From the example associated with the CKRANGE operand, the user may
Example: From the example associated with the CKRANGE operand, the user may desired error guidance is returned with the normal guidance for the next character. A detailed description of modulus 10 checking can be found in Component Description: IBM 2790 Data Communication System, GA27-3015.
length
this suboperand specifies the length of the modulus 10 check field. The value of this suboperand may be from 1 to 15. The length does not include the self-check character.
position
this suboperand specifies the starting position of the modulus 10 check
field. The value of this suboperand may be from 2 to 16.
errguidance
CKOR
this suboperand specifies the error guidance that is returned to the GDU CKMOD10 error condition exists. (See Figure 37.>
Example: CKMOD10=(4,1,16) will result in a modulus 10 check of a 5 digit characters associated with this test and only one must compare.
position
this suboperand specifies in the data entry that is the character comparison.
of this suboperand may be
IBM 2790 Data Communication System -- programming Considerations 171
checkchar1,checkcharn
Example: CKOR=(3,D3,F5,7C,61) will check the fourth data entry position
Example: From the example associated with the CKOR operand, the user may conse-cutive positions specified to ensure that they match ~ll of the specified check characters.
position1
this suboperand specifies the starting position of the field for which the CKAND compare is started. The value of this suboperand may be from 2 to 17.
position2
this suboperand specifies the last position of the field for which the the character in the corresponding position of the data field will not be checked.
Example: CKAND=(2,5,C1,C2,00,C3) will check data entry positions 2, 3, and 5 received in the consecutive positions specified do not match all of the specified check characters. The value of each suboperand may be from 1 to 16
Example: From the example associated with the CKAND operand, the user may code ANDGUID=9 to inform the GDU operator if the specified characters do not match. If the characters do numeric characters are received.
position1
this suboperand specifies the starting position of the field to be checked.
The value may be from 2 to 17.
position2
this suboperand specifies the last position of the field to be checked.
The value may be from 2 to 17, but must be greater than or equal to the
'position1' suboperand.
errguidance
this sutoperand specifies the error guidance that is returned to the GDU
Example: CKNONUM=(2,17,3,6) causes the 2715 to check positions 2 through 17 of the GDU data entry to ensure that all the characters are
non-numeric. If any of the characters in the specified positions are numeric, the error guidance lights for lines 3 numeric characters are received.
position1
this suboperand specifies the starting position of the field to te checked.
this sut~perand specifies the error
guidanc€~ that is returned to the GDU
Example: CKNUM=(8,8,15) causes the 2715 to check position 8 of the GOU operands are mutually exclusive.
Note: Only three of the following
DISPGUID (Display Guidance) Macro Instruction
The DISPGUID macro is used to define a
dis-~lay guidance message in the Display Gui-dance Tatle. A DISPGUID macro must be defined for every display guidance message the user defines. The desplay guidance
IBM 2790 Data Communication System -- Programming Considerations 173
symbol
this operand indicates whether the display guidance message is returned to the 2715 after i t is displayed at the GDU display guidance and the operator presses the GDU Enter Key.
Coding SUPPRES=YES or omitting the operand indicates that the defined data that was written to the GDU by
TRANSLAT (Translate Table) Macro Instruction
I [symbol] ITRANSLAT ITRANSCH=hexchar, I
I I ITRANTXT='text' I
L ________ ~ _________ ~ ______________________ J
symbol
the name field of this macro is optional.
TRANSCH
this operand defines the character that is translated. The value for TRANSLAT macro: TRANSCH=C3 , TRANTXT= , 4 SPEED CLUTCH'. The 2715 checks the character entered for this Translate transaction and replaces the C with
TRLIST (Transaction List) Macro Instruction The Transaction List macro is used with the instructions are composed of two elements:
a header, and either an internal message or from one to sixteen data-entry steps. The header information is provided in the
TRLIST macro instruction. The TRLIST macro must follow the last TGROUP macro. specified ROUTE parameter. Transaction routing does not mean routing to an area station 1053 printer.
Each TRLIST macro requires [5 + (text length + 1)] bytes of 2715 storage. The format of the TRLIST macro is:
r---T--·---T---,
I Name I Operation I operand I
..---+--.---+---~
symbol TRLIST TRID=absexp1
[,ROUTE=[{~~~x}]]
[,LOG][{::~;;XP2}]
[,TEXT=
I~~s 11
[,INQDISP=
YES ]
[,DEMOD10=
~~s ]
[ NO ]
, DEMOD11=- YES
['GDU={~~S
]L- _______ ~ _________ ~ _____________________ _J
symbol
the name field is required for this macro instruction.
TRID=absexp1
specifies a transaction identifier.
The user assigns a value from 0 to 159 to wabsexp1,w and the 2715 places this value in the transaction control byte of the ·transaction header for priority and deferred data. The value of
wabsexp1w must be in ascending order with the other TRIO parameters coded in the program; however, values may be omitted (a warning message is
generated at assembly time). Since the user receives the transaction header with a message, the transaction identifier allows him to determine which TRLIST macro processed the data in the 2715.
ROUTE
the ROUTE operand specifies· the
destination of the data records (tran-sactions) that originate on one of the devices attached to the 2715. At least one destination must be speci-fied, a.nd if only one is specified the parentheses are not coded.
DISK
specifies that the transaction should be routed to the 2715 integral disk;
that is, the message is a deferred message.
CPU
specifies that the transaction should be routed directly to the CPU; that is, the message is an inquiry or a priority message.
LOG
specifies that the transaction is to be routed to the 2740 attached to the 2715.
NULL
specifies that the first data entry of the transaction is the destination address of the message, that is, the hexadecimal address of an area sta-tion. The message is to be routed to
the printer attached to that area station.
absexp2
specifies the decimal representation of the address of an area station (see Figure 39). The message is to be routed to the printer attached to that area station.
~: The suboperands of the ROUTE parameter may be coded in any order.
If one is omitted, commas need not be coded to indicate the omission.
TEXT= NO YES
specifies that a message defined in a subsequent ASLIST, DEULIST, GDULIST or CTRLIST macro is to be routed.
INQDISP
the INQDISP operand indicates whether this transaction is an Inquiry Display transaction. Coding INQDISP=YES spe-cifies that inquiry display will be used in this transaction. Coding INQDISP=YES requires that INQDISP=YES be coded in the CONFIGUR macro. Cod-ing INQDISP=YES requires one extra GDULIST macro to end this transaction
list. Se~ GDULIST macro description for details.
DEMOD10
the DEMOD10 operand indicates whether the 2715 will perform a Modulus 10 self check on all or part of a data entry from an area station or data entry unit. Coding DEMOD10=YES speci-fies that Modulus 10 self checking will be performed on a dqta entry in this transaction. Coding DEMOD10 requires CORE=32 to be coded in the CONFIGUR macro. This operand is mutu-ally exclusive with the DEMOD11
operand. This operand does not apply to the 2798 GDU.
DEMOD11
the DEMOD11 operand indicates whether the 2715 will perform a Modulus 11 self check on all or part of a data entry from an area station or data IBM 2790 Data Communication System -- Programming Considerations 175
GDU
entry unit. Coding DEM0011=YES speci-fies that Modulus 11 self checking will be performed on a data entry in this transaction. Coding OEM0011=YES requires CORE=32 to be coded in the transaction identifiers (TRIO) to be specified by the user. The normal range of identifiers is from 0 to 159 and the additional identifiers range from 0 to 99. Coding GDU=YES resets identifiers. If non-unique identi-fiers exist, the user must also check other macros omitted:
TRLISTO
TRLST159 TRLIST TRID=159,ROUTE=CPU GOUTRO TRLIST TRID=O,ROUTE=DISK,
GDU=YES
GOUTR99 TRLIST TRID=99,ROUTE=CPU, GDU=YES additional storage of length-of-text-plus-one bytes. The format of the ASLIST macro
(symbol] ASLIST device-code,NORM=absexp (, LENGTH= (absexp1,
this operand indicates which guidance light on the area station should be
specifies the significant length of the data entry (the number of data characters excluding blanks). This may be any value from 0 to 81; the maximum length depends on the input device -- card reader, badge reader, manual entry, OEM entry.
atsexp2
specifies which guidance light should be switched on if the number of
r---T---T---T---,
indicates which guidance light should be switched on if the specified values do not match. This value must be from 1 to 31. (See Figure 38.>
If this operand is omitted, no error checking takes place.
The DIGIT operand can not be coded if
User-documented instructions to the opera-tor must reflect the fact that the
this operand specifies which guidance light on the area station is turned on
Coding this operand requires INQDISP=
YES to be coded in the TRLIST macro
YES to be coded in the TRLIST macro