User-written node error programs, Restrictions on the use of exec cics commands – IBM SC33-1683-02 User Manual

Page 507

Advertising
background image

DFHNEPC

DSECT

DS

F

Load instruction

DS

F

Branch instruction

CSVTNEP

DS

A

Node error program base address

CSVTESBL

DS

A

NEPESBL - ESB locate routine

CSVTNEBD

DS

A

NEPNEBD - NEB delete routine

CSVTECUP

DS

A

NEPECUP - error count update

routine

User-written node error programs

You can write your own NEP in any of the CICS-supported languages. However,
CICS-supplied NEP code is provided in assembler language only. The
communication area parameter list is supplied in assembler-language and C
versions. The names of the supplied source files, copy books, and macros, and the
libraries in which they can be found, are listed in Table 23.

Table 23. Supplied source files, copy books, and macros

Name

Type

Description

Library

DFHZNEP0

Program

Default node error
program (assembler
language)

CICSTS13.CICS.SDFHSAMP

DFHZNEPX

Source

Default NEP (embedded
by DFHZNEP0 via COPY
statement)

CICSTS13.CICS.SDFHSAMP

DFHSNEP

Macro

Sample NEP program
generator (assembler
language)

CICSTS13.CICS.SDFHMAC

DFHZNEPI

Macro

NEP interface generator
(for multiple NEPs)

CICSTS13.CICS.SDFHMAC

DFHNEPCA

Macro

Assembler-language
communication area

CICSTS13.CICS.SDFHMAC

DFHNEPCA

Copy
book

C-language
communication area

CICSTS13.CICS.SDFHC370

If you code in assembler language, you can use the sample NEP as a framework
on which to construct your own node error program.

Restrictions on the use of EXEC CICS commands

There are certain restrictions on the commands that a NEP can issue. The use of
any commands which require a principal facility causes unpredictable results,
and should be avoided
. In particular, you should not use commands which invoke
the following functions:

v

Terminal control (“CEMT-type” commands, such as EXEC CICS INQUIRE
TERMINAL,

are permissible)

v

BMS (except routing)

v

ISC communication (including function shipping). This includes START requests
for remote transactions. Such requests are not recommended because CSNE
(Node Abnormal Condition task) might become suspended while doing an
ALLOCATE to the remote system.

If you need to start a remote transaction, start a local transaction which starts a
remote one in turn.

the sample node error program

Chapter 9. Writing a node error program

475

Advertising