Using CA 7/PERSONAL SCHEDULING › Implement CA 7/PS

Implement CA 7/PS

To implement CA 7/PERSONAL SCHEDULING:

1. Define the USERIDs to CA WA CA 7 Edition that will be using CA 7/PS.

   If CA WA CA 7 Edition internal security is being used, the current Security module must be modified to allow access to the PS00 application. The access levels required are shown below. For more information about the internal security module, see the Security Reference Guide

   If command and panel access is being controlled using the CA WA CA 7 Edition External Security Interface, the resource for the new panel may need to be defined to the security package. The USERIDs that will be accessing CA 7/PS must be given access to the CA WA CA 7 Edition application and the resource listed below, with the appropriate access level.

1. Set up the PATTERN jobs.

   The AL2PSBTI member of CAL2OPTN contains sample Batch Terminal commands to define several PATTERN jobs to CA WA CA 7 Edition. The sample commands add them to the CA WA CA 7 Edition database, define their schedules, and RESOLV the schedules. The following is a list of the PATTERN jobs that are defined in the CAL2OPTN member AL2PSBTI:

   DAILY

   Every available processing day of the calendar used.

   MON

   Mondays.

   TUES

   Tuesdays.

   WED

   Wednesdays.

   THU

   Thursdays.

   FRI

   Fridays.

   FIRST

   First day of the month (actual or relative based on the calendar used).

   LAST

   Last day of the month (actual or relative based on the calendar used).

   Before using the AL2PSBTI member as input to the CA WA CA 7 Edition batch terminal, do the following:

   • Verify that no jobs are already defined to the CA WA CA 7 Edition database with the preceding names. If there are, simply change the job names in the sample AL2PSBTI member. Note that the jobs are not going to be scheduled by CA WA CA 7 Edition because their schedules are turned off with the DONT SCHEDULE BEFORE field set to 99999.
   • Supply valid SCAL values where SCAL is specified. The calendar (SCAL) specified will determine whether the FIRST and LAST will be actual or relative days (based on the specification of the OPTIONS=SCHDYONLY value) and whether DAILY will include Saturdays and Sundays or only weekdays.

   After running a batch terminal with the sample member, verify that the commands were processed correctly without errors by examining the job's output. After this verification is complete, the installation is complete and the implementation is well under way.

2. Define Personal Scheduling Defaults Job (optional).

   You may establish a DEFAULTS job specifically for personal scheduling. If you choose not to, defaults are taken from the regular CA WA CA 7 Edition defaults job. For example, you may want all Personal Scheduling jobs to be MAINT=Y while your production work is normally MAINT=N. To establish a Personal Scheduling defaults job:

   • Define the job to the CA WA CA 7 Edition database using the job definition panel. Remember that some information (such as SYSTEM, OWNER, and UID) are always overridden when a Personal Scheduling job is ADDed.
   • In your CA WA CA 7 Edition initialization file, add the following keyword to the DBASE statement:

     DEFAULTPS=jobname

3. Code Personal Scheduling Verification Exit (optional).

   Refer to the Systems Programming Guide for information on adding and implementing an exit to allow you to enforce local standards and conventions.