This section describes the customization of PAC and PAA. Also described is how to install PAC utilities separately. This information is organized in the following sections:
The sample jobs are prefixed with an operating system identifier and are located in dataset PAC26n.DATA. For a list of sample jobs, see Sample Jobs.
Log on to library SYSPAC and enter MENU at the NEXT prompt.
Select Jobs from the PAC Maintenance Menu to access the Jobs Maintenance Menu.
Modify all jobs that begin with your operating environment prefix (for example, "OS_" for z/OS) to comply with your site's requirements and job standards.
 |
Warning: Do not modify the parameters assigned to @ variables. |
These jobs use the PACBATCH procedure installed from the dataset PAC26n.SRCE.
For more information about modifying, copying, and renaming the sample jobs, refer to the section describing editing jobs in the PAC User's Guide.
PAC 2.5 jobs have been superseded by PAC 2.6.1 jobs. Jobs created using PAC 2.5 sample jobs may not run correctly under PAC 2.6.1. To convert to PAC 2.6.1 as quickly as possible, there are two options:
Using old job names and jobs, or
Using the new PAC 2.6.1 jobs
To use old job names and jobs
Ensure that your existing PAC 2.5 jobs conform to the job steps, work-file assignments, and CMSYNIN control statements in the PAC 2.6.1 jobs.
Review all PAC 2.6.1 jobs to see what you have to change in your existing jobs.
To use the new PAC 2.6.1 jobs
Rename your existing jobs.
Rename the PAC 2.6.1 jobs and tailor them to your site.
Use the SCANPATH utility to change the names of jobs referenced in your migration paths to the names of the customized PAC 2.6.1 jobs that supersede them.
For information about the SCANPATH utility, refer to Scan Utilities, in the PAC User's Guide.
To review Applymods:
Review the PAC Applymods settings and change them as necessary.
Refer to the description of the Applymods in the PAC Administration documentation and the current Release Notes.
To modify the user exits you intend to use
Back up and modify user exits to meet your site's requirements before you copy them to the libraries listed below. Otherwise, unpredictable results may occur. User exits have may have changed with PAC 2.6.1.
Note:
If you do not use the PAC 2.6.1 user exits or if you modify your
existing user exits to conform to the PAC 2.6.1 user exits, expect to receive
NAT0935 errors. Before PAC 2.6.1 will call a cataloged user exit, a PAC
administrator must use the User Exit Maintenance facility in PAC Administration
to activate the user exit.
To copy the user exits:
Use the Natural SYSMAIN utility to copy the user exits (if necessary) to the libraries listed in the table below.
| Prefix | Contents | From Library | To Library |
|---|---|---|---|
| MIGEX* | User Exits, MIGRATE | SYSPACUS | SYSTEM (FNAT) |
| PACEX* | PAC User Exits | SYSPACUS | SYSPAC |
You can customize PAA user exits.
Modify user exits to meet your site's requirements before you copy them to the destination libraries.
Use the Natural SYSMAIN utility to copy the user exits to the libraries listed in the following table.
Important:
Do not copy the user exits you do not intend to use.
| Prefix | Contents | From Library | To Library |
|---|---|---|---|
| MIGEX* | User Exits, MIGRATE | SYSPACUS | SYSTEM (FNAT) |
| PAAEX* | PAA User Exits | SYSPAAUS | SYSPAA |
The PAC utility MIGRATE is provided for loading objects to and retiring objects from locations on remote sites where neither PAC / PAA is installed.
The PAC utility COMPARE will compare both Natural and Foreign objects.
The INPL dataset PAC26n.UTIL contains the Natural modules required to run the utilities MIGRATE and COMPARE. To install and initialize these utilities, perform the following steps:
Step 1: To load the PAC Utilities
Point to the correct FNAT and FUSER files for the Natural environment in which PAA will run.
The PAC utilities are contained in the dataset PAC26n.UTIL.
Assign dataset PAC26n.UTIL to work file CMWKF01.
Load PAC utilities from dataset PAC26n.UTIL to your Natural system file (FNAT) using the Natural INPL utility.
Step 2: To ensure PAC/PAA System Programs are on all FNATs
If multiple FUSER files or separate FNAT and FUSER files will be used, ensure that Step 5: Load PAC/PAA System Programs of a first-time installation is performed on every Natural system file (FNAT) used.
Step 3: To verify Consistent Prefixes
Verify that the modules with the following prefixes are consistent between the Natural system files (FNATs):
PACN*, MIG*, MG*, CF*,COMPARE
You can use the PAC COMPARE utility to verify the modules.
Step 4: To correct Inconsistencies
If inconsistencies are detected in a Natural system file (FNAT), INPL the PAC26n.UTIL dataset into that Natural system file (FNAT) to correct the inconsistencies (See To Load the PAC Utilities).