IBM SC34-6814-04 User Manual
If used in this way, the initiated transaction can write an appropriate signon
message when the session has been acquired. Note, however, that if
LOGONMSG=YES is specified on the CEDA DEFINE TYPETERM command, the
CICS “good morning” message is also initiated when the session is opened. Refer
to “Restrictions on the use of EXEC CICS commands” on page 505.
message when the session has been acquired. Note, however, that if
LOGONMSG=YES is specified on the CEDA DEFINE TYPETERM command, the
CICS “good morning” message is also initiated when the session is opened. Refer
to “Restrictions on the use of EXEC CICS commands” on page 505.
Coding for specific VTAM sense codes
Figure 35 shows how your NEP error processors could test for the presence of
specific VTAM sense codes.
specific VTAM sense codes.
Writing multiple NEPs
You can write several node error programs, as described in “Multiple NEPs” on
page 485. When an error occurs, the node abnormal condition program passes
control to an interface module, DFHZNEPI, which determines the transaction class
and passes control to the appropriate node error program.
page 485. When an error occurs, the node abnormal condition program passes
control to an interface module, DFHZNEPI, which determines the transaction class
and passes control to the appropriate node error program.
If only one node error program is used, the interface module (DFHZNEPI) is not
required. If the node error program is named DFHZNEP, the node abnormal
condition program branches directly to that. If more than one node error program is
used, the interface module (DFHZNEPI) is required. In this case, the node error
programs must be given names other than DFHZNEP. There must be an installed
program definition for every node error program generated.
required. If the node error program is named DFHZNEP, the node abnormal
condition program branches directly to that. If more than one node error program is
used, the interface module (DFHZNEPI) is required. In this case, the node error
programs must be given names other than DFHZNEP. There must be an installed
program definition for every node error program generated.
DFHZNEPI macros
The following macros are required to generate the node error program interface
module (DFHZNEPI):
module (DFHZNEPI):
v
DFHZNEPI TYPE=INITIAL to specify the name of the default transaction-class
routine.
routine.
v
DFHZNEPI TYPE=ENTRY to associate a transaction-class with a
transaction-class error handling routine.
transaction-class error handling routine.
v
DFHZNEPI TYPE=FINAL to end the DFHZNEPI entries.
The DFHZNEPI interface module must be generated when you require the node
abnormal condition program to pass control to the appropriate user-written node
error program for resolution of the error.
abnormal condition program to pass control to the appropriate user-written node
error program for resolution of the error.
TEST1
EQU
*
CLC
TWASENSR(2),SNS1
SENSE CODE EQUAL TO NNNN
BNE
TEST2
NO, THEN NEXT TEST
NI
TWAOPT1,TWAOAF
PRINT ACTION MESSAGES ONLY
OI
TWAOPT2,TWAOAS+TWAOAR+TWAOAT
ABANDON SEND,RECEIVE AND TASK
NI
TWAOPT2,255-TWAOASM
SET SIMLOGON OFF
OI
TWAOPT3,TWAOINT
SET INTLOG NOW ALLOWED
NI
TWAOPT3,255-TWAONINT
OR RESET NOINTLOG
B
END
.
.
.
.
.
SNS1
DC
X’NNNN’
Figure 35. Sample code, showing how your node error program could test for specific VTAM sense codes
508
Customization Guide