
CIUSPDEP Stored Procedure
CIUSPDEP is a stored procedure that returns a list of application dependencies, which can be added to a CICS Bundle that is then used to define a CICS Application. CIUSPDEP can be called against a PLATFORM, an APPLICATION, or an OPERATION. It returns information about your CICS, DB2, and MQ dependencies.
For example, CIUSPDEP can show you all of the possible dependencies for the TEST_OPERATIONS application. The TEST_OPERATIONS application 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 CIUSPDEP (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 CIUSPDEP (‘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 dependencies by platform. A for a list of dependencies by application. O for a list of dependencies by operation. |
in_collid | INPUT | CHAR(16) | Specifies the collection ID for which you want to list the dependencies. |
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 CIUSPDEP stored procedure returns five 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.
RESULT SET 1
'CICS DEPENDENCIES BY...',COLLECTION_ID, APPLID, PLATFORM, APPL_NAME, APPL_VER1, APPL_VER2, APPL_VER3, APPL_OPER, TRANSID, "PROGRAM", "TYPE",OBJECT
In this case, the dependency TYPE is described by the TYPE column and the dependency name is in the OBJECT column.
RESULT SET 2
'CICS LIBRARY DEPENDENCIES BY...',COLLECTION_ID, APPLID, PLATFORM, APPL_NAME, APPL_VER1, APPL_VER2, APPL_VER3, APPL_OPER, PROGRAM_NAME, LIB_NAME,LIB_DATASET_NAME
In this case, the dependency is the LIB_NAME and the type is LIBRARY.
RESULT SET 3
'CICS EVENT DEPENDENCIES BY...',COLLECTION_ID, APPLID, PLATFORM, APPL_NAME, APPL_VER1, APPL_VER2, APPL_VER3, APPL_OPER, EVENT_NAME, EVENT_BINDING,EB_ADAPTER
In this case, the dependency name can be either the EVENT_BINDING, or the EB_ADAPTER, or both of them.
RESULT SET 4
'DB2 CONNECTION DEPENDENCY BY...',COLLECTION_ID, APPLID, PLATFORM, APPL_NAME, APPL_VER1, APPL_VER2, APPL_VER3, APPL_OPER, DB2ID
In this case, you are informed that you have a dependency on a DB2 connection definition. You are given the subsystem ID but not the resource definition name.
RESULT SET 5
'MQ CONNECTION DEPENDENCY BY...',COLLECTION_ID, APPLID, PLATFORM, APPL_NAME, APPL_VER1, APPL_VER2, APPL_VER3, APPL_OPER
In this case, you are informed that there is a dependency on an MQ connection definition. The subsystem ID and the resource definition name are not captured. However, you did use an MQ resource.
