
CIUSPEP3 Stored Procedure
CIUSPEP3 is a stored procedure that you can use to identify your application entry points for an existing platform, application, or Operation.
For example, CIUSPEP3 can show you all of the possible entry points for the TEST_OPERATIONS application. This is the DUMMY application name that is used by CICS® IA to store application and operation names that are captured as a result of editing the PROGRAM resource and defining an operation name.
Syntax
EXEC SQL
CALL CIUSPEP3 (in_calltype, in_collid, in_applid, in_platform, in_aplname, in_applver1, in_applver2, in_applver3, in_apploper, prc, psqlcode, psqlstate, perrmsg);
EXEC SQL
CALL CIUSPEP2 (‘A',’%’,' ',’TEST_OPERATIONS’,’0’,’0’,'0',' ',prc, psqlcode, psqlstate, perrmsg);
Procedure parameters
Several input parameters can help you to manage CIUSPEP3 processing and several output parameters that inform about the process completion and errors, if any.
Parameter name | Input/output | Type | Description |
---|---|---|---|
in_calltype | INPUT | CHAR(1) | Type of call. P for a list of entry points by platform. A for a list of entry points by application. O for a list of entry points by operation. |
in_collid | INPUT | CHAR(16) | Specifies the collection ID for which you want to list the entry points. |
in_platform | INPUT | CHAR(64) | Specifies the platform name. Required for P,
A, and O.
Note: It can be blank for A or O
but must not be NULL.
|
in_applname | INPUT | CHAR(64) | Specifies the application name. Required for call types A and O. |
in_applver1 | INPUT | INTEGER | Specifies application MAJOR version. Required for call types A and O. |
in_applver2 | INPUT | INTEGER | Specifies application MINOR version. Required for call types A and O. |
in_applver3 | INPUT | INTEGER | Specifies application MICRO version. Required for call types A and O. |
in_apploper | INPUT | INTEGER | Specifies operation version. Required for call type O. |
prc | OUTPUT | INTEGER | Return Code |
psqlcode | OUTPUT | INTEGER | DB2 SQL code |
psqlstate | OUTPUT | CHAR(5) | DB2 SQL state |
perrmsg | OUTPUT | VARCHAR(300) | Error message |
Returned result sets
The CIUSPEP3 stored procedure returns two result sets for all types of call types. The structure of the result sets depends on the input parameters values. A result set is a set of rows that are associated with a cursor opened in the stored procedure and returned to caller program. A result set is effectively a table. You can access the data that is returned in a result set by running an SQL ASSOCIATE LOCATORS, followed by an SQL ALLOCATE cursor, and then the SQL FETCH loop.
For PLATFORM, APPLICATION and OPERATION call types return 2 result sets. The first set contains the TRANSID or PROGRAM entry points and it returns a result set, which contains the following DB2 columns:
COLLECTION_ID, APPLID, PLATFORM, APPL_NAME, APPL_VER1, APPL_VER2, APPL_VER3, APPL_OPER, TRANSID, INITIAL_PROGRAM, and BACK_PROGRAM.
In this case the entry points can be based on the TRANSACTION, the INITIAL_PROGRAM, or the BACK_PROGRAM.
The second set contains the web service type entry points and it returns a result set, which contains the following DB2 columns:
COLLECTION_ID, APPLID, PLATFORM, APPL_NAME, APPL_VER1, APPL_VER2, APPL_VER3, APPL_OPER, NAME, PROGRAM, URIMAP, and BACK_PROGRAM.
