
CIUSPEPS Stored Procedure
CIUSPAPP is a stored procedure that you can use to identify and group your application entry points by the resource used. The type of resource that is used can be any CICS®, DB2, MQ or IMS resource.
For example, CIUSPEPS can show you the possible entry points for all of the transactions that use a CICS FILE called PAYROLL.
Syntax
EXEC SQL
CALL CIUSPEPS (in_calltype, in_collid, in_applid, in_object, in_objtype1, in_objtype2, prc, psqlcode, psqlstate, perrmsg);
EXEC SQL
CALL CIUSPEPS (‘T’,’%’,’%’,’PAYROLL’,’CICS’,’FILE’, prc, psqlcode, psqlstate, perrmsg);
Procedure parameters
There are several input parameters that help you to manage the CIUSPEPS processing and several output parameters that provide information about the process completion and any errors.
Parameter name | input/output | Type | Description |
---|---|---|---|
in_calltype | INPUT | CHAR(1) | Type of call T or P for transaction and program entry points. U for Webservice type entry points (URIMAP). A for all entry points. |
in_collid | INPUT | CHAR(16) | Specifies the collection ID for which you want to list the entry points. |
in_applid | INPUT | CHAR(8) | Specifies the application ID for which you want to list the entry points. |
in_object | INPUT | CHAR(255) | Specifies the name of the resource object for which you want to group your entry points. |
in_objtype1 | INPUT | CHAR(4) | Specifies the main type of resource object on which you want to group your entry points. The type can be CICS, DB2, IMS, or MQ. |
in_objtype2 | INPUT | CHAR(16) | Specifies the secondary type of resource object on which you want to group your entry points. For example, for DB2 it might be TABLE. |
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 CIUSPEPS stored procedure returns one or more result sets. The structure of the result sets is dependent 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.
If you select ALL you get 2 results sets returned. One for the Transaction or Program and one for the Webservice .
For both TRANSACION and PROGRAM type entry points (T or P) it returns a result set, which contains the following DB2 columns:
COLLECTION_ID, APPLID, PLATFORM, APPL_NAME, APL_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.
CICS TS V5.1 supports only PROGRAM entry points.
CICS TS V5.3 supports TRANSACTION entry points.
For both Webservice type entry points (U) 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.
In this case the entry points can be based on the PROGRAM, URIMAP, or the BACK_PROGRAM.
CICS TS V5.1 supports only PROGRAM entry points.
CICS TS V5.2 supports URIMAP entry points.
