CICS Resource Definition Changes Report package view: layout and example
The package view of the CICS® Resource Definition Changes Report consists of three parts:
- Report options
- Lists the CONNECT, REPORT, and any CRITERIASET batch commands that generated this report. This includes any default parameter values not explicitly specified in the input control cards.
- Summary report
- Lists migrate, backout, and import events that match the criteria specified by CRITERIASET; or all such events in the journal, if no CRITERIASET is specified. The events in the summary report determine the contents of the detail reports.
- Detail reports (one for each change package in the summary report)
- Show all ready, unready, approve, disapprove, migrate, import,
and backout events, regardless of the criteria you specified, for
each combination of change package and migration scheme shown in the
summary report.
The detail reports show the entire recorded history for each combination of change package and migration scheme shown in the summary report: the migrate, import, and backout events from the summary report; other migrate, import, and backout events that do not match your criteria (and so do not appear in the summary report); and events that do not change resource definitions, such as ready, unready, approve, and disapprove. The detail reports do not show install, discard, or newcopy events; to report these events, use a CICS Runtime Resource Changes Report.
If you request the resource level of detail, the detail reports expand the events from the summary report (that is, the events that match your criteria) to show changed resource definitions. If you request the attribute level of detail, the detail reports expand changed resource definitions to show changed attributes.
The following figure shows the layout of the package view and its three levels of detail.

The following figure shows an example package view.
CICS Resource Definition Changes Report
Report Options
CONNECT IPADDRESS=LOCALHOST PORT=10325 SSL=NO
REPORT TYPE=CICSDEFCHANGES,
VIEW=PACKAGE,
LEVEL=ATTRIBUTE
CRITERIASET COND=(DATE>=2007/10/01),
COND=(DATE<=2007/11/30),
COND=(CPID EQ 00000724)
CICS Resource Definition Changes Report
Package View, Summary Level
API
Package Command Scheme RC Date User Description CreateID
-------- --------- -------- -- ---------------- -------- ---------------------------------------------------------- ---------
00000724 MIGRATE DEVTTEST 00 2007/11/01 15:53 JHICKS PAYROLL first system implementation CICSUSER
00000724 MIGRATE TESTPROD 00 2007/11/09 22:12 HKEEP PAYROLL first system implementation CICSUSER
CICS Resource Definition Changes Report
Package View, Attribute Level
Approval External
Package Description Profile Reference CreateID
-------- -------------------------------------------------- -------- -------------------------------- ---------
00000724 PAYROLL first system implementation PAYPROF CICSUSER
Scheme API Command Date User RC Rsn Notes
-------- ----------- ------------------- -------- -- ---- ----------------------------------------------------------
==> DEVTTEST READY 2007/10/31 12:14:39 BSMITH 00 0000
DEVTTEST APPROVE 2007/11/01 11:27:22 JREIBY 00 0000 As MANAGER - fully approved
DEVTTEST MIGRATE 2007/11/01 15:53:10 JHICKS 00 0000
Name Type Group Config Date Func CSD File or Context Name
-------- ------------ -------- -------- ------------------- ------ --------------------------------------------
PAYFILE1 FILE PAYROLL TESTCSD 2007/11/01 15:53:03 Create CICS.TEST.DFHCSD
DESCRIPTION After : Payroll Work File
DSNAME After : PAYROLL.TEST.PAYFILE1
PASSWORD After :
RLSACCESS After : NO
LSRPOOLID After : 1
READINTEG After : UNCOMMITTED
DSNSHARING After : ALLREQS
STRINGS After : 10
NSRGROUP After :
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33 Line(s) not Displayed
PAYFILE2 FILE PAYROLL TESTCSD 2007/11/01 15:53:03 Create CICS.TEST.DFHCSD
DESCRIPTION After : Payroll Work File
DSNAME After : PAYROLL.TEST.PAYFILE2
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41 Line(s) not Displayed
PAYFILE3 FILE PAYROLL TESTCSD 2007/11/01 15:53:03 Create CICS.TEST.DFHCSD
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44 Line(s) not Displayed
PAYFILE4 FILE PAYROLL TESTCSD 2007/11/01 15:53:04 Create CICS.TEST.DFHCSD
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44 Line(s) not Displayed
PAY1 TRANSACTION PAYROLL TESTCSD 2007/11/01 15:53:05 Create CICS.TEST.DFHCSD
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 46 Line(s) not Displayed
PAY2 TRANSACTION PAYROLL TESTCSD 2007/11/01 15:53:06 Create CICS.TEST.DFHCSD
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 38 Line(s) not Displayed
WAITTIMEDD After : 00
WAITTIMEHH After : 00
WAITTIMEMM After : 10
RESSEC After : NO
CMDSEC After : NO
USERDATA1 After :
USERDATA2 After :
USERDATA3 After :
Scheme API Command Date User RC Rsn Notes
-------- ----------- ------------------- -------- -- ---- ----------------------------------------------------------
==> TESTPROD READY 2007/11/06 13:21:07 JHICKS 00 0000
TESTPROD APPROVE 2007/11/07 17:03:28 JREIBY 00 0000 As MANAGER - partly approved
TESTPROD APPROVE 2007/11/08 11:31:42 RWATSON 00 0000 As CCADMIN - fully approved
TESTPROD MIGRATE 2007/11/09 22:12:47 HKEEP 00 0000
- - - - - - - - - - - - - - - - - - - - - - - - - - - - 276 Line(s) not Displayed
***End of Report***
The summary report is sorted by change package ID and event date, and contains the following columns:
- Package
- Change package ID.
- API Command
- API command name.
- RC
- Return code of the API command. (The detail report for each change package contains the reason code, in the Rsn column.)
- Date
- Date and time of the API command.
- User
- ID of the user who invoked the API command.
- Description
- Change package description.
CreateID
ID of the user who created the change package.
The detail report for each change package is sorted by migration scheme and event date. The marker ==> indicates the first event for each migration scheme.
The Notes column in the detail reports shows the approver role specified by an Approve or a Disapprove command, and the resulting approval status of the change package for this migration scheme: "no approvals", "partly approved", or "fully approved".
At the resource level:
- The Func column indicates the function that the API command performed on the resource definition: Cre(ate), Upd(ate), or Del(ete). For example, a Backout command deletes resource definitions that were created by the corresponding Migrate command, and updates resource definitions that were updated by the Migrate.
- The Type column in the resource level uses the resource type naming convention for CSD files, regardless of where the resource definition is stored. For example, for a program resource definition, this column shows PROGRAM, not PROGDEF, even for a resource definition stored in a CICSPlex® SM data repository. For a cross-reference between resource type naming conventions, see Table 1.
If the API command created the resource definition, the attribute level shows the attributes of the newly created resource definition as "after" values, but no "before" values. Conversely, if the API command deleted the resource definition, the attribute level shows the attributes of the resource definition before it was deleted as "before" values, but no "after" values.