IBM Version 4 manual Copy QSYSINC/QRPGSRC,QUSREG, Ircv, Move \BLANKS

F\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
F\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
F\
FQPRINT O	F	132	PRINTER	UC
I\

I\ Error Code parameter include. As this sample program

I\ uses /COPY to include the error code structure, only the f￿irst

I\ 16 bytes of the error code structure are available. If the

I\ application program needs to access the variable lengt￿h

I\ exception data for the error, the developer should physi￿cally

I\ copy the QSYSINC include and modify the copied include t￿o

I\ define additional storage for the exception data.

I\

I/COPY QSYSINC/QRPGSRC,QUSEC

I\

I\ Formats for the Retrieve Exit Information API.

I\

I/COPY QSYSINC/QRPGSRC,QUSREG

I\

I\ Miscellaneous data

I\

IDS

I I	'EXAMPLE_EXIT_POINT '		1	2ð EPNTNM
I I	-1	B	21	24ðEPGMNB
I I	35ðð	B	25	28ðRCVSZ
I		B	29	32ðX
I		B	33	36ðY
I			37	57 CALLPG

IRCV	DS	35ðð
C\
C\ Beginning	of	mainline
C\

C\ Retrieve the exit point information first. If the current

C\ number of exit programs is not zero, retrieve the exit

C\ programs. It is not necessary to call for the exit point

C\ information to determine if the exit point has any exit

C\ programs. It is done here for illustrative purposes only.

C\ You can make one call to the API for the exit program

C\ information and check the number of exit program entrie￿s

C\ returned field to see if there are any exit programs to c￿all.

C\

C\ Initialize the error code to inform the API that all

C\ exceptions should be returned through the error code pa￿rameter.

C\

C	Z-ADD16	QUSBNB
C\

C\ Blank out the continuation handle to let the API know th￿at this

C\ is a first attempt at the retrieve operation.

C\
C	MOVE \BLANKS	CONTHD 16

C\

C\ Call the API to retrieve the exit point information

C\
C	CALL 'QUSRTVEI'
C	PARM	CONTHD
C	PARM	RCV
C	PARM	RCVSZ
C	PARM 'EXTIð1ðð'FORMAT 8

B-72System API Programming V4R1