Changeman audit program

This step is needed to test the component in your test regions. The audit process verifies whether or not all of your components are in synch.

For example, if no changes are made to a component, the AUDIT will detect that staging and baseline libraries are duplicate. A change package must been in FRZ status before the Approval process can take place. During the installation, CM submits the migration jobs to copy all the components from staging libraries to production libraries. This indicates all current and backup versions have been successfully updated. In the event of a back-out, CM will take the current version 0 generation and copy the -1 version into baseline.

To access a particular package where you have the components to be edited or changed, note the Package number it will be usually like OIN, OIN The below screen is the outline when you enter on the LIST option. If you want to accesses a package OIN Enter the package OIN in the package-id field and hit enter which will display you the package list screen which is displayed below.

There are two types of commands which can be entered first is on the command line and second on the underscores before the package name. Here are some of the command commands which you usually enter on the package prompts. Check out Components Option C1. If a component program or copybook or subroutine, assembler table etc is present in the baseline library which is nothing but the group of changeman Partitioned datasets PDS. A component when checked out into a changeman package should be assigned with a type.

The component type should be correct because as mentioned previously changeman generates JCLS to compile the component automatically. To tell changeman to use the correct procedure to use for compilation we should specify the type. For e. So depending on the type the sources for the baseline library are defined to change.. As discussed previously, For each type we incorporate into a package it will go as member to a partitioned group of datasets created at the time of creating the package.

The following are component types supported by changeman. The following are the corresponding libraries or partitioned datasets which are created for a sample package OIN The following are the baseline libraries that changeman searches when you request change man to check out any component the type and the corresponding datasets searched are also mentioned.

HCA PO HCC PO HC2 PO HCD PO HC4 PO HC5 PO HC6 PO HBA PO HBC PO HB2 PO HB3 PO HBD PO HB5 PO HB4 PO HCM PO DBR PO DBB PO DCL PO RUN PO BLM PO CL6 PO MAP PO CT1 PO CP1 PO JB1 PO PR1 PO LST PO CC1 PO DMS PO XP1 SYS4. Coming back to the steps for checking out the component.

This is done by concatenating all the members in the baseline libraries mentioned above or you can enter even a pattern corresponding to the items, like you want a list of component available in the baseline with starting with PO. If it is yes change man prompts that the component is already checked out in another package specifying the package number.

L - List libraries where component is located. Once this message comes when you are doing an online check out the same has been done by change man. If it is a batch mode then change man will prompt you about the completion of a job which confirms that the check out has been done. Staging a component S1. Specify the location of the component you want to stage in the appropriate fields and as in the check out option specify the library type and language of the component.

The first screen will appear as shown below. The above is initial screen displayed before submitting a job of compilation and link edit. If the program has a DB2 attachment then the next screen will ask you to select the DB2 system where the program is going to be attached. Enter S to select a DB2 subsystem and continue. Enter END command to exit. Use Y or N to select or deselect additional processing options;. The first two fields are generally blank.

Note down the job name and Job number for the reference for any compilation and link edit mistakes. The extra step you should do in the checkout is to edit and recompile so that it will be in ready for testing. Package list is to view the components attached with the package. User variables to be used. For multiple variables, use a semi-colon [;] as a separator. Other separators will be treated as a single user variable.

The Audit step audits a package. The default value is 5. Note: You should set this to a higher value if your requests time out. Use this in conjunction with filters to limit the amount of data returned. For multiple scope applications use semi-colon [;] as a separator. Other separators will be treated as single scope applications. Audit Auto Resolve Indicates whether you want audit to resolve out-of-sync conditions involving copybooks and load modules automatically. Audit Include History Indicates whether to include audit history.

Audit Format Report Indicates whether to format the report by including printer control characters in the output file. This option lets you omit cross-package dependencies from the audit of a participating package and follow rules for simple packages concerning baseline libraries.

Hi Jugi, It seems you did not pick up the latest version of the called program. It may happen that your were trying to audit a package with the corresponding components but missed out to pick up the latest version of any of the compononent from the baseline.

Before auditing the package all the corresponding programs should be taken up from the baseline latest which moved to production recently. I too not confident on this issue, but this could be one of the reason. Please make sure and let us know.

Hi Rajesh, I have taken the latest version of the called program. And moreover, I'm not getting the synch 8 for the other 3 calling programs. It is coming only for 1 calling program.