Terminal not known condition exits 214 – IBM SC33-1683-02 User Manual

Page 246

Advertising
background image

DELETE_SUSPEND

DEQUEUE

ENQUEUE

RESUME

SUSPEND

WAIT_MVS.

The sample program for the XALTENF and XICTENF exits, DFHXTENF

One program can be used for both exits, or a separate program can be written for
each. Figure 2 shows the executable code from the supplied sample program
DFHXTENF, which can be used for both exits. DFHXTENF rejects transient data
requests, because the action in this case is very much installation-dependent.

Important

The example is intended purely as a demonstration of some of the possibilities
available, and would be impractical in a production environment.

DFHXTENF CSECT

DFHVM XTENF

ENTRY DFHXTENA

DFHXTENA DS

0H

STM

R14,R12,12(R13)

save registers

BALR R11,0

set up base register

USING *,R11

*

USING DFHUEPAR,R1

DFHUEH parameter list

*

*

Could check the terminal ID at this point. In this

*

program we assume it is valid. We also choose to accept

*

START requests and reject Transient Data trigger level

*

events.

*

L

R2,UEPICEVT

access type of request

CLC

0(2,R2),START

START command?

BE

STARTCMD

yes

*

CLC

0(2,R2),STARTDAT

START command with data?

BNE

NOTSTART

no, must be Transient Data

*

STARTCMD DS

0H

*

*

Accept the default netname if we are Function Shipping.

*

Otherwise build a netname.

*

L

R2,UEPICFS

access FS information

CLI

0(R2),UEPICFY

Function Shipping?

BNE

BLDNETNM

no, build a netname

*

LH

R15,NETNAME

accept the default netname

B

EXIT

Figure 2. Sample program for XALTENF and XICTENF exits (Part 1 of 2)

terminal not known condition exits

214

CICS TS for OS/390: CICS Customization Guide

|

|

Advertising