
CIUSPEP2 Stored Procedure
CIUSPEP2 is a stored procedure that you can use to identify your application entry points for a transaction, program, or web service and group them by the type of the resources they use.
For example, CIUSPEP2 can show you the possible entry points for transaction SSC1 and all other transactions that use MAPSETs, which are used by transaction SSC1.
Syntax
EXEC SQL
CALL CIUSPEP2 (in_calltype, in_collid, in_applid, in_object, in_objtype1, in_objtype2, prc, psqlcode, psqlstate, perrmsg);
EXEC SQL
CALL CIUSPEP2 (‘T’,’%’,’%’,’SSC1’,’CICS’,’FILE’,'MAPSET', prc, psqlcode, psqlstate, perrmsg);
Procedure parameters
There are several input parameters that help you to manage CIUSPEP2 processing and several output parameters that inform you 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). |
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. |
prc | OUTPUT | INTEGER | Return Code |
psqlcode | OUTPUT | INTEGER | DB2 SQL code |
psqlstate | OUTPUT | CHAR(5) | DB2 SQL state |
perrmsg | OUTPUT | VARCHAR(300) | Error message |
in_objtype1 | |
---|---|
CICS | FILE , MAPSET , MAP, TDQUEUE, TSQUEUE, CONTAINER, CHANNEL |
DB2 | TABLE , VIEW , CURSOR |
MQ | QUEUE |
IMS | PCB, PSB |
Returned result sets
The CIUSPEP2 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.
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, APPL_VER1, APPL_VER2, APPL_VER3, APPL_OPER, TRANSID , INITIAL_PROGRAM, BACK_PROGRAM, and OBJECT.
In this case, the entry points can be based on the TRANSACTION , the INITIAL_PROGRAM, or the BACK_PROGRAM.
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, BACK_PROGRAM, and OBJECT.
In this case the entry points can be based on the PROGRAM, URIMAP, or the BACK_PROGRAM.
