Month-End Control Card Procedure
Introduction
An important part of preparing the FRS Monthly Schedule is updating the control card members for monthly jobs. Because a large number of control card members is involved, the process has been automated by the use of EXEC's. There are four EXEC's and two OPTION files which govern the control card update process. These EXEC's and OPTION files are maintained on the STUINFO 202 minidisk ('X'disk) and are identified as follows:
EXEC's
These EXEC's perform the actual control card updates and allow a subsequent review of the changes made.
- FRSMNTH1 EXEC X
- FRSMNTH2 EXEC X
- FRSCHK1 EXEC X
- FRSCHK2 EXEC X
OPTION Files
These OPTION files specify the names of the control card members to be changed and are used as input files for the respective EXEC's listed above.
- FRSMNTH1 OPTION X
- FRSMNTH2 OPTION X
The Control Card Update Process
The process for updating control cards monthly is separated into two parts because certain control cards require only standard date changes while other control cards require date and other parameter changes which must be specified individually by the user. These two types of changes are as follows:
Standard Control Card Changes (DATE parameter)
This group of control cards is comprised entirely of DATE parameter change which specify the date to be printed on various month-end reports. The dat used is normally the last day of the month being closed. These changes are processed with the FRSMNTH1 EXEC. The control cards which are processed by this EXEC are identified in the FRSMNTH1 OPTION file. The FRSMNTH1 EXEC retrieves the individual control card members from the 'X' disk, allows the user to input the desired report date just once, and then changes all the control card members automatically.After the changes are made, the control cards are filed on the 'A' disk. Whenthe parameter changes are completed, an option is presented for the user to review the parameter changes that were made (the FRSCHK1 EXEC does this automatically).
Individual Control Card Changes
This group of control cards requires parameter changes which must be determined by the user based on the requirements of the individual jobs. The usual parameters for these jobs are identified in a subsequent section of this this documentation. These changes are processed with the FRSMNTH2 EXEC. The control cards which are processed by this EXEC are identified in the MRSMNTH2 OPTION file. The FRSMNTH2 EXEC retrieves the individual control card members from the 'X' disk and then 'XEDITS' each member so that the user can enter the requiredparameter changes. After the changes are made, the control cards are filed on the 'A' disk. When the parameter changes are completed, an option is presented for the user to review the parameter changes that were made (the FRSCHK2 EXEC does this automatically).
The FRSOPT EXEC Request
Once all the control card changes have been made and reviewed, the user must submit an FRSOPT request form to the UCC Scheduling Dept. so that the control card changes can be processed for the monthly production run. The following sections provide specific details about using these control card change procedures.
FRSMNTH1 EXEC
This exec uses a date submitted by the user to change the date parameter in a specified list of control cards. This list can be found in the CMS file FRSMNTH1 OPTION X. The exec pulls the old control cards from the 'X' disk and files them to the users 'A' disk after changing the date.
NOTE!! You must be linked to the 'X' disk before running this exec.Running the EXEC
- To run the exec type: FRSMNTH1 (enter)
- The screen asks for the date to be entered. This is normally the last day of the month that you are about to process. Enter this in the exact format of MM/DD/YY.
- The exec runs through it's process of changing the date in all the specified control records. When it has completed, it will prompt you with the following screen.
- Option 1 will allow you to check the last control record on the list.
- Option 2 will show you every control record that was updated. As you go through each record you may change it and enter file on the command line, or press PF3 and continue to the next record.
- Option 3 just exits the program.
********************************************************** * * * Enter the date for the month-end reports * * in the following format: * * * * * * mm/dd/yy * * * *********************************************************** |
************************ TASK IS COMPLETE ******************** * * * Choose one of the options below: * * * * 1 - Check only one file * * 2 - Check all the files * * 3 - Exit this EXEC * * NOTE: We strongly recommend that at least one * * file be checked. (option 1) * *************************************************************** |
As it states in the exec we strongly recommend that you at least check one file to make sure that the date is in the correct format.
FRSMNTH2 EXEC
This exec will allow the user to make changes to specific control card members that are needed for month-end processing. It pulls the member from the 'X' disk and puts the user in xedit. Here the member will be changed and filed to the 'A' disk. The members that are pulled can be found in the CMS file FRSMNTH2 OPTION X. NOTE!! You must access the 'X' disk before running this exec.
Running the EXEC
- To run the exec type: FRSMNTH2 (enter)
- As you go through each entry make the necessary changes and enter file on the command line.
- When you have completed changing all the specified control records, the following screen will appear.
- Option 2 will show you every control record that was updated. As you go through each entry you may change it and enter file on the command line or press PF3 and continue on.
- Option 3 just exits the program.
*********************************************************************** * * * This exec will bring up the control members that * * must be changed before Month-End processing. * * Dates must be entered in accordance with the * * individual job instructions. * * * * ** To continue press -------> ENTER * * ** To exit this exec type --> X * *********************************************************************** |
**************** TASK IS COMPLETE ******************** * * * Choose one of the options below: * * * * 2 - Check all the files * * 3 - Exit this EXEC * * NOTE: It is advisable to choose option 2. * ********************************************************** |
As it is noted, we advise that you choose option 2. (We are all subject to human error.)
Individual Control Card Changes
The following is a list of parameter changes for control cards in the FRSMNTH2 exec which must be entered individually by the user. These control parameters must be entered with care as many of them can have an adverse effect on system processing if they are entered incorrectly. This information is included in the descriptions below.- J0276M02
C0276M04 - The TAPE=NNNN parameter normally should be increased by 1 each month. It must match the PO History Tape Label created by PBM092 during the previous month's run.C0276M05 - The PURGEKEY=N parameter is usually set to '1' (purge requisitions). The PURGEDATE=MM/DD/YY parameter is usually back dated 6 months to keep 6 months of requisition history on the PO file. (The day portion of the PURGEDATE parameter should be set to the 10th day of the month.)
- J0315M01
C0315M02 - The PAID-THRU=MM/DD/YY parameter is usually back dated 6 months because 6 months of voucher and check records are maintained in the Accounts Payable module for Bank '10'.C0315M07 - The DATE=YYMMDD parameter is usually back dated 6 months because 6 months of voucher and check records are maintained in the Accounts Payable module for Bank '10'. The date entered in this member should be the same date as the date entered in member C0315M02 (note format difference).
- J0315M08
C0315M8A - The PAID-THRU=MM/DD/YY parameter is usually set to the run date. The TYPE=OUT/RECON/VOID/ALL parameter is usually set to "VOID" to list all the void checks on the system through the run date. - J0316M02
C0316M2A - The DATE=MM/DD/YY parameter is the run date. The INVDROP=MM/DD/YY parameter is the first day of this run month of the previous year which retains a full year's data on the Duplicate Invoice file. This is a critical parameter which, if set incorrectly, could result in the loss of data from the Duplicate Invoice file.C0316M2B - The DATE=MM/DD/YY parameter is the run date. The INVDROP=MM/DD/YY parameter is the first day of this run month of the previous year which retains a full year's data on the Duplicate Invoice file. This is a critical parameter which, if set incorrectly, coulc result in the loss of data from the Duplicate Invoice file. It is critical that the DATE=parameter in the DUMP step match the DATE= parameter in the RESTORE step or else the job will ABEND.
- J0365M02
C0365M02 - The DATE=MM/DD/YY parameter MUST BE THE LAST DAY OF THE MONTH BEING CLOSED. This is a critical parameter which, if set incorrectly, will result in the Report History File being updated improperly.C0365M03 - TheDATE=MM/DD/YY parameter MUST BE THE LAST DAY OF THE MONTH BEING CLOSED. This is a critical parameter which, if set incorrectly, will result in the Processing Month being updated improperly for the new Processing Month.
- J0365R03
C0365R03 - The DATE=MM/DD/YY parameter is normally set to the last day of the month being closed. - J0366M01
C0366M01 - The DATE=MM/DD/YY parameter is normally set to the first day of the month being closed to retain one month's data in the Online Inquiry file. This is a critical parameter which, if set incorrectly, could result in the loss of data from the Online Inquiry file. - J0366M02
C0366M02 - The DATE=MM/DD/YY parameter is the run date. The ZERODROP=YES/NO parameter is normally set to 'YES'. This results in the dropping of individual Account Control records from the GL file and Sub code records from the SL file if the records have zero activity counters and zero dollar fields.C0366M03 - The DATE=MM/DD/YY parameter is the run date. The ZERODROP=YES/NO parameter is normally set to 'YES'. This results in the dropping of individual Account Control records from the GL file and Sub code records from the SL file if the records have zero activity counters and zero dollar fields. It is critical that the DATE= parameter in the DUMP step matchthe DATE= parameter in the RESTORE step or else the job will ABEND.
University of Connecticut