ACI Book

CO-ach
Installation Guide
Software Release Information The information in this document applies to the following releases of software: CO-ach.............................................................. Release 2.4 SUPERFILE ....................................................... Release 2.0
1995 by Applied Communications, Inc. All rights reserved. All information contained in this manual is confidential and proprietary to Applied Communications, Inc. No part of this document may be photocopied or reproduced in any manner without the prior written consent of Applied Communications, Inc.
______________________________________________________________________________ 07/97 Applied Communications, Inc. 2
Table of Contents
Section 1....................................First Time CO-ach Installation Section 2................................. Standard CO-ach Configuration Section 3........................................ NetBatch-Plus Installation Section 4..................................Extended CO-ach Configuration Section 5......................................Report Control Configuration Section 6.............................................Configuring RDF Report Section 7.................................................. GO-LIVE Reminders Section 8........................ Information relevant to Sizing CO-ach Appendix A ..........................................Custom CIF Installation Appendix B ..........................................Pre-funding Installation Appendix C.............................. NetBatch-Plus Site Specific Jobs Appendix D.......................... Installing CO-ach with SUPERFILE Appendix E ........................ Configuring CO-ach with SUPERFILE Appendix F ............................................... Modification History
Applied Communications, Inc.
CO-ach
First Time CO-ach Installation
Section 1
CO-ach First Time Installation Procedures Introduction These instructions enable users with a CO-ach version 2.4 release tape to produce a CO-ach application. Plan on at least a full day to complete these installation tasks. More time should be allocated to install the NetBatch-Plus part of CO-ach. The user should know EDIT or TEDIT. Review these instructions thoroughly prior to executing the individual tasks. If any step is not clear, please call Applied Communications, Inc. to clarify the instructions before executing the installation. Some of the instructions contain commands to be entered. These commands are printed on separate lines beginning with the prompt. For example, TACL commands are preceded with the TACL prompt . Enter the specified text after the . If optional add-on products, such as Custom CIF (CCIF), Prefunding(PFND) or SUPERFILE are purchased, the standard install instructions should be completed up to and including step 14. Detailed installation instructions are described in the appendices for the relevant add-on product. Steps 24 thru 27 give reduced instructions for the addon products.
Last Modified 02/24/99
1-1
CO-ach
Installation Steps - Summary 1. Log on. 2. Mount the installation tape and restore the CO-ach files. 3. If purchased, restore the SUPERFILE tape. 4. Move configuration files to the AC24OBEY subvolume. 5. Modify edit commands to define the configuration. 6. Edit the AC24OBEY.TACLCONF file. 7. Load the TACL segment files. 8. Modify the AC24OBEY.TACLCSTM file. 9. Load the TACL segment files. 10. Install the LIBINDEX file and Enable screen. 11. Coldload LIBINDEX & shutdown. 12. Converting the Enform source files. 13. Prepare SCANLOOP file for system compilation. 14. Compile and bind the system. 15. Check for errors in the compilation. 16. Define where the CO-ach system and data files reside. 17. Send Default Table reports to the Spooler. 18. Create CO-ach database files and turn auditing on. 19. Configure Pathway. 20. Bring up the Pathway system and ensure that it functions. 21. Alter the Default Table. 22. Clean up from the installation. 23. Dual Security Option Installing Optional Products - Summary 24. Installing the Optional Products. 25. Enabling Installing Custom CIF Option. 26. Installing the Pre-funding Option. 27. Installing the SUPERFILE Option. 28. Final Install Stage for Optional Features.
1-2
CO-ach
Detailed Instruction Steps Coach 2.4 Detailed Instruction Steps 1. Log On To The Tandem. Instructions: Log on to the designated CO-ach userid which owns the CO-ach files. If a new logon id is created for CO-ach, it should default to the subvolume $x.AC24OBEY. If it does not, use the TACL DEFAULT command to change the logons defaults. Also set the default security to NCNC. Make sure to logoff and then log back on if the defaults are changed to ensure that a TACLCSTM file is created. To change logon id defaults, at the TACL prompt: DEFAULT AC24OBEY, NCNC LOGOFF/SEGRELEASE/ LOGON userid, password The remaining instructions assume the user is creating a new copy of CO-ach on a disk where no prior version exists. 2. Mount The Installation Tape. Instructions: Mount the installation tape without the write ring, and set the tape unit ONLINE. If your using a cartridge, make sure the LOCK SYMBOL is displayed on the front of the cartridge. __ RESTORE/OUT $S.#RESTORE/$TAPEn,$*.AC24*.*,&<Enter> & VOL $X,LISTALL,MYID,TAPEDATE,OPEN,AUDITED ** Do not remove the asterisks from the RESTORE command ** where: the second & is supplied by TACL to indicate command line continuation.
__
1-3
CO-ach 3. Restore Superfile
If the SUPERFILE Product has been purchased enter the following RESTORE command to load the appropriate files. At the TACL prompt: __ RESTORE/OUT $S.#RESTORE/$TAPEn, $*.SF10*.*,&<Enter> & VOL $x, LISTALL, MYID, TAPEDATE, OPEN, AUDITED ** Do not remove the asterisks from the RESTORE command ** Check the spooler #RESTORE jobs for any errors or warnings. A number of alternate key file warnings, *WARNING-7053* At least one alternate key file name references a volume that does not exist, may be generated for the LIBINDEX file and some NetBatch-Plus files. These warnings are normal and require no correction at this point. Prepare To Define The Configuration. Instructions: Move designated files to the AC24OBEY subvolume. At the TACL prompt: __ 5. VOLUME $x.AC24INST FUP DUP (DEFTAB, EDITCONF, TACLCOLD,&<enter> & TACLCONF),AC24OBEY.*, PURGE Defining The Configuration. Instructions: Edit the AC24OBEY.EDITCONF configuration file to define the configuration. This file contains a series of change commands used to modify other files. At the TACL prompt: __ VOLUME $x.AC24OBEY EDIT EDITCONF; XVS F NOTE: The replaced text must be in upper case!! What Will Appear: There will be a series of change commands. Each has three quote symbols. The text on the left of the middle quote is in lower case, while the text on the right
Last Modified 02/24/99 Applied Communications, Inc. 1-4
4.
CO-ach
First Time CO-ach Installation of the middle quote is in upper case. When these commands are executed, the lower case text is changed to the upper case text. This way, text which was previously changed will not be accidentally changed again because the upper case text, which has already been changed, will not match the lower case text which will be changed in the subsequent commands. What to Change: In each of these commands, the upper case text to the right of the middle quote needs to be changed to whatever is correct for the system. The replaced text must be in UPPER CASE. This file contains the following commands: change change change change change change change change change change change change change change where: $MYVOL The volume where most of the subvolumes will reside. (Individual subvols can be changed using the screen editor) The subvol prefix where the CO-ach system source files reside. This command should not be changed for a production system. A test system can be installed to TC24*.* subvols. The volume where the CO-ach database will reside. The default data subvol prefix is ACH. During the
Applied Communications, Inc. 1-5
all all all all all all all all all all all all all all
$x$MYVOL all uuAC all $a$DATAVOL all wwwACH all pP all yA all $z$SCRTCH all $t$OPSTERM all $c$S all #1#PRTR all $n$NBP all oCOACH.OWNER all r2 all v4 all
AC
$DATAVOL ACH
CO-ach
First Time CO-ach Installation installation and test cycle of the CO-ach product, it may be necessary to create a test system that can easily be identified as a test system. The data subvol prefix can be changed to TST for example. Note: the number of characters in the change command must not change from 3. P The first letter of pending file output subvols. Subvol name will be of the form P1nnnnnn. Note: The letters A and R are reserved. They must not be used for pending file subvols. The first letter of all process names (after the $). This may be any letter, including A. This will be prefaced to process names. Using different first letters for different applications (or versions of the same application) helps avoid conflicts between process application names. Verify the letter is not being used for other process names. Avoid using X, Y, or Z; these are normally reserved for Tandem use. The name of a volume to be used as a scratch (work disk) disk. It can be the same as $MYVOL. The name of a terminal/process used to monitor the system. Error logging can appear on this terminal. The Spooler collector to be used for compilation. Some Tandem users prefer to use a special collector for large Spooler jobs so that the regular collector does not become full. The printer location to be used for Pathway screen prints. This may or may not be linked to an actual printer. Individual terminals may be assigned different printers using the PATHTERM file. The name of the Pathmon process for NetBatchPlus. Check with the system administrator to
$SCRTCH $OPSTERM $S
#PRTR
$NBP
CO-ach
First Time CO-ach Installation determine the proper process name. COACH.OWNER The users system logon id for the owner of the CO-ach system. Pathway and NetBatch-Plus will operate under this logon, so all the files will be owned by this user. 2 The current release of the product is 2.4. THIS ENTRY MUST NOT BE CHANGED. It is used when converting the DEFTAB file. The current version of the product is 2.4. THIS ENTRY MUST NOT BE CHANGED. It is used when converting the DEFTAB file.
4 __
When finished making these changes, exit the edit session: <Shifted F16> (to exit XVS mode) * EXIT (to exit EDIT) 6. Prepare The Configuration File. Instructions: Edit the AC24OBEY.TACLCONF file using the EDITCONF file: VOLUME $x.AC24OBEY EDIT TACLCONF; OBEY EDITCONF Results: The edit commands prepared previously will execute. This should result in a configuration file close to the required format.
Additional Tuning Instructions: Browse through the file for other items to change. Most of the items just changed do not need further attention. If configuring a production system, consider changing file locations to distribute the system. It is recommended that only the AC24OBJ, AC24LOAD, or ACHDATA subvolumes be changed to a different volume. The following items should be considered for further changes:
CO-ach
First Time CO-ach Installation CPU_SELECTION_LIST This determines which CPUs will be used during compilation. For faster compiling, extend this list to include all available CPUs. DEFAULT_TABLE This file contains detailed configuration information including data file names. (It will be created later in these instructions.) OBJSEARCHLIST For a test or production system, this does not need to be changed. It may be used for a development system on which only a subset of the modules are compiled. This allows modules to be bound from another complete system. Insert the subvolume names of the complete system as indicated. PROGRAM_FILE_SECURITY This determines the security applied to the compiled program files. When done, exit the edit session: <Shifted F16> (to exit XVS mode) * EXIT (to exit EDIT) Load The TACL Configuration Files. Instructions: Load the TACL segment files. The configuration in the previous step is loaded along with other TACL routines. At the TACL prompt:
7.
__
VOLUME $x.AC24OBEY RUN $x.AC24OBEY.TACLCOLD TACLCONF Prompts: TACLCOLD will prompt the user if the files it will create already exist. The first time answer Y to all prompts. Subsequent times, certain steps may be skipped if no changes have been made. The last step (editing AC24OBEY.TACLCOOL) should be done during subsequent runs if there were changes to
CO-ach AC24OBEY.TACLCONF. Errors:
TACLCOLD checks for conflicts between the variable names in TACLCONF and TACL variables that are previously defined outside the CO-ach application. If such a conflict exists, call Applied Communications Inc. for suggestions on resolution. Note: When TACLCOLD finishes, the warning shown below is displayed after the ASSIGN statement and is acceptable:
*WARNING* $x.ACHDATA.DEFTABLE DOES NOT EXIST 8. Add A TACLCOOL Command To The TACLCSTM File. Explanation: The TACLCOOL file created in the previous step is used to set up the TACL configuration every time a user logs on. It attaches the TACL segment files loaded in the previous step. A TACLCOOL command should be placed in the AC24OBEY.TACLCSTM file. Use a copy of an existing TACLCSTM file if one does not exist in AC24OBEY. Logging off and back on should also create a TACLCSTM file if the system user id defaults to the AC24OBEY subvolume. When obey files are used as TACL input files, the AC24OBEY.TACLCSTM file is used by the new TACL during its logon sequence. Optional: If the system is set up to run with DataExpress, add the necessary DataExpress ASSIGN to the TACLCSTM file. Otherwise do not add the assign statement to the file.
Instructions: Add the TACLCOOL command and optional DataExpress ASSIGN. At the TACL prompt: VOLUME $x.AC24OBEY EDIT TACLCSTM *ADD LAST xxx RUN $x.AC24OBEY.TACLCOOL
CO-ach __ xxx //
If DataExpress has been purchased: *ADD LAST xxx ASSIGN DX-DEFAULT-TABLE, $v.sv.DEFTABLE xxx // ___ *EXIT where: xxx, supplied by the editor, is the last line number in the file. $v.sv is the volume and subvolume where the DataExpress DEFTABLE file resides. Possible Exceptions: If the default subvolume of a users logon is different from $x.AC24OBEY, place the TACLCOOL command in the default TACLCSTM file as well. (The default TACLCSTM file is in the default subvolume of the logon.) If this is not done, the user must use the TACLCOOL command each time the user accesses CO-ach. Loading The TACL Configuration Instructions: After making these changes to the TACLCSTM files, log off and back on. The TACL configuration for COach is displayed after logon. When logging off, release the TACL segment files. At the TACL prompt: __ LOGOFF/SEGRELEASE/ LOGON userid,password Warnings: When TACLCOOL is invoked during the next few steps, there will be a warning about a missing Default Table or a missing program file PSX000. This refers to the CO-ach Default Table, not the DataExpress Default Table. This warning is normal and will be corrected in a later step.
9.
10.
Load The Module Description Table. Explanation: Install the LIBINDEX file and Enable screen. This
1-10
CO-ach
First Time CO-ach Installation file contains information about how to compile each module. The user is able to specify certain compile options for all modules. There is also an Enable screen used to modify the compile options of individual modules. The TACL COMPILE routines included with this release use the LIBINDEX file to determine how to compile each module. In this way, it is only necessary to give the COMPILE routine the name of a module to have it compiled correctly. The LIBINDEX Enable Pathway may be used to make changes to the compile options (for example, when changing the SUPPRESS option on a particular module) or to add new modules. Otherwise, it may not be necessary to use the LIBINDEX Enable screen, but it is good to have it ready just in case. Instructions: The LIBINDEX file is moved from the AC24INST subvol to AC24LIB. While it is being moved, the SUPPRESS, SYMBOLS or INSPECT options can be added if required. In the following command, brackets are used to show the choices. The brackets themselves should NOT be typed. Square brackets [ ] are used for optional choicesuse only one, or none, of the choices. Curly brackets { } are used for required choiceschoose one or the other, but do not omit. Place a space between each choice. At the TACL prompt:
__
VOLUME $x.AC24INST NEWINDX [SUPPRESS ] { SYMBOLS } { INSPECT } [NOSUPPRESS ] { NOSYMBOLS }{ NOINSPECT} where: The SUPPRESS/NOSUPPRESS option defaults NOSUPPRESS. This controls whether compiles produce a complete listing {NOSUPPRESS} or just error/warning messages and a summary at the end {SUPPRESS}. Either SYMBOLS or NOSYMBOLS must be specified. This controls whether a symbol table for Inspect is
1-11
CO-ach produced.
Either INSPECT or NOINSPECT must be specified. This controls whether Inspect or Debug will be used when the process traps or encounters a breakpoint. Prompt: NEWINDX will prompt the user if the file it creates already exists. The first time answer Y to the prompt. Subsequent times, answer Y or N. If responding Y, the $.AC24LIB.LIBINDEX file is overwritten.
For example, on a test system where listings are required, use: NEWINDX NOSUPPRESS SYMBOLS INSPECT For a production system where listings are not required, use: NEWINDX NOSYMBOLS NOINSPECT The last thing NEWINDX does is to move the LIBCONF file from AC24INST to AC24LIB. Check Point: Start up the Pathway for the LIBINDEX Enable screen. This ensures that the LIBINDEX data really exists, and to be sure the Enable screen works. Cold start the LIBINDEX Enable Pathway. Instructions: At the TACL prompt: VOLUME $x.AC24LIB LIBDDLC PERUSE (when complete, check the spooler job for any errors) _LL (List Last on spooler job #LIBDDLS. Look for any errors) _EXIT LIBENABC PERUSE (when complete, check the spooler job for any errors) __ _LL (List Last on spooler job #LIBENBS, you will see Program Generated if the program has been successfully generated.) _EXIT
Note:
11.
__ __ __
CO-ach
First Time CO-ach Installation Run the LIBINDEX Enable screen and start the pathway, at the TACL prompt:
__
LIBCOLD VOLUME $x.AC24LIB RUNINDX Press F4 to view the first data record (If no error messages are displayed, then the Enable screen works correctly) Press SF16 to exit.
__
Shutdown the LIBINDEX Pathway. At the TACL prompt: __ VOLUME $x.AC24LIB LIBSTOP Once the LIBINDEX Pathway is configured, LIBCOOL may be used to re-start it. At the TACL prompt: __ 12. VOLUME $x.AC24LIB LIBCOOL Converting The Enform Source Files. Explanation: The Enform source files must be converted to contain correct volume and subvol names. Instructions: At the TACL prompt: VOLUME $x.AC24OBEY CONVERT AC24INST.CHKENTRY TO AC24ENF CONVERT AC24INST.CHKP50C TO AC24ENF CONVERT AC24INST.DEFTABLE TO AC24ENF CONVERT AC24INST.ENTRYCTL TO AC24ENF CONVERT AC24INST.RSKPEND TO AC24ENF CONVERT AC24INST.SAUD0 TO AC24ENF CONVERT AC24INST.SAUD1 TO AC24ENF CONVERT AC24INST.SAUD2 TO AC24ENF Results:
___
AC24INST.CHKENTRY
(78)
1-13
CO-ach AC24INST.CHKP50C AC24INST.DEFTABLE AC24INST.ENTRYCTL AC24INST.RSKPEND AC24INST.SAUD0 AC24INST.SAUD1 AC24INST.SAUD2
First Time CO-ach Installation (144) (286) (83) (386) (137) (89) (70)
1-14
CO-ach 13. Prepare For System Compilation.
Explanation: The AC24INST.COMPALL file is used to compile and bind the system. COMPALL starts a second TACL using AC24INST.SCANLOOP, which scans the resulting compiler listings for errors and, depending upon its options, will automatically delete error-free compiler listings in the spooler. Copy SCANLOOP from AC24INST to AC24OBEY. Instructions: At the TACL prompt: __ VOLUME $x.AC24OBEY FUP DUP $x.AC24INST.SCANLOOP, *, PURGE Optional: SCANLOOPs default option will not delete any compiler listing jobs in the spooler. Edit SCANLOOP, as shown in the next set of commands, and remove the pairs of equal signs, which will cause SCANLOOP to delete jobs that are OK and/or have only WARNINGS. Doing so can help keep the spooler from getting too full. DO NOT do this if all of the compiler listings should be kept!
Instructions: At the TACL prompt: EDIT SCANLOOP If OK and WARNING compiler listings are to be deleted, enter in UPPER CASE: *CHANGE == OK *CHANGE == WARNING If the WARNINGs are to be kept and the OKs deleted, enter: *CHANGE == OK __ *EXIT (to exit EDIT)
1-15
CO-ach
14.
Compile And Bind The CO-ach Run-Time Modules. Optional: If optional add-on products are purchased, such as Custom CIF (CCIF), Pre-funding (PFND), or SUPERFILE, see steps 24 through 28 for instructions on installation before doing a full system compile. NOTE: If using the dummy SFUTIL, make sure the object file resides on AC24SUPR.
DataExpress Instructions: If the site is using Data Express as its file transfer vehicle, change the AC24BIND.PSX010 and AC24BIND.PSX020 files by removing the comment marks (see bold comment in the example below) from the lines specifying the location of the Data Express object files. Example:
comment comment comment comment ADD CODE CSEXCUPD FROM $vol.subvol.CSEXCUPD,DELETE SELECT SEARCH ($vol.subvol.CONVDATE) SELECT SEARCH ($vol.subvol.INITGC ) SELECT SEARCH ($vol.subvol.EAQSVR )
If the object files do not reside on the specified AC24DX subvol, change the $vol.subvol specification appropriately. Instruction: To start the compiles, at the TACL prompt: __ VOLUME $x.AC24OBEY ASSIGN TACLCSTM, $x.AC24OBEY.TACLCSTM TACL /IN $x.AC24INST.COMPALL,OUT & $S.#TACL.COMPALL,NOWAIT,NAME/ where: the second & is a TACL command line continuation $s is the spooler collector to be used for compilation. Warning: MONITOR THE SPOOLER TO MAKE SURE IT DOESNT GET TOO FULL!!
Considerations: TACL must be started as a named process and the TACLCSTM file must invoke TACLCOOL. The
CO-ach
First Time CO-ach Installation above command instructs TACL to generate a random process name. Specific process name may also be used. The system monitor terminal should be kept paused because the compiler may attempt to display an error message on its home terminal, which is changed by COMPALL to be the system monitor. Results: The following steps execute: TACL home term changed to system monitor (SYS_TERM) A second TACL is started to scan the compiler listings for errors A DELETE macro/job is started which deletes jobs that compiled without errors or some acceptable warnings. The DDL source is compiled into the dictionary The copy libraries are produced from the dictionary The TAL subroutines are compiled The global TAL libraries are bound The COBOL subroutines are compiled The COBOL subroutine libraries are bound The TAL, COBOL, SCOBOL, ENFORM & ENABLE programs are compiled The COBOL programs are bound The DDL, TAL, COBOL, and SCOBOL Spooler output scanned for errors, and the Spooler LOCATION name is changed accordingly Problem Resolution: The TACL can be suspended when an early compile problem will cause problems in later compiles. If compile problems occur, suspend the TACL just started - the lower named process of the two TACLs - using the following command: SUSPEND $<tacl process name> While the TACL is suspended, fix the compile problems. When the TACL is reactivated, the compiles resume execution without starting from the beginning. Enter the following command to activate the TACL: ACTIVATE $<tacl process name>
1-17
CO-ach
First Time CO-ach Installation To re-compile individual modules, at the TACL prompt: COMPILE /BIND/ <module name> <module name> where: <module name> is the name of the module to be compiled. Do not use the volume or subvolume name. To re-bind individual modules which are already compiled, at the TACL prompt: COMPILE /BINDONLY/ <module name> <module name> ... where: <module name> is the name of the module that was compiled. This may differ from the load module name. In the case of object libraries such as COBLIBA, COBLIBB, etc., use the name of only one subroutine that needs to be bound into the library. Do not use the volume or subvolume name. Note: If installing CO-ach with SuperFile, this is a good time to begin the SuperFile Configuration listed in Appendix E. Check The Spooler For Compilation Errors. Instructions: As compiles complete check the spooler jobs for errors. The SCANLOOP command file, previously defined contains SCANCOMP commands to check the summary of errors on the last page of most compiler listings. After checking the summary, SCANLOOP changes the location names to either #OK, #WARNING or #ERROR. Depending on SCANLOOPs option settings, the #OK and #WARNING jobs may already be deleted at the end of the system compile. Normal Warnings: Enable/Enform Messages: Enable and Enform listings must be checked manually because they do not summarize the errors at the end of the compile listing.
15.
1-18
CO-ach
First Time CO-ach Installation Check each Enform listing in the spooler for any error (!!! ERROR) or warning (*** WARNING) messages and correct before recompiling. Enable modules will have warnings when initially compiled, but do not cause any problems. If the message Program generated <PN> does not appear on the last page of each Enable listing, the program was not created properly and must be corrected before recompiling. TACLLIB Message: During the system compile, a warning message comes from the TACLLIB peruse job. This happens because the endpoint record has a redefine of the ep-tran-amt-limit field. We need the output of endpoint for the distproc tacl macro. The following warning message is okay from TACLLIB:
*** WARNING *** TACL OUTPUT DIAGNOSTICS: *** WARNING *** Unsupported data type in element EP-TRAN-AMT-LIMIT-NUM
ENABLE Message:
*** WARNING *** DELETE has been SET OFF for this box because of filetype
Other Messages: When the system is first compiled, it is normal to have COBOL 390 warnings about missing object modules with respect to COBOL subroutines. This is due to subroutines calling other subroutines that have not yet been compiled. Once a complete set of object files has been compiled, these warnings should not appear when the modules are recompiled. The modules generating these warnings (the specific modules listed may vary as the product evolves) during the first system compile are: LTXNIO PSXS0004 PSXS0012 PSXS0035 PSXS0057 PSXS0090 TXNDSTAT MATCH PSXS0005 PSXS0024 PSXS0044 PSXS0061 PSXS0095 TXNDIO PSXS0000 PSXS0006 PSXS0031 PSXS0045 PSXS0067 PSXS0122 TXNIO PSXS0001 PSXS0008 PSXS0033 PSXS0054 PSXS0072 RSKPROC TXNDMAP
The PSX010 and PSX020 modules will have COBOL 390 compiler warnings because they may be using Data Express subroutines.
CO-ach
First Time CO-ach Installation warnings because they may be using Data Express subroutines. Check Point: The following command will check the AC24OBJ and AC24LOAD subvolumes to make sure all of the TAL, COBOL, ENFORM, and ENABLE modules have been compiled.
__
Instructions: At the TACL prompt: CHECK_COMPILES Results: CHECK_COMPILES reads the LIBINDEX file and looks for the expected language specific module. For TAL and COBOL85 modules, it checks for a file in the AC24LOAD subvol, provided there is a corresponding file in the AC24BIND subvol. For ENFORM modules, it looks for a file in the AC24LOAD subvol; for ENABLE modules, it looks for a file in the AC24PATH subvol (the Pathway configuration file); for SCOBOL modules, it looks at the module in AC24LOAD.POBJ using SCUP. This command displays, on screen, any object files which do not exist or are more than three days old from the date/time specified. And will display the source file if it has been modified AFTER the object was compiled. A different date and time may be used with CHECK_COMPILES. CHECK_COMPILES 10 JUL 95, 10:30 The following sample output was obtained after installing CO-ach 2.4 with both CCIF and PreFund enabled, and with symbols turned on in the compile options. Depending on the options you have enabled, your output may differ. Sample Output: --- CHECKING FOR COMPILED FILES SINCE <date, time> ----------------------------------------------
Example:
For example, at the TACL prompt:
1-20
CO-ach
__
Source files checked = 316 Copy files checked = 4 Object files checked = 235 Run unit files checked = 230 Scobol units checked = 61 Enable files checked = 9 Enform files checked = 4 Errors counted = 0 ------------------------------------------------ DONE CHECKING COMPILED FILES --Note: These numbers may vary but the Errors Counted must equal 0. To manually delete remaining #OK jobs from the spooler, execute the following command at the TACL prompt:
___
SPOOLCOM JOB (OWNER, LOC #OK), DELETE ! Also delete any remaining #WARNING jobs after checking for allowable warnings (see Normal Warnings). Save #ERROR jobs until the compile problems have been fixed. Last Step: After compiling and error checking, reload the TACLSEGF.
Instructions: At the TACL prompt: VOLUME $x.AC24OBEY RUN $x.AC24OBEY.TACLCOLD TACLCONF Answer Y (yes) only to the TACLSEGF and TACLCOOL prompts. 16. Define The Application Residence. Explanation: Define where the CO-ach system and data files reside, so that these Installation Procedures run appropriately. A copy of the Default Table is supplied as an edit file and can be configured for the sites own installation.
CO-ach
First Time CO-ach Installation It contains the name of each data file used by the system, as well as some subvolume names and process names. There is an Enable screen used for later modification of specific entries. For now, it is easier to simply use the editor. Instructions: Use the EDITCONF obey file to change the volume names, as was previously done with the TACLCONF file. At the TACL prompt:
__
VOLUME $x.AC24OBEY EDIT DEFTAB;OBEY EDITCONF *EXIT Additional Tuning: If the data files are to be distributed across multiple volumes, make these changes now. However, there will be an opportunity to use an Enable screen later to edit individual entries which may be easier since Enable will show labels for each entry. Be careful to not change the text positions. On some lines, there is more than one item and the positions of the additional items are important. DO NOT delete or insert any lines. Instructions: Now load the edit file into the actual Default Table. At the TACL prompt:
__
VOLUME $x.AC24INST OBEY LOADDEFT After making changes to the Default Table using the enable screen, the AC24OBEY.DEFTAB file should not be used; otherwise, the changes made directly to the Default Table will be lost. Produce The Default Table Reports. Instructions: Run the Default Table Report to see the Default Table settings. At the TACL prompt: Warning:
17.
1-22
CO-ach
__
VOLUME $x.AC24OBEY OBEY DEFTRPT Results: This will produce several ENFORM jobs in the Spooler, each showing a different part of the Default Table. The global and module parts are reported separately and each is split into several jobs because ENFORM cannot handle records the size of the Default Table in one report. These reports should be checked for full verification. These reports will be used later if there are any modifications made to the Default Table. At this point, it is okay to leave the reports in the spooler.
18.
Create The Database Files And Turn TMF Auditing ON. Instructions: Enter the following command to create the Database and to turn auditing on. At the TACL prompt: __ VOLUME $x.AC24INST OBEY CREATE Results: Information that is output from the CREATE function will appear on the screen, as well as in the Spooler. An error 80 reported during file creation indicates that the TMF system is not operating. This must be corrected before continuing. Be sure to check the spooler output report for NO ERRORS.
19.
Configure The CO-ach Pathway Environment. Instructions: Create the configuration files using these commands at the TACL prompt: __ __ VOLUME $x.AC24OBEY CONVERT AC24INST.PATHCONF TO AC24OBEY CONVERT AC24INST.ENABCONF TO AC24OBEY
CO-ach Results:
First Time CO-ach Installation AC24INST.PATHCONF - 697 records AC24INST.ENABCONF - 93 records
Additional Tuning: Alter the resulting files as necessary. The following table shows possible changes. Generally, the previous processes should have resulted in a correct Pathway configuration, but it is better to double check. Instructions: Use EDIT or TEDIT to view the file named in the left column. At the TACL prompt: __ VOLUME $x.AC24OBEY EDIT <file>; XVS F Look for the items mentioned in the right hand column of the below table: FILE: PATHCONF TYPE OF FILE: WHAT TO CHANGE: PATHWAY HOMETERM Config file PRINTER Spooler output names Process names Node Names/Volume Names PATHWAY Config file
20.
HOMETERM PRINTER Spooler output names Process names Node Names/Volume Names Explanation: Establish the valid Tandem volume(s) for the pending control files created by CO-ach. This step is especially necessary if you WILL NOT BE RUNNING THE IVP. Instructions: VOLUME AC24OBEY O PATHCOLD O PDCONFIG n Fkey: F4 (This file is empty) n PENDC-VOLUME [01]
ENABCONF
1-24
CO-ach n PENDC-ENTRY n Fkey: n Fkey:
First Time CO-ach Installation enter $volume where ACHDATA resides F10 (Insert Record) SF16 (Exit PDCONFIG File)
21.
Expected results: A message will be displayed at the bottom of the screen stating Record inserted ok. Perform The Initial Pathway Verification. Instructions: The initial set of Operator Ids and passwords are kept in AC24XTRA.OPERID. This data needs to be loaded into the CO-ach database. At the TACL prompt: VOLUME $x.ACHDATA FUP ALTER OPERID, NO AUDIT FUP LOAD AC24XTRA.OPERID, OPERID Ignore any FUP OPEN ERROR 4 messages. Expected results: RECORDS LOADED: 9 FUP LOADALTFILE 0, OPERID Expected results: PRIMARY RECORDS READ: 9 RECORDS LOADED: 9 FUP ALTER OPERID, AUDIT Instructions: Move the initial date file to the CO-ach database: __ FUP DUP AC24XTRA.DATETDY, ACHDATA.*, PURGE FUP ALTER ACHDATA.DATETDY,AUDIT Instructions: Run the ONLINE Pathway. At the TACL prompt: ONLINE Logon as the user specified below and verify access. n USER NAME 00000001
1-25
__
CO-ach __
First Time CO-ach Installation n PASSWORD AAAAAAAA n Press F1 (Log On) If the system displays the Main Menu Screen, CX01, then log off: n Shift-F16 (returns to the Logon screen) n Enter EXITPROG in the USER NAME field n Press F1. If the system displays the Change Password Screen, SE01, refresh the password: n n n n n n n n Enter OLD PASSWORD AAAAAAAA Enter NEW PASSWORD BBBBBBBBB F14 (UPDATE) Enter NEW PASSWORD BBBBBBBBB F14 (CONFIRM) Shift-F16 (return to the Logon screen) Enter EXITPROG in the logon id field F1 (Log Off)
__
Instructions: If the Pathway is not needed for other purposes, it may be shut down. To stop the pathway, at the TACL prompt: OBEY PATHSHUT Instructions: To start the ONLINE Pathway after configuration, at the TACL prompt: __ VOLUME $x.AC24OBEY OBEY PATHCOOL Instructions: To access ONLINE Logon Screen when the pathway is running, at the TACL prompt: VOLUME $x.AC24OBEY ONLINE Perform Adjustments To The Default Table Instructions: Alter the Default Table. After checking the Default Table reports printed in step 17, make any necessary adjustments using Enable.
22.
CO-ach
Explanation: There are two Enable screens for records in the Default Table. The first screen, DEFTABGL, is for the global records, where the program name is blank. The second screen, DEFTABMD, is for the remaining module records, where a module name, job name, or report name is entered as the program name key. Instructions: The commands to run the Enable screens are, at the TACL prompt: __ __ VOLUME $x.AC24INST OBEY DEFTABGL OBEY DEFTABMD Instructions: PATHWAY must be running in order to access to the DEFTABLE. __ n In Enable n F4 reads the first record (only be used for DEFTABGL) __ The program name field should always be blank when reading the Global Default Table. n F6 reads a record by key (program name and database index) Always enter the program name when reading the Module Default Table. n F14 updates a record with any changes. NOTE: If any changes are made to the location of data files, the files must be moved using the FUP RENAME or FUP DUP commands. Remember to move any related alternate key files and properly adjust the related altfile attributes.
1-27
CO-ach 23. Perform The Installation Cleanup
Instructions: This step is to clean up from the installation, including Spooler jobs and files. After verifying that the system was built successfully, clean out the installation outputs from the SPOOLER queue. Use the job delete commands from within PERUSE to purge files that the user does not want to print At the TACL prompt: __ 24. OBEY AC24OBEY.CLRZZ This is the end of the CO-ach Installation Process. Enabling The Dual Security Option. Explanation: The Dual Security feature is delivered with the standard product but is not enabled. To enable the Dual Security feature, a configuration change must be made to a Security record using the Online system. All operators except the operator tasked with enabling Dual Security should be logged off of the Online system. Instructions: Using Step 20 as a template, ensure that the Pathway system is running and logon to the Online system. Go to the DEFINE DUAL SECURITY PROFILE screen - SE03: __ Press HOME Enter SE03 F1 Enter Y in the field to the right of each specific file or function to enable Dual Security F14 (UPDATE)
Be aware that all Files or Functions enabled for Dual Security require a second operator to take action on the initial request using EX07 - DUAL SECURITY APPROVAL.
1-28
CO-ach 25. Installing the Optional Products.
The CO-ach Application also has a number of Optional add-on cost features: 1. Custom CCIF 2. Risk Management with Pre-funding Step Installing Custom CIF Option. (CCIF) (PFND)
26.
Instructions: See Appendix A. The Custom CIF feature is delivered on a separate subvolume, AC24CCIF. Ensure the AC24CCIF subvolume exists and then invoke the macro to install this feature. At the TACL prompt: ___ AC24CCIF.INSTALL The Global Deftable record has been provided with the assign DF-CCIF-FILENAME filled with the location of the CCIF file (e.g., $x.ACHDATA.CCIF). It is OK if the peruse report created by the INSTALL macro lists an error stating that the Pathmon process does not exist. (See Appendix A for more detail.) Once all the required add-on products have been installed, go back to Step 14. 27. Installing The Pre-Funding Option. Instructions: See Appendix B. The Pre-funding option is delivered on a separate subvolume, AC24PFND. Ensure the AC24PFND subvolume existsand then invoke the macro to install this feature. At the TACL prompt: ___ AC24PFND.INSTALL Once all the required add-on products have been installed, go back to Step 14.
1-29
CO-ach 28. __ Installing The SUPERFILE Option.
Instructions: Refer to Appendix D - Installing CO-ach with SUPERFILE. Once all the required add-on products have been installed, go back to Step 14.
29. __
Final Install Stage For Optional Features. Ensure that all CO-ach processes and the Pathway system are not running, then follow the procedures set out in Step 14 to perform a system compile.
1-30
Section 2
Standard CO-ach Configuration Overview The CO-ach First Time Installation Procedures leads the user through a vanilla installation of the CO-ach software. BASELINE does not include the Custom CCIF (CCIF), Pre-Funding (PFND) or SUPERFILE which are purchased separately as add-on products. Dual Security is installed as part of the CO-ach First Time Installation Procedures, but is configured as DISABLED. The Dual Security feature is activated on the SE03 screen of the On-line subsystem. The initial record is read by pressing the F13 key. The files/functions which are to have Dual Security enabled must have the option set to 'Y' and the security record must be updated by pressing the F14 key. Careful consideration should be used when enabling the Dual Security as once enabled, a second operator will be required to either Approve or Deny a file update request (from the EX07 screen). Before any On-line file maintenance can be performed, a Host Processing Center (HPC) record must be added using the USERTRX data file and the PSX200 module must be executed (Refer to the Installation Verification Guide for an example of the procedures to follow). An alternative method to adding an HPC record is to start the On-line subsystem, entering the HPC data at the CF01 screen and then executing the RUNDCM NetBatch-Plus Job. The data files created during the First Time Installation use the FUP command files on the AC24FUP subvolume. These files may be edited to reflect the sites specific transaction volumes and the data files created.
______________________________________________________________________________ 07/97 Applied Communications, Inc. 2-1
CO-ach
Standard CO-ach Configuration
This page intentionally left blank.
______________________________________________________________________________ <draft> Applied Communications, Inc. 2-2
CO-ach Section 3 NetBatch-Plus Installation INTRODUCTION
NetBatch-Plus Installation
These instructions will help the user install the CO-ach NetBatch-Plus (NBP) database. The NBP database may be installed using either Procedure 1 or Procedure 2. Procedure 1 uses the NetBatch-Plus database that resides on the CO-ach release tape. This procedure should be used when the user's current NBP database does not exist or is very small. The first procedure will replace any previous NBP job specific information with the CO-ach data. The user will then need to manually re-add any previous data. Procedure 2 requires manually adding all the NBP Jobs and Parameters using the Enform reports included with the CO-ach Installation Package. The second procedure is used when a large NBP database currently exists and the users do not want to re-add previous data. PROCEDURE 1 Procedure 1 uses the NetBatch-Plus (NBP) database included on the CO-ach release tape. The CO-ach First Time Installation Procedures should have restored the NBP database and associated macros to subvolume $x.AC24NBP. The NBP database files in $x.AC24NBP are used to overlay the existing NBP database. Assumptions: The NetBatch-Plus product is already installed and operational. The users have access to the NetBatch-Plus Reference Manual in case there are questions on NBP concepts or NBP operations. Warning: Procedure 1 is destructive to any previous data that resides in the NetBatch-Plus database. Procedure 1 does save the existing NBP database to the NBPSAV subvol before
______________________________________________________________________________ 02/24/99 Applied Communications, Inc. 3-1
CO-ach
NetBatch-Plus Installation installing the CO-ach NBP database. After executing Procedure 1, the user will need to re-add any previous NBP data.
NetBatch Plus Installation Steps - Procedure 1 1. Log on to the Tandem. Use a Logon ID that has access to stop and start the NetBatch-Plus Pathway. This logon ID may be the SUPER.SUPER or SUPER.OPER IDs. The logon ID must also have access to modify the NetBatch-Plus Pathway. Stop processes that have any of the NetBatch-Plus database files open. Instructions: To stop the NBP Pathway, determine where the System Administrator has installed NBP. Stop the NBP Pathway using a macro that resides with the NBP files, at TACL: VOLUME $volume.subvol NSHUT _ FUP LISTOPENS NBP0* Where volume.subvol is the location of the NBP system. If it becomes necessary to stop the NetBatch Scheduler, please refer to the procedures located at the end of this section. Execute TACL macro to install NBP database from the CO-ach subvolume. Explanation: This step assumes NetBatch-Plus has both its objects and data files in a single subvolume. If that is not the case, simply copy file PS0000O (PS, 4zeros, O) from the object subvolume into the data subvolume using the following command, Instruction: at TACL: FUP DUP <nbp_vol>.<obj_subvol>.PS0000O, _ <$nbp_vol>.<data_subvol>.* Instruction: Execute the CO-ach NBP Install macro. At TACL:
2.
3.
CO-ach
VOLUME $x.AC24NBP _ INSTNBP $volume.subvolume Where $volume.subvolume is the location of the NBP system If PS0000O was copied at the beginning of this step, it should now be deleted. At TACL: _ PURGE $nbp_volume.data_subvolume.PS0000O 4. Start the NetBatch-Plus Pathway. Start the NBP Pathway using a macro that resides with the NBP files. At TACL: VOLUME $volume.subvolume (location of NBP system) _ NCOOL (macro used by SYSADMIN to start NBP Pathway) 5. Log on to NetBatch-Plus. Logon to NetBatch-Plus to determine if the CO-ach NBP database is installed correctly. At TACL: _ NBP At the main NBP screen, logon to NBP: n Enter coach in the NBP user name field (no password) n F16 (Sign On) n SF5 (Password Validation) At the Password Validation screen, enter Guardian logon: n Enter <logon.id>, <password> in the User fields n F5 (Validate) n F16 (Return to Main Menu)
Check the Defaults Set Details:

CO-ach
n F1 (Defaults Set Details) n Blank out the SET: field n F2 (Next) _ Displayed Next OK should appear on bottom left of the screen. 6. Update Defaults Set Details record for user site. The previous step should have left the Defaults Set Details screen displayed. n The SET: field should contain the value ACH n Enter the System and Scheduler Process names in the SCHEDULER: field. n The CLASS: field may need to be changed. If COACH is used, then COACH as a CLASS needs to be made known to the Scheduler. This can be done in the macro that starts the Scheduler or done online via the SCHEDULER INTERFACE (F9) from the NBP Main Menu. If COACH is not used, then change CLASS to the assigned value. n The OWNER: field should contain the same user ID that was entered as the CO-ach owner in the EDITCONF file during the COach application installation. Also enter the password, if any. n Enter the correct $vol.subvol.filename for TACL in the EXEC.PRG: field. ACI strongly recommends that the TACL object reside on $SYSTEM.SYSTEM.TACL n Enter $x.AC24OBEY in the VOLUME: field. $x is the volume where the CO-ach application resides. n F6 (Update) Changed OK should appear bottom left of screen. _ n F16 (Return to Main Menu) 7. Update Catalogs records. Update Catalog Assigns and Params. The previous step should have left the system at the Main Menu screen. n F4 (Catalogs) At the Catalog Assign screen: n F2 (Next) The XLOG-PROCESS ASSIGN record displays.
CO-ach
n Enter the correct XLOG process name in the PHYSICAL FILENAME: field. (The character after the $ needs to match the process name prefix specified in the EDITCONF file) n F6 (Update) Changed OK should appear on the bottom right of screen. _ n F16 (Return to Main Menu) END PROCEDURE 1 The installation of the CO-ach NetBatch-Plus database is complete. Press SF16 twice to exit the NetBatch-Plus Pathway screen. Any previous NetBatch-Plus data destroyed during Procedure 1 should now be re-added to the database.
CO-ach PROCEDURE 2
Procedure 2 requires the user to manually add all the CO-ach NetBatch-Plus database information. The user will need to reference the NBP Enform reports that came with the CO-ach Install Package. NetBatch Plus Installation Steps - Procedure 2 1. 2. _ Log on to the Tandem system with the CO-ach logon ID. Log on to NetBatch-Plus. Logon to NetBatch-Plus to add CO-ach job information. At TACL: NBP At the main NBP screen, logon to NBP: n Enter coach in the NBP User Name field (no password) n F16 (Sign On) n SF5 (Password Validation) At the Password Validation screen, enter Guardian logon: n Enter <logon.id>, <password> in the User fields n F5 (Validate) n F16 (Return to Main Menu) Add the DEFAULTS SET DETAILS. At the NBP Main Menu screen: n F1 (Defaults Set Details) n Enter ACH in the SET: field n Enter the correct System and Scheduler Process names in the SCHEDULER: field. The user may need to change the CLASS field. If COACH is used, then COACH as a CLASS needs to be made known to the Scheduler. This can be done in the macro that starts the Scheduler or done online via the SCHEDULER INTERFACE (F9) from the NBP Main Menu. If COACH
_ 3.
CO-ach is not used, then change CLASS to DEFAULT. n Enter the following in the appropriate fields: CLASS: OWNER: COMMENT: EXEC. PRG:
COACH (or DEFAULT) <Co-ach Guardian User ID> ACH JOBS Enter correct $vol.subvol.filename for TACL IN: Blank OUT: Blank VOLUME: $x.AC24OBEY ($x is the CO-ach Volume) STARTUP: Blank ANY USER SUBMIT: Y HOLD AFTER: N Leave all other fields blank
_ 4.
n F4 (Add) Added OK should appear bottom left of screen. n F16 (Return to Main Menu) Add the Catalog Attachments. Add the Catalog Attachments. There is one Catalog Assign and three Catalog params. From the NBP Main Menu screen: n F4 (Catalogs) OPTION: ASSIGN SET: ACH ASSIGN NAME: XLOG-PROCESS OWNER: (from DEFAULT SET) PHYSICAL FILENAME: $aXLG (a- sys letter from EDITCONF)
n F4 (Add)
Added Ok should appear bottom of screen.
Now add Catalog Params. From the NBP Catalog Assigns screen: OPTION: PARAM n F13 (Choose Option) OPTION: PARAM
CO-ach
SET: ACH PARAM NAME: FROM-DATE OWNER: (from DEFAULT SET) PARAM VALUE: 920902 n F4 (Add) Added Ok should appear bottom of screen. OPTION: PARAM SET: ACH PARAM NAME: PROCESSING-DATE OWNER: (from DEFAULT SET) PARAM VALUE: 920902 n F4 (Add) Added Ok should appear bottom of screen. OPTION: PARAM SET: ACH PARAM NAME: TO-DATE OWNER: (from DEFAULT SET) PARAM VALUE: 920902 n F4 (Add) Added Ok should appear bottom of screen.
5.
Add the CO-ach Jobs. Add the CO-ach Jobs. The instructions will indicate how to add the first Job. The rest of the procedure consists of repeating this step for every Job listed in the CO-ach NBP Job Enform report. From the NBP Main Menu screen: n F2 (Job Definition) SET: JOB NAME: SCHEDULER: CLASS: OWNER: COMMENT: EXEC. PRG: IN: OUT: VOLUME: STARTUP ANY USER SUBMIT: ACH RUN010 Blank (Uses DEFAULT) Blank (Uses DEFAULT) Blank (Uses DEFAULT) ACH START PSX010 Blank (Uses DEFAULT) RUN010 $S.#ACH.RUN010 Blank (Uses DEFAULT) Blank Y
CO-ach HOLD AFTER: N Leave all other fields blank n F4 (Add)
Now add Job Attachments for RUN010. From Job Definition screen: n F13 (Job Attachments) OPTION: PARAM OWNER: (Uses DEFAULT) JOB SET: (Uses DEFAULT) JOB NAME: (Name from Job Definition screen) PARAM NAME: DIST-DATE CATALOG SET: ACH CATALOG NAME: PROCESSING-DATE PARAM VALUE: Blank (From Catalog) n F4 (Add) OPTION: OWNER: JOB SET: JOB NAME: PARAM NAME: CATALOG SET: CATALOG NAME: PARAM VALUE: n F4 (Add) OPTION: OWNER: JOB SET: JOB NAME: PARAM NAME: CATALOG SET: CATALOG NAME: PARAM VALUE: n F4 (Add) OPTION: OWNER: JOB SET: PARAM (Uses DEFAULT) (Uses DEFAULT) (Name from Job Definition screen) DIST-KEY-DATE ACH PROCESSING-DATE Blank (From Catalog) PARAM (Uses DEFAULT) (Uses DEFAULT) (Name from Job Definition screen) EFFECTIVE-DATE ACH PROCESSING-DATE Blank (From Catalog) PARAM (Uses DEFAULT) (Uses DEFAULT)
CO-ach JOB NAME: PARAM NAME: CATALOG SET: CATALOG NAME: PARAM VALUE: n F4 (Add)
NetBatch-Plus Installation (Name from Job Definition screen) PROCESSING-DATE ACH PROCESSING-DATE Blank (From Catalog)
Now add the rest of the CO-ach NBP Jobs listed in the Enform report. _ n F16 (Return to Job Definition screen) n F16 (Return to Main Menu screen)
END PROCEDURE 2 The installation of the CO-ach NetBatch-Plus database is complete. Press SF16 to exit the NetBatch-Plus Pathway screen.
CO-ach
Stopping and Starting the NetBatch-Plus Scheduler Process 1. Log on to the Tandem system. Use a Logon ID that has access to stop and start $ZBAT (or whatever scheduler the site is using). This logon ID is usually the SUPER.SUPER or SUPER.OPER Ids. Stop the Scheduler. To stop the Scheduler process, determine where the System Administrator has installed NBP. At TACL: VOLUME $vol.subvol (this is the location of the NBP system) BATCHCOM $xxxx; SHUTDOWN SCHEDULER PATHCOM $NBP; SHUTDOWN,WAIT where: xxxx is the scheduler name. The Scheduler process should now be stopped. If following the Procedure 1 steps and it is necessary to stop the Scheduler in order to continue, then return to Step 3 of Procedure 1 now. When ready to re-start the Scheduler process, continue with Step 3 on the following page. 3. Edit the STRTZBAT macro. Using the text editor, examine the contents of the STRTZBAT macro located on the NBP subvolume. Pay particular attention to any CLASSes and EXECutors that are added by this file to ensure they are not in conflict with any existing NetBatch-Plus configuration. _ Note: The COACH class is assumed to be reserved for the use by the CO-ach system. Resolve any conflicts between the STRTZBAT macro and any existing configurations and proceed to the next step. Start the Scheduler and the NetBatch-Plus Pathway.
2.
4.
CO-ach
Start the Scheduler first, then start the NetBatch-Plus Pathway using the folloowing commands at TACL: _ _ VOLUME $volume.subvolume (location of the NBP system) STRTZBAT (macro used to by SYSADMIN to start scheduler) NCOOL (macro used by SYSADMIN to start the NBP Pathway)
Section 4
Extended CO-ach Configuration The First Time CO-ach installation procedures install a BASELINE CO-ach system. Each CO-ach site has distinct processing needs and varying volumes. It is recommended that prior to the GO-LIVE in a production environment that the ACI Performance group review a completed CO-ach Sizing Questionnaire and CO-ach System Configuration, to ensure that the system configuration will process the expected transaction volumes without incident. As part of the review, any number of recommendations may be provided; these should be analyzed and implemented. (Section 8 contains a sample CO-ach Sizing Questionnaire) One of the recommendations from the Performance group might be to configure multiple processes in order to 'complete' various processing cycles, such as Entry edit, Entry Processing and Distribution, within required processing windows. Also, transaction volumes may increase significantly because of new business opportunities. A significant volume increase would impact the data file sizes required to support the new volumes. This section details the procedures to configure multiple processes and to size the volume dependent data files. Before making any configuration changes ensure that a) all CO-ach processing has completed; b) all application modules are SHUTDOWN; and c) a backup is made of all data files that will be changed.
______________________________________________________________________________ Last Modified - 08/19/98 Applied Communications, Inc. 4-1
CO-ach Configuring Multiple CO-ach Processes
Extended CO-ach Configuration
The following table summarizes the modules that can be configured to run multiple processes and their configuration dependencies: CO-ach Module Entry Processing (PSX020) Exposure Monitor (EXPO) Distribution History Update (PSX041) Distribution Report Data Generation (PSX042) Distribution (PSX050) End Of Day Settlement (PSX060) History Cleanup (PSX062) Maximum No of Processes 36 36 36 Main Configuration Dependencies
Multiple Module DEFTABLE Additions Multiple Report Data File Creation Risk Management Enabled Multiple Module DEFTABLE Additions Multiple Module Deftable Additions Multiple Module DEFTABLE Additions Multiple Report Data File Creation
36
36
Multiple Module DEFTABLE Additions NetBatch Plus Job added for each PSX050 defined Multiple Module DEFTABLE Additions Multiple Report Data File Creation Multiple Module DEFTABLE Additions
36
36
Important!! The number of PSX041 and PSX042 modules defined must be the same. (i.e., if 36 PSX041 processes are defined, then 36 PSX042 processes must be defined)
DEFTABLE Changes
CO-ach
The DEFTABLE file that resides on the ACHDATA subvolume contains two types of records - Global records and Module records. DEFTABLE Global Records The Global Base record must always exist and has an index value of 0 or space. A Global Index record does not exist. The Global records are accessed through the DEFTABGL Enable program. The Pathway system must be running. (Refer to Section 1, Step 18 - Perform the Initial Pathway Verification - for information on starting/stopping the Pathway system)
GLOBAL-DEF-TABLE Page 1/6 Approx key DF-PRIMARY-KEY DF-TABLE DF-HEADER * DF-PRIMARY-KEY DF-PROGRAM-ID DF-DATABASE-INDX DF-GLOBAL-FILES DF-CONTROL-FILES DF-AUTH-FILENAME $DATA24.ACHDATA.AUTH DF-BANK-FILENAME $DATA24.ACHDATA.BANK DF-BATCH-CUST-FILENAME $DATA24.ACHDATA.BCUST DF-BTF-INPUT-FILENAME DF-BTF-OUTPUT-FILENAME DF-CAR-FILENAME DF-CUSTOMER-FILENAME DF-ENDPOINT-FILENAME $DATA24.ACHDATA.FTQIN $DATA24.ACHDATA.FTQOUT $DATA24.ACHDATA.CAR $DATA24.ACHDATA.CUSTOMER $DATA24.ACHDATA.ENDPOINT
DF-DISTRIB-CONTROL-FILENAME $DATA24.ACHDATA.PSX050C DF-HOLIDAY-FILENAME $DATA24.ACHDATA.HOLIDAY
CO-ach DF-HPC-FILENAME DF-IMF-FILENAME DF-OPR-ID-FILENAME Record read OK
Extended CO-ach Configuration $DATA24.ACHDATA.HPC $DATA24.ACHDATA.IMF $DATA24.ACHDATA.OPERID F3 for Help,shift F16 to Exit
Ready for input
CO-ach DEFTABLE Module Records
There are two types of DEFTABLE Module records, a Base record and an Index record. A Module Base record must always exist and has an index value of 0 or space. At least one Module Index record must exist for replicated processes. The Module records are accessed through the DEFTABMD Enable program. The Pathway system must be running. (Refer to Section 1, Step 18 - Perform the Initial Pathway Verification -for information on starting/stopping the Pathway system) PSX020 MODULE BASE RECORD
CO-ach
MODULE-DEF-TABLE Page 1/4 Approx key DF-PRIMARY-KEY DF-TABLE DF-HEADER * DF-PRIMARY-KEY DF-PROGRAM-ID PSX020 DF-DATABASE-INDX DF-MODULE-FILES DF-DATABASE-FILES DF-WORK-CONTROL-FILENAME DF-BACKUP-DATA-FILENAME DF-INPUT-DATA-FILENAME $DATA24.ACHDATA.CUSTROUT DF-TEMPORARY-FILES DF-LEFT-DRAFT-FILENAME DF-RIGHT-DRAFT-FILENAME DF-SORT-WORK-FILENAME DF-SORT-WORK-2-FILENAME DF-SORTED-DATA-FILENAME DF-SORTED-DATA-2-FILENAME DF-TEMP-DATA-FILENAME DF-TEMP-INPUT-FILENAME DF-TEMP-REQUEST-FILENAME Record read OK Ready for input
F3 for Help,shift F16 to Exit
CO-ach
MODULE-DEF-TABLE Page 2/4 Approx key DF-PRIMARY-KEY DF-TABLE DF-MODULE-FILES DF-REPORT-FILES DF-DELETE-PRINT-FILENAME DF-DETAIL-PRINT-FILENAME DF-DUP-PRINT-FILENAME DF-ERROR-PRINT-FILENAME DF-HISTORY-PRINT-FILENAME DF-IMF-PRINT-FILENAME DF-MICR-DRAFT-FILENAME DF-MICR-RPT-FILENAME DF-PARM-PRINT-FILENAME DF-PRINT-FILENAME $S.#ACH020.RECAP DF-REPORT-FILENAME $DATA24.ACHDATA.RPT020 DF-RT-OVRRD-PRINT-FILENAME DF-TOTALS-PRINT-FILENAME DF-TRANSACTION-FILENAME DF-TRANSMITTAL-FILENAME Ready for input F3 for Help,shift F16 to Exit
CO-ach MODULE-DEF-TABLE Page 3/4 Approx key DF-PRIMARY-KEY DF-MODULE-FILES DF-OTHER-INFO DF-OUTPUT-INFO DF-OUTPUT-SUBVOL DF-TEMP-INFO DF-TEMP-SUBVOL DF-SAVE-INFO DF-SAVE-SUBVOL DF-PROCESS-CLASS-INFO DF-IMMED-ORIGIN DF-ENDPOINT DF-RUN-OPTIONS DF-PROGRAM-FILENAME DF-PRIORITY 155 DF-TMF-WINDOW 10 DF-SWAP-SUBVOL $DATA20
Ready for input
CO-ach
MODULE-DEF-TABLE Page 4/4 Approx key DF-PRIMARY-KEY DF-OTHER-INFO DF-PROCESS-SUBCLASS-INFO DF-NUM-PROCESSES 1 DF-PROCESS-INFO[1] DF-PROCESS-NAME DF-PRIMARY-CPU DF-SECONDARY-CPU DF-PROCESS-INFO[2] DF-PROCESS-NAME DF-PRIMARY-CPU DF-SECONDARY-CPU DF-PROCESS-INFO[3] DF-PROCESS-NAME DF-PRIMARY-CPU DF-SECONDARY-CPU
Ready for input
CO-ach PSX020 MODULE INDEX RECORD
MODULE-DEF-TABLE Page 1/4 Approx key DF-PRIMARY-KEY DF-TABLE DF-HEADER * DF-PRIMARY-KEY DF-PROGRAM-ID PSX020 DF-DATABASE-INDX 1 DF-MODULE-FILES DF-DATABASE-FILES DF-WORK-CONTROL-FILENAME DF-BACKUP-DATA-FILENAME DF-INPUT-DATA-FILENAME DF-TEMPORARY-FILES DF-LEFT-DRAFT-FILENAME DF-RIGHT-DRAFT-FILENAME DF-SORT-WORK-FILENAME DF-SORT-WORK-2-FILENAME DF-SORTED-DATA-FILENAME DF-SORTED-DATA-2-FILENAME DF-TEMP-DATA-FILENAME DF-TEMP-INPUT-FILENAME DF-TEMP-REQUEST-FILENAME Record read OK Ready for input F3 for Help,shift F16 to Exit
CO-ach
MODULE-DEF-TABLE Page 2/4 Approx key DF-PRIMARY-KEY DF-TABLE DF-MODULE-FILES DF-REPORT-FILES DF-DELETE-PRINT-FILENAME DF-DETAIL-PRINT-FILENAME DF-DUP-PRINT-FILENAME DF-ERROR-PRINT-FILENAME DF-HISTORY-PRINT-FILENAME DF-IMF-PRINT-FILENAME DF-MICR-DRAFT-FILENAME DF-MICR-RPT-FILENAME DF-PARM-PRINT-FILENAME DF-PRINT-FILENAME $DATA24.ACHDATA.RPT020A DF-RT-OVRRD-PRINT-FILENAME DF-TOTALS-PRINT-FILENAME DF-TRANSACTION-FILENAME DF-TRANSMITTAL-FILENAME DF-REPORT-FILENAME Ready for input F3 for Help,shift F16 to Exit
CO-ach
MODULE-DEF-TABLE Page 3/4 Approx key DF-PRIMARY-KEY DF-MODULE-FILES DF-OTHER-INFO DF-OUTPUT-INFO DF-OUTPUT-SUBVOL DF-TEMP-INFO DF-TEMP-SUBVOL DF-SAVE-INFO DF-SAVE-SUBVOL DF-PROCESS-CLASS-INFO DF-IMMED-ORIGIN DF-ENDPOINT DF-RUN-OPTIONS DF-PROGRAM-FILENAME DF-PRIORITY 155 DF-TMF-WINDOW 10 DF-SWAP-SUBVOL $DATA20
Ready for input
CO-ach MODULE-DEF-TABLE Page 4/4 Approx key DF-PRIMARY-KEY DF-OTHER-INFO DF-PROCESS-SUBCLASS-INFO DF-NUM-PROCESSES 1 DF-PROCESS-INFO[1] DF-PROCESS-NAME $E20A DF-PRIMARY-CPU DF-SECONDARY-CPU DF-PROCESS-INFO[2] DF-PROCESS-NAME DF-PRIMARY-CPU DF-SECONDARY-CPU DF-PROCESS-INFO[3] DF-PROCESS-NAME DF-PRIMARY-CPU DF-SECONDARY-CPU
Ready for input
CO-ach Instructions to Configure Multiple PSX020 1.
Extended CO-ach Configuration 3
Using DEFTABGL, set the global base record (index 0 or space) field FNUM-DTRAN-FILES-X to the number of PSX020 processes to be run. At TACL: VOLUME AC24INST OBEY DEFTABGL n F4 (Read First Record) n F2 (Next Page) to Page 5 n Set DF-NUM-DTRAN-FILES-X to the number of required PSX020s n Set DF-ACTIVE-PART-IND to one less than the above n F14 (UPDATE) n SF16 (EXIT) Using DEFTABMD, verify PSX020 base record (index 0 or space) field DF-NUM-PROCESSES is set to 1. DO NOT CHANGE THIS. At TACL: VOLUME AC24INST OBEY DEFTABMD n n n n Enter PSX020 in the DF-PROGRAM-ID field F6 (Read Approximate) F2 (Next Page) to Page 4 Verify DF-NUM-PROCESSES is set to 1
2.
3.
Verify the following params for index 1 record of PSX020: n n n n n n n n n n F1 (Previous Page) to Page 1 Enter PSX020 in the DF-PROGRAM-ID field (case sensitive) Enter 1 in the DF-DATABASE-INDX field F6 (Read Approximate) F2 (Next Page) to Page 2 Verify DF-REPORT-FILENAME is set to $vol.subvol.RPT020A F2 (Next Page) to Page 4 Verify DF-PROCESS-NAME is set to $y20A Verify DF-PRIMARY-CPU is set to 0 Verify DF-SECONDARY-CPU is set to 1
4.
Add index records for any additional PSX020 process. Repeat Step 3, as necessary, changing the parameters accordingly, until index records ______________________________________________________________________________
Last Modified - 08/19/98 Applied Communications, Inc. 4-14
CO-ach
as necessary, changing the parameters accordingly, until index records for all required PSX020 processes are added. (PSX020 index 2 uses RPT020B, index 3 uses RPT020C, index 3 uses RPT020D, etc.) If adding index record 2, set the params as shown: DF-REPORT-FILENAME= DF-PROCESS-NAME = DF-PRIMARY-CPU = DF-SECONDARY-CPU = n F10 (INSERT) n F16 (EXIT) 5. Create the report files, and the required alternate key files, specified in the DF-REPORT-FILENAME parameters. At TACL: VOLUME AC24FUP FUP DUP RPT020A, RPT020B EDIT RPT020B * XVS F n Change the process/file letter in the SET ALTFILE statement n Change the process/file letter in both CREATE statements n SF16 *EXIT VOLUME ACHDATA FUP/IN AC24FUP.RPT020B/ 6. Create the report files for any additional PSX020 processes. Repeat Step 5 changing the process/file letter accordingly. NOTE: Spread the files across multiple volumes as needed. $vol.subvol.RPT020B $y20B 1 (Alter the CPU pairs for 0 balancing resource usage)
CO-ach
Instructions to Configure Multiple PSX041 ** For every PSX041, there needs to be a PSX042 ** 1. Using DEFTABMD, change the base module record (index 0 or space) field DF-NUM-PROCESSES to the number of PSX041 processes to be run. At TACL: VOLUME AC24INST OBEY DEFTABMD Enter PSX041 in the DF-PROGRAM-ID field F6 (Read Approximate) F2 (Next Page) to Page 4 Set DF-NUM-PROCESSES to the number of required PSX041 processes n F14 (UPDATE) n n n n 2. Verify the following params for the index 1 record of PSX041: n n n n n n n n n n n n n 3. F1 (Previous Page) to Page 1 Enter PSX041 in the DF-PROGRAM-ID field Enter 1 in the DF-DATABASE-INDX field F6 (Read Approximate) F2 (Next Page) to Page 2 Verify DF-PRINT-FILENAME is set to $s.#ACH041A.PARM Verify DF-REPORT-FILENAME is set to $vol.subvol.RPT060A F2 (Next Page) to Page 4 Verify DF-NUM-PROCESSES is set to number required Verify DF-PROCESS-NAME is set to $y41A Verify DF-PRIMARY-CPU is set to 0 Verify DF-SECONDARY-CPU is set to 1 If this record is altered, F14 (UPDATE) to save changes
Add index records for any additional PSX041 process. Repeat Step 3, as necessary, changing the parameters accordingly, until index records for all required PSX041 processes are added. (PSX041 index 2 uses RPT060B, index 3 uses C, index 3 uses D,etc.) For example, if adding index record 2, set the params as shown:
CO-ach
DF-PRINT-FILENAME = DF-REPORT-FILENAME= DF-PROCESS-NAME = DF-PRIMARY-CPU = DF-SECONDARY-CPU = n F10 (INSERT) n SF16 (EXIT) 4.
$s.#ACH041B.PARM $vol.subvol.RPT060B $y41B 1 (Alter the CPU pairs for 0 balancing resource usage)
Create the report files, and the required alternate key files, specified in the DF-REPORT-FILENAME parameters. At TACL: VOLUME AC24FUP FUP DUP RPT060A, RPT060B EDIT RPT060B * XVS F n Change the process/file letter in the SET ALTFILE statement n Change the process/file letter in both CREATE statements n SF16 *EXIT VOLUME ACHDATA FUP/IN AC24FUP.RPT060B/
5.
Create the report files for any additional PSX041 processes. Repeat Step 4 changing the process/file letter accordingly. NOTE: Spread the files across multiple volumes as necessary.
CO-ach
Instructions to Configure Multiple PSX042 ** For every PSX041, there needs to be a PSX042 ** 1. Using DEFTABMD, change the base module record (index 0 or space) field DF-NUM-PROCESSES to the number of PSX042 processes to be run. At TACL: VOLUME AC24INST OBEY DEFTABMD n n n n Enter PSX042 in the DF-PROGRAM-ID field F6 (Read Approximate) F2 (Next Page) to Page 4 Set DF-NUM-PROCESSES to the number of required PSX042 processes n F14 (UPDATE) Verify the following params for the index 1 record of PSX042: n n n n n n n n n n n n F1 (Previous Page) to Page 1 Enter PSX042 in the DF-PROGRAM-ID field Enter 1 in the DF-DATABASE-INDX field F6 (Read Approximate) F2 (Next Page) to Page 2 Verify DF-PRINT-FILENAME is set to $s.#ACH042A.PARM Verify DF-REPORT-FILENAME is set to $vol.subvol.RPT040A F2 (Next Page) to Page 4 Verify DF-NUM-PROCESSES is set to number required Verify DF-PROCESS-NAME is set to $y42A Verify DF-PRIMARY-CPU is set to 1 Verify DF-SECONDARY-CPU is set to 0
2.
n If this record is altered, F14 (UPDATE) to save changes 3. Add index records for any additional PSX042 process. Repeat Step 3, as necessary, changing the parameters accordingly, until index records for all required PSX042 processes are added. (PSX042 index 2 uses RPT040B, index 3 uses C, index 3 uses D, etc.) For example, if adding index record 2, set the params as shown:
CO-ach
DF-PRINT-FILENAME = DF-REPORT-FILENAME = DF-PROCESS-NAME = DF-PRIMARY-CPU = DF-SECONDARY-CPU = n F10 (INSERT) n SF16 (EXIT) 4.
$s.#ACH042B.PARM $vol.subvol.RPT040B $y42B 1 (Alter the CPU pairs for 0 balancing resource usage)
Create the report files, and the required alternate key files, specified in the DF-REPORT-FILENAME parameters. At TACL: VOLUME AC24FUP FUP DUP RPT040A, RPT040B EDIT RPT040B * XVS F n Change the process/file letter in the SET ALTFILE statement n Change the process/file letter in both CREATE statements n SF16 *EXIT VOLUME ACHDATA FUP/IN AC24FUP.RPT040B/
5.
1. Create the report files for any additional PSX042 processes. Repeat Step 4 changing the process/file letter accordingly. NOTE: Spread the files across multiple volumes as necessary.
CO-ach
Instructions to Configure Multiple PSX050 1. Using DEFTABMD, verify the PSX050 base record (index 0 or space) field DF-NUM-PROCESSES = 1. DO NOT CHANGE THIS. At TACL: VOLUME AC24INST OBEY DEFTABMD n n n n 2. Enter PSX050 in the DF-PROGRAM-ID field F6 (Read Approximate) F2 (Next Page) to Page 4 Verify DF-NUM-PROCESSES is set to 1
Verify the following params for the index 1 record of PSX050: n n n n n n n n n n n n n n n F1 (Previous Page) to Page 1 Enter PSX050 in the DF-PROGRAM-ID field Enter 1 in the DF-DATABASE-INDX field F6 (Read Approximate) F2 (Next Page) to Page 2 Verify DF-ERROR-PRINT-FILENAME is set to $s.#ACH050A.ERROR Verify DF-PARM-PRINT-FILENAME is set to $s.#ACH050A.PARAM Verify DF-PRINT-FILENAME is set to $s.#ACH050A.RECAP Verify DF-TRANSMITTAL-FILENAME is set to $s.#ACH050A.XMITTAL F2 (Next Page) to Page 4 Verify DF-NUM-PROCESSES is set to 1 (DO NOT CHANGE) Verify DF-PROCESS-NAME is set to $y50A Verify DF-PRIMARY-CPU is set to 1 Verify DF-SECONDARY-CPU is set to 0 If this record is altered, F14 (UPDATE) to save changes
3.
Add index records for any additional PSX050 process. Repeat Step 3, as necessary, changing the parameters accordingly, until index records for all required PSX050 processes are added. (PSX050 index 2 uses ACH050B, index 3 uses C, index 3 uses D, etc.) For example, if adding index record 2, set the params as shown:
CO-ach
pairs
DF-ERROR-PRINT-FILENAME DF-PARM-PRINT-FILENAME DF-PRINT-FILENAME DF-TRANSMITTAL-FILENAME DF-PROCESS-NAME DF-PRIMARY-CPU DF-SECONDARY-CPU
= = = = = = =
$s.#ACH050B.ERROR $s.#ACH050B.PARAM $s.#ACH050B.RECAP $s.#ACH050B.XMITTAL $y50B 1 (Alter the CPU 0 for balancing resource usage)
n F10 (INSERT) n SF16 (EXIT) 4.
Create additional NBP jobs for each PSX050 process added. From NBP: n Read the DISTRIB1 job n Change the JOB NAME field to DISTRIB(x) and duplicate using F9 (where (x) is the index indicator) n Read the new DISTRIB(x) job n Update the COMMENT, IN and OUT fields appropriately using F6 n Via Job Attachments, update param DATABASE-IDX to index record (x) Repeat Step 4, as necessary, changing the job names and index indicators, until new NBP jobs are created for the required PSX050 processes. Create an obey file for each NBP job added in Step 4. From TACL: VOLUME AC24OBEY FUP DUP DISTRIB1, DISTRIB(x) Repeat Step 5, as necessary, changing (x) in the new obey file name, until new obey files are created for the required PSX050 processes.
5.
CO-ach
Instructions to Configure Multiple PSX060 1. ** For each PSX060, there needs to be a PSX062 ** Using DEFTABMD, change the base module record (index 0 or space) field DF-NUM-PROCESSES to the number of PSX060 processes to be run. At TACL: VOLUME AC24INST OBEY DEFTABMD n n n n 2. Enter PSX060 in the DF-PROGRAM-ID field F6 (Read Approximate) F2 (Next Page) to Page 4 Set DF-NUM-PROCESSES to the number of required PSX060 processes n F14 (UPDATE) Verify the following params for the index 1 record of PSX060: F1 (Previous Page) to Page 1 Enter PSX060 in the DF-PROGRAM-ID field Enter 1 in the DF-DATABASE-INDX field F6 (Read Approximate) F2 (Next Page) to Page 2 Verify DF-ERROR-PRINT-FILENAME is set to $s.#ACH060A.ERROR Verify DF-REPORT-FILENAME is set to $vol.subvol.RPT060A F2 (Next Page) to Page 4 Verify DF-NUM-PROCESSES is set to number required Verify DF-PROCESS-NAME is set to $y60A Verify DF-PRIMARY-CPU is set to 0 Verify DF-SECONDARY-CPU is set to 1 If this record is altered, F14 (UPDATE) to save changes
n n n n n n n n n n n n n 3.
Add index records for any additional PSX060 process. Repeat Step 3, as necessary, changing the parameters accordingly, until index records for all required PSX060 processes are added. (PSX060 index 2 uses RPT060B, index 3 uses C, index 3 uses D, etc.) For example, if adding
CO-ach index record 2, set the params as shown: DF-ERROR-PRINT-FILENAME DF-REPORT-FILENAME DF-PROCESS-NAME DF-PRIMARY-CPU DF-SECONDARY-CPU n F10 (INSERT) n SF16 (EXIT) 4. = = = = =
$s.#ACH060B.ERROR $vol.subvol.RPT060B $y60B 1 (Alter the CPU pairs 0 for balancing resource usage)
Because PSX041 and PSX060 share the RPT060 files, there is no need to execute the report creation step.
CO-ach Instructions to Configure Multiple PSX062 1.
Using DEFTABMD, change the base module record (index 0 or space) field DF-NUM-PROCESSES to the number of PSX062 processes to be run. At TACL: VOLUME AC24INST OBEY DEFTABMD n n n n Enter PSX062 in the DF-PROGRAM-ID field F6 (Read Approximate) F2 (Next Page) to Page 4 Set DF-NUM-PROCESSES to the number of required PSX062 processes n F14 (UPDATE) Verify the following params for the index 1 record of PSX062: n n n n n n F1 (Previous Page) to Page 1 Enter PSX062 in the DF-PROGRAM-ID field Enter 1 in the DF-DATABASE-INDX field F6 (Read Approximate) F2 (Next Page) to Page 2 Verify DF-ERROR-PRINT-FILENAME is set to $s.#BCH062A.ERROR n F2 (Next Page) to Page 4 n Verify DF-NUM-PROCESSES is set to number required n Verify DF-PROCESS-NAME is set to $y62A n Verify DF-PRIMARY-CPU is set to 0 n Verify DF-SECONDARY-CPU is set to 1 n If this record is altered, F14 (UPDATE) to save changes Add index records for any additional PSX062 process. Repeat Step 3, as necessary, changing the parameters accordingly, until index records for all required PSX062 processes are added. (PSX062 index 2 uses $y62B, index 3 uses C, index 3 uses D, etc.). For example, if adding index record 2, set the params as shown: DF-ERROR-PRINT-FILENAME DF-PROCESS-NAME DF-PRIMARY-CPU DF-SECONDARY-CPU = = = = $s.#BCH062B.ERROR $y62B 1 (Alter the CPU pairs 0 for balancing
2.
3.
CO-ach
Extended CO-ach Configuration resource usage)
n F10 (INSERT) n SF16 (EXIT) NOTE: The number of PSX062 index module records must be less than or equal to the number of active partition indicators (Global DEFTABLE DF-ACTIVE-PART-IND + 1). This allows for one PSX062 for each partition. If configuring multiple processes, ensure that Global DEFTABLE DF-ACTIVE-PART-IND is set correctly. Because PSX062 does not use the DF-REPORT-FILENAME parameter, there is no need to execute the report file creation step.
4.
CO-ach Instructions to Configure Multiple EXPO 1.
Using DEFTABMD, change the base module record (index 0 or space) field DF-NUM-PROCESSES to the number of EXPO processes to be run. At TACL: VOLUME AC24INST OBEY DEFTABMD Enter EXPO in the DF-PROGRAM-ID field F6 (Read Approximate) F2 (Next Page) to Page 4 Set DF-NUM-PROCESSES to the number of required EXPO processes n F14 (UPDATE) n n n n
2.
Verify the following params for the index 1 record of EXPO: n n n n n n n n n n F1 (Previous Page) to Page 1 Enter EXPO in the DF-PROGRAM-ID field Enter 1 in the DF-DATABASE-INDX field F6 (Read Approximate) F2 (Next Page) to Page 4 Verify DF-NUM-PROCESSES is set 1 (DO NOT CHANGE) Verify DF-PROCESS-NAME is set to $yXPA Verify DF-PRIMARY-CPU is set to 0 Verify DF-SECONDARY-CPU is set to 1 If this record is altered, F14 (UPDATE) to save changes
3.
Add index records for any additional EXPO process. Repeat Step 3, as necessary, changing the parameters accordingly, until index records for all required EXPO processes are added. (EXPO index 2 uses $yXPB, index 3 uses C, index 3 uses D, etc.) For example, if adding index record 2, set the params as shown: DF-PROCESS-NAME DF-PRIMARY-CPU DF-SECONDARY-CPU n F10 (INSERT)
= = =
$yXPB 1 (Alter the CPU pairs for 0 balancing resource usage)
CO-ach n SF16 (EXIT)
CO-ach
Configuring Volume Dependent Data Files The CO-ach application is designed to meet the current and future needs for ACH processing in large volume environments. Every customer configuration for CO-ach is dependent upon the processing being performed and the transaction volumes to be processed. As such, each customer may wish to tailor their configuration for performance balancing and to manage their investment in disk media. The ACHDATA data files are produced by using the TANDEM FUP utility and FUP input files provided by ACI on the ACnnFUP subvolume. The FUP input files will allow the systems manager to tailor the primary, secondary and maximum extents for file creation and designate specific volume locations. When creating an Enscribe file, the maximum amount of physical disk space to be allocated for the file can be specified. Physical space is allocated in the form of extents. An extent is a contiguous block of disk space that can range from a single page (2048 bytes) to 65,535 pages (134,215,680 bytes). By default, every Enscribe disk file and partition has 16 extents; a particular non-partitioned file or the partitions of a key-sequenced file can have more than that number. For further information on file creation and extents refer to the Tandem Enscribe Programmers Manual, Section 4 - General File Creation and Access Information. A number of temporary files are created or generated as part of an intermediate step and are subsequently purged by the application (e.g., in the case of sorting various files using FASTSORT). Below are descriptions of modules that require source file changes, modules that may require TACL environment changes, and modules that support the definition of file extents through NetBatch Plus. Batch modules that create NACHA output files typically have file attributes defined within the source code for the batch module. In
CO-ach
order to allow these modules to process larger volumes, the file attributes within the source code must be changed and the module recompiled and bound.
CO-ach
The Prenote Creation module (PSX210), the BAI Report module (PSX410), the Received Returns module (PSX530), and the MICR Draft creation module (PSX630), are active only as long as there is processing to be performed. The current values for the constants defined within the source files for the BAI Report/Received Return and MICR Draft Creation module should be sufficient for most processing volumes. Again, there is the option to alter the file attributes within the relevant source file module and then recompile and bind. For the BAI Report, Received Return, and MICR Draft Creation modules there is another way to define the values used in file creation. A new assign and param value can be added to the NetBatch Plus jobs used to execute the Prenote Creation, BAI Report, Received Return, or MICR Draft Creation modules, and then used to determine the attributes for file creation.
CO-ach
NACHAIO The source file AC24SRC.NACHAIO has several items that can be changed to tailor file attributes: WORKING-STORAGE 01 NACHA-FILE-ATTRIBUTES. 02 NFA-PRIMARY-EXTENTSIZE PIC S9(4) COMP VALUE 100. 02 NFA-SECONDARY-EXTENTSIZE PIC S9(4) COMP VALUE 200. 02 NFA-MAX-EXTENTS PIC S9(4) COMP VALUE 900. The NFA-PRIMARY-EXTENTSIZE field corresponds to the FUP file attribute PRIMARY Extents. The NFA-SECONDARY-EXTENTSIZE field corresponds to the FUP file attribute SECONDARY Extents. The NFA-MAX-EXTENTS field corresponds to the FUP file attribute MAX EXTENTS. The record length for NACHAIO records is set programmatically. Impacted Modules The following modules will have to be compiled and bound: 1. 2. 3. 4. 5. AC24SRC.NACHAIO AC24SRC.PSX516 AC24SRC.PSX517 AC24SRC.PSX526 AC24SRC.RELRSK (Reject Returns) (Reject Reentry Exceptions) (History Exceptions: On-line & Host Returns) (Risk Hold Exceptions)
CO-ach
PSXS0119 The source file AC24SRC.PSXS0119 has several items that can be changed to tailor file attributes: WORKING-STORAGE 01 WS-FILE-INFO. 05 PRIMARY-EXTENTSIZE 05 SECONDARY-EXTENTSIZE 05 MAX-EXTENTS
PIC S9(04) COMP VALUE 100. PIC S9(04) COMP VALUE 200. PIC S9(04) COMP VALUE 900.
The PRIMARY-EXTENTSIZE field corresponds to the FUP file attribute PRIMARY Extents. The SECONDARY-EXTENTSIZE field corresponds to the FUP file attribute SECONDARY Extents. The MAX-EXTENTS field corresponds to the FUP file attribute MAX EXTENTS. The record length(s) for PSXS0119 records will either be 94 bytes (NACHA Format), or 109 bytes (Extended NACHA), or 530 bytes (PSG format) depending upon the values passed in the calling params. Impacted Modules The following modules will have to be compiled and bound: 1. 2. 3. 4. 5. 6. 7. AC24SRC.PSXS0119 AC24SRC.PSXS0122 AC24SRC.PSXS0129 AC24SRC.PSX005 AC24SRC.PSX050 AC24SRC.PSX070 AC24SRC.PSX530
(Reformat input file to NACHA) (Distribution) (Consolidation) (Received Returns)
Please note the Tandem limitations and recommendations for file

CO-ach
attributes when altering the CO-ach application data files. For further information refer to the Tandem Enscribe Programmers Manual, Section 4 - General File Creation and Access Information and the language specific programming manual.
CO-ach
PSX010 The file AC24MACS.PSX010 uses four TACL variables to determine the primary and secondary extents of the Addenda Hold (ADDHOLD) and Batch Header Hold (BTCHOLD) files created by PSX010. Variables related to the FUP file attribute PRIMARY EXTENTS: ADDHOLD_FILE_PRIMARY_EXT BTCHOLD_FILE_PRIMARY_EXT Variables related to the FUP file attribute SECONDARY EXTENTS: ADDHOLD_FILE_SECONDARY_EXT BTCHOLD_FILE_SECONDARY_EXT These variables are TACL constants defined in the TACLCONF file. To change, edit the AC24OBEY.TACLCONF file, make the necessary adjustments to the four TACL constants, and perform a TACLCOLD as specified in Step 7, Load the TACL configuration files, of the CO-ach Installation Guide. The Addenda Hold (ADDHOLD), Batch Header Hold (BTCHOLD) and Sub-Batch Header Hold (SBTCHOLD) files are also created using the relevant FUP edit files contained on the ACnnFUP subvolume.
CO-ach
Miscellaneous The Prenote Creation module (PSX210), the BAI Report module (PSX410), the Received Returns module (PSX530), and the MICR Draft Creation module (PSX630) can obtain file creation attributes from either the source code or from an assign and param added to a NetBatch Plus job. The hierarchy for determining file creation attributes are: 1. Look for the FC-DFLT-ASSIGN assign and the MAXEXT params first. 2. If the FC-DFLT-ASSIGN assign and MAXEXT params do not exist, or the values are invalid or not set, then use the constants defined within the source code module. The following cross reference table defines the source modules and the standard NetBatch jobs, delivered by ACI, which can be changed. CO-ach Program Module PSX210 (Prenote Creation) PSX410 (BAI Report) PSX530 (Received Returns) NetBatch Plus Job RUN210 RPTBAI RECDRETS RUN530 PSX630 (MICR Draft Creation) DISTALL MICRCR MICRDB RUN630
CO-ach
Before altering a NetBatch Plus job set, ensure that tape backups are made of the NetBatch Plus environment to allow for recovery.
CO-ach
The following examples will show logging on to NetBatch Plus (NBP), selecting the RUN210 job, and adding an assign and a param attachment to the RUN210 job. 1. Logon to NetBatch Plus (NBP)
NETBATCH-PLUS T9189D20 - (05NOV93) MAIN MENU 20Aug1995 SNP000 COPYRIGHT TANDEM COMPUTERS INCORPORATED 1988-1993 NBP User Name: COACH Password: Pathway: \CFS.$SNBP F16 Sign On F1 Defaults Set Details F2 Job Definition F3 Ad Hoc Job Selection F4 Catalogs F5 Calendar F6 Bulk Submit Environment F7 Bulk Submit F8 Utilities F9 Scheduler Interface F10 Reports F11 Security SF16 Sign Off, Exit All Screens: SF1-Screen Help SF3-Field Help SF13-Print SF15-Recover OK Instructions n Enter the NBP User Name n Press F16 (SIGN-ON) n Press SF5 (PASSWORD VALIDATION) SF5-Password Validation
CO-ach
2.
Password Validation
NETBATCH-PLUS
PASSWORD VALIDATION
20Aug1995 SNP170
User: COACH.TEST2
F5-Validate
Instructions n n n n Enter the User and Password F5 (VALIDATE) Password accepted message will display Press F16 (Return to Main Menu) Press F2 (Job Definition)
CO-ach
3.
Retrieving A Job Definition
NETBATCH-PLUS Set : __________ Scheduler: \CFS.$SBAT Class : COACH Owner : COACH.TEST2 Comment : Exec.Prg : In : Out : Volume Startup : Selpri : Drives : Wait : Restart : Stop On Abend: F1-Read F8-Delete OK
JOB DEFINITION Job Name: __________
20Aug1995 SNP030
/ OOOO
Pri : Lines : At/Af : Hold : Hold After :
High PIN: Pages : Time : Any User Submit : Stall : F6-Update F7-Read Set F14-Depend F15-Bulk Select
F2-Next F3-Submit F4-Add F9-Duplicate F13-Job Attachments
Instructions n Enter Set and Job Name n Enter User and Password n Press F1 (Read)
CO-ach
NETBATCH-PLUS
JOB DEFINITION
20Aug1995 SNP030
Set : ACH Job Name: RUN210 Scheduler : \CFS.$SBAT Class : COACH Owner : , / COACH.SUPER AAAA Comment : PSX210 CROSS REF PRENOTE CREATE ACH JOBS Exec.Prg : $SYSTEM.SYSTEM.TACL In : RUN210 Out : $S.#ACHBAT.RUN210 Volume : $DATA20.AC24OBEY Startup : Selpri : Drives : Wait : Restart : Stop On Abend : Pri : Lines : At/Af : 150 High PIN : Pages : Time : Any User Submit: Y Stall :
Hold : Hold After: N
F1-Read F2-Next F3-Submit F4-Add F8-Delete F9-Duplicate F13-Job Attachments Displayed Ok - Ready for use Instructions n Press F13 (Job Attachments)
F6-Update F7-Read Set F14-Depend F15-Bulk Select
CO-ach 5. Adding An Assign Attachment To A Job
NETBATCH-PLUS Option : ASSIGN Job Set : ACH ASSIGN Name : Catalog Set : Catalog Name : Physical Filename : Exclusion : Access : Prim Extent : Sec Extent : File Code : Record Size : Block Size : F1-Read F8-Delete OK
JOB ASSIGNS
20Aug1995 SNP030A / AAAA
Owner : COACH.SUPER Job Name: RUN210
F2-Next F4-Add F6-Update F7-Read Catalog F13-Choose Option F14-Depend F15-Bulk Select
Instructions n Enter FC-DFLT-ASSIGN in the ASSIGN Name: field n Enter the required primary extents value in the Prim Extent: field n Enter the required secondary extents value in the Sec Extent: field n Enter the required block size value in the Block Size: field n Press F4 (ADD) Note: NetBatch Plus validates Prim Extent, Sec Extent and Block Size for numeric values, but does NOT validate entered values for valid
CO-ach Enscribe value ranges.
The CO-ach File Creation module (FCREATE) validates the entered values for Prim Extent, Sec Extent and Block Size. If these values are invalid or blank, the PSX210 constants are used. The validation and fallback to source program constants are performed on a field by field basis unless the FC-DFLT-ASSIGN assign does not exist.
CO-ach
For further information on file creation and extents, refer to the Tandem Enscribe Programmers Manual, Section 4 - General File Creation and Access Information.
NETBATCH-PLUS
JOB ASSIGNS
20Aug1995 SNP030A / AAAA Job Set : ACHTEST
Option : ASSIGN Owner: COACH.TEST2 Job Name: RUN210 ASSIGN Name : FC-DFLT-ASSIGN Catalog Name : Physical Filename : Exclusion : Access : Prim Extent : 20 Sec Extent : 40 File Code : Record Size : Block Size : 4072
Catalog Set :
F1-Read F2-Next F4-Add F6-Update F13-Choose Option F14-Depend F15-Bulk Select Added Ok - Ready for use Instructions
F7-Read Catalog F8-Delete
n Press F13 (Choose Option) n Enter PARAM in the Option: field n Enter F13 (Choose Option)
CO-ach
6.
Adding A Param Attachment To A Job JOB PARAMS 20Aug1995 SNP030P / AAAA
NETBATCH-PLUS
Option : PARAM Owner : COACH.TEST2 Job Set : ACHTEST Job Name: RUN210 PARAM Name : MAXEXT Catalog Set : Catalog Name :
PARAM Value : 0100
F1-Read F8-Delete OK
F2-Next F4-Add F6-Update F7-Read Catalog F13-Choose Option F14-Depend F15-Bulk Select
Instructions n Enter MAXEXT in the PARAM Name: field n Enter the Maximum Extents value in the PARAM Value: field(a four digit numeric value) n Enter F4 (ADD) Repeat the steps to add the FC-DFLT-ASSIGN and MAXEXT for eac NetBatch Plus jobs requiring larger values for file creation than those defined in the program source file.
Section 5
Report Control The Report Control module (RPTCTL) manages the environment for the production of a specific group of reports within the CO-ach application. RPTCTL can optionally archive report data files and control the application interface to a disaster backup site maintained via Tandem's Remote Database Facility (RDF). The specific report data groups controlled by RPTCTL are shown in the following table:
Report Data Creator Entry Processing (PSX020) Distribution Processing (PSX042) General Ledger (PSX060) Consolidation (PSX070) Standard Report File Data (Name/location) $x.ACHDATA.RPT020A S $x.ACHDATA.RPT040A S Report ID C01/C05/C06/C07/C13/C15/C17 C08/C09/C10/C11/C12/C14/C18/C22
$x.ACHDATA.RPT060A S $x.ACHDATA.RPT070A S
C24/C25/C26/C27/C28 C32
SIn a multiprocess environment, there can be up to 36 report files that follow the naming convention for multiple processes. For example, the first RPT20 data file assign would be RPT020A and the 36th would be RPT0209 [RPT0nn<A-Z, 0-9>].
General Notes: 1. The RPT060 Job executes only once a day. 2. If an RDF backup site is being maintained, and based on your business needs, you may choose not to enable the RPT040 files on the remote site. The NetBatch Plus REMAKE Job can accomplish the same result.
______________________________________________________________________________ Last Modified - 03/09/99 Applied Communications, Inc 5-1
CO-ach
Report Control Configuration
NetBatch Plus Job RPT020 RPT040 RPT060 RPT070 RPTC01 RPTC03 RPTC08 RPTC11 RPTC09
Report Produced C01 / C05 / C06 / C07 / C13 / C15 / C17 C08 / C09 / C10 / C11 / C12 / C14 / C18 / C22 C24 / C25 / C26 / C27 / C28 C32 C01 C03 C08 C11 C09
DISTALL
C32
The DEFTABLE entries used by the RPTCTL module are:

Module DEFTABLE Record RPTCTL20 RPTCTL40 RPTCTL60 RPTCTL70 DF-WORK-CONTROL-FILENAME $x.AC24OBEY.SUBSRT20 $x.AC24OBEY.SUBSRT40 $x.AC24OBEY.SUBSRT60 $x.AC24OBEY.SUBSRT70 DF-RUN-OPTIONS YN0060 YN0060 YN0060 YN0060
CO-ach
The SUBSRTnn files are used to further refine the sorting of report data files by FASTSORT. Please refer to the Tandem FASTSORT manual (84144, Tools and Utilities Library). The DF-RUN-OPTIONS break out as follows: Position 1 is the ARCHIVE-ENABLED flag Valid values: 'Y' - Archive enabled. Causes current ACHDATA.RPT0n0 to be 'moved' to an archive subvolume prior to sorting new data into the RPT0n0. 'N' - Archive disabled. Causes the current ACHDATA.RPT0n0 to be purged and subsequently created prior to sorting new data into the RPT0n0. Position 2 is the RDF-ENABLED flag Valid values: 'Y' - RDF enabled. RPTCTL assumes that the RDFRPT module is currently running on the backup site. RPTCTL will attempt to communicate with the RDFRPT process on the back-up site, and will wait DELAY-TIME seconds for the RDFRPT process to reply. When the RDFRPT process replies, RPTCTL writes control records to the ACHDATA.RPT0n0A files to notify RDFRPT that RPT0n0A are going to be renamed. 'N' - RDF disabled. Position 3 thru 6 is the DELAY-TIME Valid values: '0000' thru '9999' seconds, numeric.
CO-ach
Parameters used by the Report Control module (RPTCTL)

PARAM Name ARCHIVE-ENABLED ARCHIVE-ID DATA-USAGE PROCESSING-DATE Valid Values 'Y', 'N' A-Z, 0-9 'ARCHIVE', 'BOTH', 'CURRENT', 'NEW' 'TODAY' or YYMMDD Fixed/Required/Optional Required Required, for DATA-USAGE of 'ARCHIVE' Required Required
KEEP-CURRENT RDF-ENABLED
'Y', 'N' 'Y', 'N'
Required, if RUN-PHASE is 'CLEAR' Required
DATA-USAGE valid values: NEW The current RPT0n0 file is renamed to an archive location, if the archive-enabled flag is 'Y'. New report data is appended to the end of the ACHDATA.RPT0nn; no archive is ever created. RPTCTL assumes that the current RPT0n0 file is used for producing reports. Thus no sorting, renaming or merging will be performed. If the previous execution of the RPT0nn NetBatch Plus job was against an archive, RPTCTL returns the archive file to the archive subvolume and returns the current RPT0n0 file back to the ACHDATA.RPT0n0 location. Processing is against an archived report file; an ARCHIVE-ID is required. A wild-card purge on a processing dates
BOTH
CURRENT -
ARCHIVE CLEAR -
CO-ach
Report Control Configuration archive report subvolume. The KEEPCURRENT param determines if the current days report files are purged.
KEEP-CURRENT valid values (relevant only in an RDF-ENABLED environment) Y Causes the RDFRPT process to be informed that the current days renamed files on the backup site should be kept. Causes the RDFRPT process to be informed that the current days renamed files on the backup site should be purged.
Parameters used by the RDF Report module (RDFRPT)

DEFTABLE Entry RDFRPT DF-RUN-OPTIONS 060 Fixed, Required, Optional Required
The RDFRPT runs on the backup site, but is configured in the DEFTABLE of the primary site. The RDFRPT executable (i.e., AC24LOAD.RDFRPT) must reside on the backup site. The RDFRPT process will monitor the RPT020, RPT040, RPT060 and RPT070 files on the RDF site. The primary site's DEFTABLE is accessed to obtain the assigns for the report work files and for the RPTCTL file. RDFRPT opens these filenames on the RDF site by using the system designated in its DF-PROGRAM-FILENAME. For further detail on configuring the reports in an RDF environment refer to Section 6 - Configuring CO-ach with RDF.
CO-ach Sample Report Job Configurations
NOTE: Params for all the RPT0n0 NetBatch jobs are obtained from the AC24MACS.PSX080 macro or the DEFTABLE. The params listed in the following table under NetBatch Plus Param can be added as param attachments and their values will override Macro/DEFTABLE settings. Scenario 1: A new RPT020 file should be created for each execution of the NetBatch job RPT020. This is the second time the RPT020 job has been executed. The RPT020 data file should be archived prior to the production of the RPT020 reports. A hot backup site is not implemented. The following table shows the NetBatch RPT020 job params and the DEFTABLE configuration:
NetBatch Plus Param Param Value DEFTABLE Record RPTCTL20 DATA-USAGE ARCHIVE-ENABLED RDF-ENABLED PROCESSING-DATE NEW Y N 950930 DF-RUN-PTIONS YN0060
Expected Result: 1. The old ACHDATA.RPT020 data file will be archived to $x.A950930.RPT020BZ. 2. The RPT020'<A> thru <9>' are sorted into a new RPT020 file. 3. RPT020 reports are output to the spooler.
CO-ach
Scenario 2: An incremental view of the RPT040 data file should be created, when the NetBatch RPT040 job is executed. This is the third time the RPT040 job has been executed. A hot backup site is not implemented. The following table shows the NetBatch RPT020 job params and the DEFTABLE configuration:
NetBatch Plus Param
Param Value
DEFTABLE Record RPTCTL40
DF-RUN-OPTIONS YN0060
DATA-USAGE ARCHIVE-ENABLED RDF-ENABLED PROCESSING-DATE
BOTH N N 950930
Expected Result: 1. The RPT040 file is renamed to RPT040ST. 2. The RPT040ST and RPT040'<A> thru <9>' are sorted into a new RPT040 file. 3. The RPT040ST file is purged. 4. The current ACHDATA.RPT040 data file will have data records appended to the existing ACHDATA.RPT040. 5. RPT040 reports are output to the spooler.
CO-ach
Scenario 3: Archive is enabled for RPT020 data files and the RPT020 NetBatch job has been executed ten times on the current processing day. The reports printed as part of the fifth run of RPT020 were mistakenly shredded by janitorial services and the RPT020 reports are needed now. An RDF backup site is operational. The following table shows the NetBatch RPT020 job params and the DEFTABLE configuration:
NetBatch Plus Param Param Value DEFTABLE Record RPTCTL20 DATA-USAGE PROCESSING-DATE ARCHIVE 951001 DF-RUNOPTIONS YY0020
ARCHIVE-ID
Expected Result: 1. The RPT020 file is renamed to a temporary area. 2. The RPT020 Archive file is temporarily renamed to RPT020. (The fifth RPT020 archive will be used as input for a RPT020 Job, i.e., $x.A951001.RPT020FZ) 3. RPT020 reports are output to the spooler. (Note: The amount of disc space needed to archive RPTnnn files must be determined in advance and diligently monitored.
CO-ach
Scenario 4: RPT070 completed successfully and the report jobs were about to be printed, but another application on the Tandem caused the spooler to fill. An operator, in attempting to reclaim spooler space, mistakenly deleted the RPT070 jobs. No other RPTnnn jobs have been executed after the RPT070 completed successfully. There is an urgent need for the RPT070 report. The following table shows the NetBatch RPT070 job params and the DEFTABLE configuration.
NetBatch Plus Param Param Value DEFTABLE Record RPTCTL70 DATA-USAGE PROCESSING-DATE CURRENT 951101 DF-RUN-OPTIONS YN0060
Expected Result: 1. The data currently in the ACHDATA.RPT070 will be reported on by the RPT070 Job. 2. RPT070 report output to the spooler.
CO-ach Work Files Managed by RPTCTL
File Type /Content Archive Renamed RPT0n0<A-9> Renamed RPT0n0<A-9>0 Temporary Sort of RPT0nn<V-9>X files Merge/Sort of RPT0nnST and RPT0nn<A-U> Temporary Rename of RPT0nn while report on archive file performed
Filename Naming Convention $x.Ayymmdd.RPTnn<archive-id>Z RPT0nn<A-9>X RPT0nn<A-9>R RPT0nnST RPT0nnSS RPT0nnTT
NOTE: The ST, SS, TT and RPT0n0 files will all reside on the same volume. Size considerations for the report data files are important.
CO-ach Tailoring the FASTSORT/FUP Environment
The RPTCTLnn modules make use of the Tandem FASTSORT software. When large volumes of report data are being produced it may be desirable to tailor the FASTSORT work environment. Sorting can be accomplished in a shorter time by taking advantage of under-utilized CPU power and DISC processes. Edit the AC24OBEY.SUBSTRnn files to tailor the FASTSORT environment. The most likely use of the SUBSRTnn files is to define the number of subsorts, their swap volumes, and the cpus in which to run. The SUBSRT files are delivered as empty files causing FASTSORT to execute with its default values. It is recommended that the SUBSRT files be tailored for each individual site. Please refer to the Tandem FASTSORT manual for more information (84144, Tools and Utilities Library). The following example alters the FASTSORT environment used in RPT020 processing. Two SUBSORTs are enabled, each having their own SCRATCH file and SWAP file. AC24OBEY.SUBSRT020 SUBSORT SUBSORT $DATA1.ACHSRT20.SCRATCH, SWAP $WORK1.ACHSWP20.SWAP $DATA2.ACHSRT20.SCRATCH, SWAP $WORK2.ACHSWP20.SWAP
RPTCTL starts and manages a FUP and a FASTSORT process. The configuration of the FUP process is controlled using params FUP-PRI and FUP-CPU. The configuration of the FASTSORT process is controlled using params FASTSORT-PRI and FASTSORT-CPU.
CO-ach
This page intentionally left blank.
CO-ach Section 6
Configuring RDF Report
Configuring RDF Report Overview This section describes the configuration steps to follow so the CO-ach application can use the Tandem Remote Disaster Facility (RDF) to programmatically control the report data files on a backup node. It is assumed, per the Tandem RDF requirements, that the primary and backup sites are 'mirrored.' Additionally, the volume names on the production Tandem and the remote Tandem must be the same name. CO-ach RDF functionality is delivered as DISABLED. RDF Report Install Procedures The main configuration changes for RDF Report involve updating the DEFAULT table on the primary site. The Online Pathway system must be running. At the TACL prompt: VOLUME $x.AC24INST OBEY DEFTABMD n Enter RPTCTL20 in the DF-PROGRAM-ID field (UPPER CASE) n F6 (Read Approximate) n F2 (Next Page) to Page 3
CO-ach
The DF-RUN-OPTIONS field is installed with the following setting YN0060 Position 1 is the ARCHIVE-ENABLED flag. Valid values: 'Y' - Archive enabled Causes the current ACHDATA.RPT0n0 to be 'moved' to an archive subvolume prior to sorting new data into the RPT0n0. 'N' - Archive disabled Causes the current ACHDATA.RPT0n0 to be purged and subsequently created prior to sorting new data into the RPT0n0. Position 2 is the RDF-ENABLED flag. Valid Values 'Y' - RDF enabled RPTCTL assumes the RDFRPT module is currently running on the backup site. RPTCTL will attempt to communicate with the RDFRPT process on the back-up site and will wait DELAY-TIME seconds for the RDFRPT process to reply. When the RDFRPT process replies, RPTCTL writes control records to the ACHDATA.RPT0n0A files to notify RDFRPT that RPT0n0A are going to be renamed. 'N' - RDF disabled. No RDF Processing enabled for RPT020. Position 3 thru 6 is the DELAY-TIME. Valid Values '0000' thru '9999' seconds, numeric.
CO-ach
n Change the second position to 'Y', RDF-ENABLED n Enter a value in DELAY-TIME n F14 (UPDATE) Repeat the above three steps for each report file to be include in the RDF processing (i.e., RPTCTL40, RPTCTL60 and RPTCTL70 Default table entries). RDF enabling can be controlled for each report data category (RPT020, RPT040, RPT060 and RPT070). The RPTnnn<A-9> must be TMF protected on the primary site. If a report data category will not be RDF protected, such as RPT040, the corresponding RPTCTLnn module DEFTABLE entry must have RDFENABLED set to 'N'. If a report data category will be RDF protected, such as RPT020, the corresponding RPTCTLnn module DEFTABLE entry must have RDFENABLED set to 'Y'. The final setting for each report will be dependent upon the site's specific requirements for disaster recovery.
CO-ach
If any of the report data categories are RDF protected, the module DEFTABLE for the RDFRPT must be updated on the primary site to reflect that the RDFRPT process will be running on the backup site. From DEFTABMD: n Enter RDFRPT in the DF-PROGRAM-ID field (for the Primary site) n F6 (Read Approximate) n F2 (Next Page) to Page 3 n Enter \node in the DF-OUTPUT-SUBVOL field where \node is the backup system name n Enter \node.$volume.AC24LOAD.RDFRPT in the DFPROGRAM-FILENAME field, again enter the backup node name. NOTE: If a swap volume is entered in the DF-SWAP-SUBVOL field, it must reside on the backup system and be fully qualified to include the backup system name. n F14 (UPDATE) Note: Having enabled RDF, the RDFRPT module must be started by a site specific NetBatch-Plus job, or by using the RUNRDFRP job delivered as part of the standard CO-ach install, or by modifying the AC24OBEY.START file. RDFRPT is started from the primary site. References CO-ach Installation Guide The Tandem documentation for establishing/maintaining Network Security between the primary and backup nodes.
CO-ach Section 7 GO-LIVE Reminders Overview
GO-LIVE Reminders
With so many tasks to be completed for a GO-LIVE event, some minor checks that may have major impacts to the success of the GO-LIVE may be missed. This section covers some areas to review well in advance of the GO-LIVE. - Determine the daily, weekly, monthly and 'holiday' volumes. - The system has sufficient DISC space and CPUs to handle the work loads. - The ACI Performance Group have reviewed the completed COach Sizing Questionnaire and the CO-ach System configuration. Recommendations have been reviewed and implementation planned. - The average production day/month has been defined and documented. The operations/support staff have been trained in the CO-ach environment and an operations run book is available including information for any custom modules/functionality. The audit department have conducted a review and have approved the various security and audit procedures. The Tandem data file security access has been reviewed and the ownership verified, including the use of the enhanced security feature SAFEGUARD. Any Tandem logon and CO-ach application operid's configured for the test environment should be removed and replaced by production id's as defined by the Security/Audit procedures.
_____________________________________________________________________________ Last Modified - 03/24/99 Applied Communications, Inc. 7-1
CO-ach -
GO-LIVE Reminders Procedures to monitor file, disc and spooler sizes have been defined and operational schedules implemented. Any test data should be purged from any production data volumes. The NetBatch Plus environment has been adjusted to reflect standard jobs and custom jobs for the production cycle, and each job has been fully exercised for the production cycle. The AC24XTRA.AUDIT macro has been run to enable TMF for all files that require TMF. The STATISTICS and SEQUENCE number fields of the Host Processing Center (HPC) file have been reset by either deleting and adding the PSX200 process or using an Enable program.
- The data files have been deleted using the PURGEDB macro.
______________________________________________________________________________ Last Modified 03/24/99 Applied Communications, Inc. 7-2
CO-ach Appendix A Custom CIF Installation Overview
Custom CIF Installation
The Custom Customer Information File (CCIF) is a purchasable add-on feature to the CO-ach product. The CCIF feature allows the CO-ach site to define, maintain and utilize custom customer information associated with CO-ach Customer or Batch Customization records. References CO-ach Installation Guide Custom CIF Subvolume AC24CCIF CC01 CCIFCONF CCIFCOPY CCIFDBLB CCIFDDL CCIFFUP CCIFIO CCIFLIB CCIFSCRN CCIFSVR CCIFSVRB INSTALL Custom CIF requester Pathway configuration file for CCIF Copy code for the CCIF add on modules CCIF DDL obey file CCIF DDL source file CCIF DDL FUP obey file CCIF file access subroutine LIBINDEX records to compile CCIF CCIF requester screens CCIF server source CCIF server bind file CCIF install macro
______________________________________________________________________________ Last Modified - 03/24/99 Applied Communications, Inc. A-1
CO-ach Custom CIF Installation Overview
This installation assumes that the user has installed the vanilla version of CO-ach and has subsequently purchased the CCIF feature. There should be one subvolume, AC24CCIF, on the CCIF feature tape. The INSTALL TACL macro provided on the AC24CCIF subvolume automates the replacement of stub source files with the CCIF enabled source files on the AC24CCIF subvolume. Restore Procedures Restore the AC24CCIF subvolume from the tape delivered. More complete procedures are outlined in the CO-ach Installation Guide. Install Prerequisites The CCIF install follows the typical standards for a CO-ach software install detailed in the CO-ach Installation Guide. The installation of the CCIF feature does not require a complete reinstall of the CO-ach system. However, it is advisable to have a recent backup of the CO-ach system available and to ensure that no CO-ach modules are running -- submit the NetBatch-Plus job SHUTDOWN. For further information and considerations, please consult the CO-ach Installation Guide.
CO-ach
Custom CIF install procedures 1. At the TACL prompt: $x.AC24CCIF.INSTALL where x is the disk volume on which the AC24CCIF subvol resides An error 80 reported during file creation indicates the TMF system is not operating. This must be corrected before continuing. 2. Check the peruse listings created by the install macro for correct completion. Note: The DF-CCIF-FILENAME of the Global DEFTABLE is provided with the assign for the Custom CIF file name. Skip Steps 3 through 5 if Custom CIF is part of an initial CO-ach installation. 3. We recommend you perform a compile all as specified in the COach Installation Guide. If you dont, the following modules that must be compiled, in the order shown, are: AC24DDL CCIFDDL AC24SCOB CF03 CCIFFUP CF04 CCIFDBLB CC01 PSXS0067 PSXS0102 PSX200
AC24SRC CCIFIO CCIFSVR PSXS0103 PSGDC02
4. After all compiles and binds are complete, verify the compiles. At TACL: CHECK_COMPILES 5. After the CCIF install is complete, delete the SPOOLER jobs.
CO-ach
Summary of INSTALL TACL macro All files on the AC24CCIF subvolume are moved existing CO-ach subvolumes. Stub source files are saved in the AC24CCIF subvolume and replaced by CCIF enabled source files from the AC24CCIF subvolume. A complete explanation of the install TACL macro processing is not given, but a summary is provided to allow the installer to analyze the macro and compensate for any site specific considerations. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. AC24COPY.CCIFCOPY is backed up to AC24CCIF.SAVECOPY. AC24COPY.CCIFDBLB is backed up TO AC24CCIF.SAVEDBLIB. AC24CCIF.CCIFCOPY replaces AC24OPY.CCIFCOPY. AC24CCIF.CCIFSCRN is duped to the AC24COPY subvolume. AC24CCIF.CCIFDDL is duped to the AC24DDL subvolume. AC24CCIF.CCIFDBLB is duped to the AC24DDL subvolume. AC24CCIF.CCIFFUP is duped to the AC24DDL subvolume. AC24CCIF.CC01 is duped to the AC24SCOB subvolume. AC24CCIF.CCIFSVR is duped to the AC24SRC subvolume. AC24CCIF.CCIFIO is duped to the AC24SRC subvolume. AC24CCIF.CCIFSVRB is duped to the AC24BIND subvolume. AC24CCIF.CCIFCONF is converted and written to AC24OBEY.CCIFCONF. AC24CCIF.CCIFLIB is copied to the LIBINDEX file (used in automated TACL compiles). Creates the CCIF (Custom CIF) file in the ACHDATA subvolume. Edits AC24BIND.COBLIBD and adds the line to include the CCIFIO subroutine when the COBLIBD is bound. Edits AC24OBEY.PATHCOLD and adds the line to create the CCIFsvr when the pathway is started via PATHCOLD. Edits AC24XTRA.PURGECTL and adds the line to purge data on the CCIF file. Edits AC24MAS.AUDIT and adds the line to DO_AUDIT for the CCIF file. Creates the CCIF FUP file in the AC24fup subvolume. Attempts to add the CCIF-SVR to the Pathway environment if Pathmon is running. Informs the user that CCIF is installed and that a compile all should be performed.
CO-ach
Errors during INSTALL If errors occur during INSTALL, correct the errors and rerun INSTALL. If the peruse report created by the INSTALL macro lists an error stating that the Pathmon process does not exist, this is OK. The install macro tries to add the server configuration dynamically if the Pathmon process is up and running.
CO-ach Appendix B Pre-funding Installation Overview
Pre-funding Installation
Pre-funding is a purchasable add-on feature to the CO-ach product. This feature provides Credit Transaction Pre-funding capabilities to avoid the Corporate credit risk and the settlement timing exposure associated with ACH processing. References CO-ach Installation Guide
Pre-funding Subvolume AC24PFND PFNDCOPY PFNDSCRN INSTALL Copy code for the PFND add on modules Pre-funding requester screens PFND install macro
______________________________________________________________________________ Last Modified - 03/24/99 Applied Communications, Inc. B-1
CO-ach Pre-funding Installation Overview
This installation discussion assumes that the user has installed the vanilla version of CO-ach and subsequently purchased the Pre-funding feature. There should be one subvolume on the Pre-funding feature tape, AC24PFND. The INSTALL TACL macro provided on the AC24PFND subvolume automates the replacement of stub source files, with the PFND enabled source files on the AC24PFND subvolume. The macro will prompt the user for the site specific configuration information and optionally automatically recompile the necessary program modules. Restore Procedures Restore the AC24PFND subvolume from the tape delivered. More complete procedures are outlined in the CO-ach Installation Guide. Install Prerequisites The PFND install follows the typical standards for a CO-ach software install detailed in the CO-ach Installation Guide. The installation of the Pre-funding feature does not require a complete re-install of the CO-ach system. However, it is advisable to have a recent backup of the CO-ach system available and to ensure no CO-ach modules are running submit the NetBatch-Plus job SHUTDOWN. For further information and considerations, please consult the CO-ach Installation Guide.
CO-ach Pre-Funding install procedures 1. At the TACL prompt: $x.AC24PFND.INSTALL
where x is the disk volume on which the AC24PFND subvol resides 2. Check the peruse listings created by the install macro for correct completion. Skip Steps 3 through 5 if Pre-funding is part of an initial CO-ach installation. 3. We recommend you perform a compile all as specified in the COach Installation Guide. If you dont, the following modules that must be compiled, in the order shown, are: AC24SCOB CF03 CF04 EX06 CUSTSVR PSX240
AC24SRC PSXS0075 PSXS0076 BCSTSVR The modules that must be bound are: AC24SRC PSXS0067 PSX200
4. After all the compiles and binds are complete, verify the compiles. At TACL: CHECK_COMPILES 5. After the PFND install is complete, delete the SPOOLER jobs.
CO-ach Summary of INSTALL TACL macro
All files on the AC24PFND subvolume are migrated to existing CO-ach subvolumes. Stub source files are deleted and replaced by PFND enabled source files from the AC24PFND subvolume. A complete explanation of the install TACL macro processing is not given, but a summary is provided to allow the installer to analyze the macro and compensate for any site specific considerations. 1. 2. 3. 4. 5. AC24COPY.PFNDCOPY is backed up to AC24PFND.SAVECOPY. AC24COPY.PFNDSCRN is backed up to AC24PFND.SAVESCRN. AC24PFND.PFNDCOPY replaces AC24COPY.PFNDCOPY. AC24PFND.PFNDSCRN replaces AC24COPY.PFNDSCRN. Informs the user that Pre-funding is installed and a compile all should be performed.
Errors during INSTALL If errors occur during INSTALL, correct the errors and rerun INSTALL.
CO-ach Appendix C
Netbatch Plus Site Specific Jobs
NetBatch Plus Site Specific Jobs Overview As part of the CO-ach First Time Installation Procedures two NetBatch sets are delivered: ACH and ACHTEST. A set contains a number of jobs. A job, when submitted, will cause an obey file (typically located on the AC24OBEY subvolume) to execute from the NetBatch Plus/TACL environment. The obey file on AC24OBEY typically contains some TACL statements and performs the execution of a macro on the AC24MACS subvolume. Once the expected production processing day is analyzed and defined, a number of Site specific jobs may be required such as a custom report. To take full advantage of the CO-ach environment, add any custom modules to the DEFTABLE and enter any required assigns and params to the custom modules DEFTABLE record. Adding custom modules require creating a related obey file on the AC24OBEY subvolume, a corresponding macro on the AC24MACS subvolume, and placing the executable object on the AC24LOAD subvolume. The following table includes examples of the files required to configure the Corporate Relationship Report (CRPRPT). Use this table as checklist for adding custom modules:
AC24SRC CRPRPT AC24LOAD CRPRPT AC24OBEY RUNCRPT AC24MACS CRPRPT NetBatch Plus Job RUNCRPT
Once the sites Endpoints have been determined, add a job for each
______________________________________________________________________________ Last Modified - 10/08/97 Applied Communications, Inc. C-1
CO-ach
Netbatch Plus Site Specific Jobs
separate distribution. The DISTALL job will perform a distribution for all Endpoints defined in the system, but the site may require a distribution to the same Endpoint several times throughout the day and/or at specific times. Various parameters are required for a successful distribution to occur. Two examples of NetBatch Plus Distribution jobs are FED and MICRDB. The common entity required for a distribution is the param attachment in NetBatch Plus. In the FED job, the param PARAM Name : ENDPOINT has a value of 011000015 -- the CO-ach Endpoint Id. By reviewing each of the required files in a job, as detailed for the CRPRPT job in the previous table, general idea of how to produce custom processing can be gained. There are also a number of excellent example files found in the AC24OBEY and AC24MACS subvolumes. Additionally, the spooler output produced by any of the Installation Verification Plan days can be a useful source of relevant information. References CO-ach First Time Installation Guide CO-ach Installation Verification Guide
______________________________________________________________________________ Last Modified - 10/08/97 Applied Communications, Inc. C-2
CO-ach Appendix D
Installing CO-ach with SUPERFILE
Installing CO-ach with SUPERFILE Overview The CO-ach product is designed to support extremely large transaction volumes. The Tandem file system Enscribe supports a maximum of 16 partitions for a data file. After performing an analysis of the potential transaction volumes the CO-ach system will process, it was determined that the Enscribe limit of 16 was unacceptable. The SUPERFILE product was designed and developed by ACI to manage over one hundred partitions for a data file. The need for the SUPERFILE product is based on the site specific volume of ACH processing. The use of the SUPERFILE product should always include discussion with the ACI performance group. This document outlines the steps involved in installing the SUPERFILE product in the CO-ach environment. It is assumed that the SUPERFILE product has been installed before the CO-ach with SUPERFILE install is performed. The SUPERFILE Product Installation Guide details the necessary steps to install the SUPERFILE product. The CO-ach system uses the SUPERFILE product with the CO-ach Transaction and History data files. References SUPERFILE Product Installation Guide CO-ach Installation Guide ACI SuperFile User's Guide CO-ach Install Verification Plan
______________________________________________________________________________ Last Modified - 10/08/97 Applied Communications, Inc. D-1
CO-ach
Prerequisites Prior to installation, the SUPERFILE product must be licensed by the ACI Software Management Group for the Tandem nodes where the software is to be used. Users of this install guide should be familiar with the Tandem RESTORE utility and have some knowledge of compiling and binding programs. The installation of the SUPERFILE product has been completed with the help of the SUPERFILE Product Installation Guide.
CO-ach Running The Installation TACL Macro.
The Tandem system should have a SUPERFILE subvolume installed. The SFUTIL object file must be compiled and bound with various CO-ach program modules. Locate the SFUTIL object file and the SFILINST install file on the AC24SUPR subvolume. The SFILINST file contains a TACL macro to aid in the installation of CO-ach and SUPERFILE. A stub or dummy SFUTIL object is provided in a vanilla install of the CO-ach product and is replaced with a SUPERFILE product SFUTIL object file. The necessary CO-ach modules are then compiled and bound. Before compilation, ensure that no CO-ach application modules are running. Please refer to the CO-ach Install Verification Plan Document and NetBatch Plus Installation Instructions for the procedures involved in accomplishing the shutdown of the CO-ach application. Instructions 1. At the TACL prompt: VOLUME AC24SUPR SFILINST $x.SUPRFILE where: $x is the volume on which the SUPRFILE subvol resides Summary Of The SFILINST TACL Macro. The macro checks to ensure that a SFUTIL file exists on the Tandem disk entered on the SUPERFILE subvolume. The stub AC24SUPR.SFUTIL file is renamed to OSFUTIL and the SFUTIL from the SUPERFILE subvolume is copied to the AC24SUPR subvolume. After the compiles and binds complete, the TACL macro executes the CHECK_COMPILES macro. The following modules will be compiled and bound:
2.
CO-ach
AC24SRC APPRVSVR PSX030 PSX062 PSX525 RELRSK 3.
EDTLSVR PSX041 PSX070 PSX530 RPTFMTR
HISTSVR PSX042 PSX080 PSXS0045 TRANINQ
MATCH PSX050 PSX515 PSXS0061 TXNDIO
PSX020 PSX060 PSX520 RECOVER2 TXNIO
Check the SPOOLER output from the binds for any errors. Post Software Installation. The software installation of CO-ach with SUPERFILE is complete. Next, the actual configuration of the SUPERFILE product and impacts to the CO-ach Transaction and History file must take place. Appendix E of the CO-ach Installation Guide provides a detailed configuration description of SUPERFILE enabled data files. For additional information refer to the ACI SuperFile User's Guide.
Appendix E
Configuring CO-ach with SUPERFILE Verify that SuperFile is installed. If it is not installed, refer to ACI's SuperFile Product Installation Guide and Appendix D of this document. Before continuing with this section, please read Section 1 and 2 of the SuperFile User's Guide. In addition to the following instructions in this section, refer to Section 3 of the SuperFile User's Guide. Perform the exact steps that follow in this section and use the SuperFile User's Guide for explanation and assistance.
_____________________________________________________________________________ Last Modified - 02/24/99 Applied Communications, Inc. E-1
CO-ach Configuring CO-ach with SUPERFILE Explanation:
Configuring CO-ach With SuperFile
1.
Instructions: If the SuperFile Pathway is not already running, start it. At TACL: VOLUME $x.SUPRFILE (or the subvolume where Superfile is located) TEDIT SFPMCONF Verify and update the values for Hometerm, Log1, Log2, and Swap BLDRQSTR Executes a macro to build the SuperFile Requester objects SFPMCOLD or SFPMCOOL n Use SFPMCOLD if changes were made to SFPMCONF n Use SFPMCOOL if no changes to SFPMCONF were necessary or after initial configuration. 2. Expected results: Superfile system will be running. Explanation: Building a SuperFiled TXN file The TXN file is a key sequenced file with three alternate key files. To create a SuperFiled TXN file, or a SPDS (SuperFile Partitioned Data Set), four (4) SCAT files must be built; one for the TXN file and one for each alternate key file. When creating the TXN SCAT file, specify the locations of the SCAT files for the alternate key files. The following steps detail how to create the SCAT files to reside on $x.ACHDATA and also detail how to place the SPDS on $x.ACHDATA. In a production environment, use different volumes for these files. Instructions: Creating the TXN SCAT files. At TACL: VOLUME $x.SUPRFILE SFONLINE (the following screen will display) n F15 (LOGON)
______________________________________________________________________________ Last Modified - 02/24/99 Applied Communications, Inc. E-2
CO-ach
SuperFile LOGON

96/04/06 13:06 Page 01 OF 01
Please press function key F15 to log on to the SuperFile PATHWAY environment. The SuperFile LOGON function ensures that no more than one user may access the SuperFile PATHWAY environment at any given time. If your LOGON request is denied, the SuperFile Server is already in session with another user/terminal.
*********************************************************************** F15-LOGON SF16-LOGOFF
3.
Explanation: The SCAT Definition screen will display, as shown below, with spaces in the fields. Instructions: Fill in the fields as shown. Replace the lower case letters with the correct system and volume names. Always fully qualify the filenames as the defaults may not be accurate. Note: The F2 - PRNTScat function spooler job incorrectly lists the KEY SPECS in ascending alphabetical order which mistakenly indicates an error in the Scat definition. Expected results:
CO-ach
SuperFile SCat DEFINITION

96/04/06 16:15 Page 01 OF 01
INITIAL SCat: __________________________________ FUTURE SCat: \system.$volume.ACHDATA.SCATTXN ALTERNATE SCat FILE NAMES 0: \system.$volume.ACHDATA.SCATTXSR 1: \system.$volume.ACHDATA.SCATTXTR 2: \system.$volume.ACHDATA.SCATTXSE 3: __________________________________ 4: __________________________________ 5: __________________________________ 6: __________________________________ 7: __________________________________ Audited? (Y or N) Y
File File File File File File File File
KEY KEY KEY U N NULL SPEC LEN OFST K V VALUE SR 60 18 Y Y 032 TR 74 78 Y Y 032 SE 18 152 Y Y 032 __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___
Please enter the fully qualified names of the initial and future SuperFile Catalogs and then press a function key. *********************************************************************** F2 -PRNTSCat SF1-CREATE SF2-READ SF8 -PREVSCRN SF15-REORG F3 -HELP SF13-SAVENEW SF16-LOGOFF LOGON Successful. 0101
4.
Explanation: Instructions: Press SF1 to create the TXN SCAT file. The following screen will display:
CO-ach
SuperFile I: LOW KEY/FILENAME DEFINITION

98/04/22 14:33 Page 01 OF 03
F: \system.$volume.ACHDATA.SCATTXN IDX KEYLEN USER DATA FILE NAME/LOW KEY VALUE --- -----------------------------------
IDX 0
USER DATA FILE NAME/LOW KEY VALUE
****************************************************************************** F2 -PRNTSCat F11-ADD SF2-READ F6 -NEXTPAGE SF8 -PREVSCRN SF15-REORG F14-CHG-KEY F12-DELETE SF14-CHG FILE SF6-PREVPAGE SF13-SAVENEW SF16-LOGOFF FUTURE SCAT file created successfully. 0103
5.
Explanation: Define the SuperFiled TXN files or the SPDS. Instruction: n Enter \system.$volume.ACHDATA.TXN000 in the USER DATA FILE NAME field n Enter 0 in the LOW KEY VALUE field which is on the next line at the first position n Press F11 (ADD) n Enter \system.$volume.ACHDATA.TXN001 in the USER DATA FILE NAME field. n Enter 5 on the next line at the first position. n Press F11 (ADD) The following shows how the screen will look after adding both entries:
CO-ach
SuperFile I: IDX --1 0 2 5 1 \system.$volume.ACHDATA.TXN001 LOW KEY/FILENAME DEFINITION

98/04/22 14:33 Page 01 OF 03
F: \system.$volume.ACHDATA.SCATTXN KEYLEN USER DATA FILE NAME/LOW KEY VALUE ----------------------------------1 \system.$volume.ACHDATA.TXN000
IDX 0
USER DATA FILE NAME/LOW KEY VALUE \system.$volume.ACHDATA.TXN001
5 ****************************************************************************** F2 -PRNTSCat F11-ADD SF2-READ F6 -NEXTPAGE SF8 -PREVSCRN SF15-REORG F14-CHG-KEY F12-DELETE SF14-CHG FILE SF6-PREVPAGE SF13-SAVENEW SF16-LOGOFF Table entry added successfully. 0104
6.
Explanation: Save the changes to the TXN SCAT file. Instruction: Press SF13
7.
Expected results: The SCAT for the TXN file is complete. Explanation: Create the alternate key SCAT files. Instruction: n Press SF8 to return to the SCat DEFINITION screen n Fill in the fields as shown; blank out any previously entered data. n Press SF1 to create the SCAT file for the alternate key.
CO-ach

96/04/06 21:24 Page 01 OF 01
INITIAL SCat: __________________________________ FUTURE SCat: \system.$volume.ACHDATA.SCATTXSR ALTERNATE SCat FILE NAMES 0: __________________________________ 1: __________________________________ 2: __________________________________ 3: __________________________________ 4: __________________________________ 5: __________________________________ 6: __________________________________ 7: __________________________________ KEY KEY SPEC LEN __ ___ __ ___ __ ___ __ ___ __ ___ __ ___ __ ___ __ ___ Audited? (Y or N) Y KEY U N NULL OFST K V VALUE ____ _ _ ___ ____ _ _ ___ ____ _ _ ___ ____ _ _ ___ ____ _ _ ___ ____ _ _ ___ ____ _ _ ___ ____ _ _ ___
Please enter the fully qualified names of the initial and future SuperFile Catalogs and then press a function key. *********************************************************************** F2 -PRNTSCat SF1-CREATE SF2-READ SF8 -PREVSCRN SF15-REORG F3 -HELP SF13-SAVENEW SF16-LOGOFF
8.
Explanation: The LOW KEY/FILENAME DEFINITION screen will display. Instruction: n Enter \system.$volume.ACHDATA.TXNSR0 in the USER DATA FILE NAME field n Enter SR in the LOW KEY VALUE field which is on the next line at the first position. n Press F11 (ADD) n Enter \system.$volume.ACHDATA.TXNSR1 in the USER DATA FILE NAME field n Enter SRG on the next line in the first position. n Press F11 (ADD) Expected results: The following shows how the screen will look after adding all entries :
CO-ach
SuperFile I: LOW KEY/FILENAME DEFINITION

98/04/22 14:33
F: \system.$volume.ACHDATA.SCATTXSR IDX KEYLEN USER DATA FILE NAME/LOW KEY VALUE --- -- ---------------------------------1 2 \system.volume.ACHDATA.TXNSR0 2 3 \system.volume.ACHDATA.TXNSR1
SR SRG
IDX 2
USER DATA FILE NAME/LOW KEY VALUE $system.$volume.ACHDATA.TXNSR1
SRG ****************************************************************************** F2 -PRNTSCat F11-ADD SF2-READ F6 -NEXTPAGE SF8 -PREVSCRN SF15-REORG F14-CHG-KEY F12-DELETE SF14-CHG FILE SF6-PREVPAGE SF13-SAVENEW SF16-LOGOFF Table entry added successfully. 0104
9.
Explanation: Save changes to the new alternate SR key. Create the SCAT files for the TR and SE alternate keys. Instruction: n Press SF13 n Follow steps 7 through 9 to create the other two SCAT files but substituting the SR with TR & SE and the SRG with TR5 & SE5 - see the following examples: n DONT FORGET TO PRESS SF13 AFTER EACH F11 (ADD), Expected results: Screen prints of the files are shown below:
CO-ach

96/04/06 21:24 Page 01 OF 01
INITIAL SCat: __________________________________ FUTURE SCat: \system.$volume.ACHDATA.SCATTXTR ALTERNATE SCat FILE NAMES 0: __________________________________ 1: __________________________________ 2: __________________________________ 3: __________________________________ 4: __________________________________ 5: __________________________________ 6: __________________________________ 7: __________________________________ Audited? (Y or N) Y
KEY KEY KEY U N NULL SPEC LEN OFST K V VALUE __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___
SuperFile I: SuperFile IDX KEYLEN 14:33 --- -1 2 I: TR IDX KEYLEN 2 3 --- -TR5 1 2 SE 2 3 IDX SE5 0 TR5
LOW KEY/FILENAME DEFINITION
98/04/22 14:33
F: \system.$volume.ACHDATA.SCATTXTR LOW KEY/FILENAME DEFINITION 98/04/22 USER DATA FILE NAME/LOW KEY VALUE ---------------------------------\system.volume.ACHDATA.TXNTR0 F: \system.$volume.ACHDATA.SCATTXSE USER DATA FILE NAME/LOW KEY VALUE \system.volume.ACHDATA.TXNTR1 ---------------------------------\system.volume.ACHDATA.TXNSE0 \system.volume.ACHDATA.TXNSE1 USER DATA FILE NAME/LOW KEY VALUE $system.$volume.ACHDATA.TXNTR1
IDX USER DATA FILE NAME/LOW KEY VALUE ****************************************************************************** 0 $system.$volume.ACHDATA.TXNSE1 F2 -PRNTSCat F11-ADD SF2-READ F6 -NEXTPAGE SF8 -PREVSCRN SF15-REORG SE5 F14-CHG-KEY F12-DELETE SF14-CHG FILE SF6-PREVPAGE SF13-SAVENEW SF16-LOGOFF Table entry added successfully. 0104 ****************************************************************************** F2 -PRNTSCat F11-ADD SF2-READ F6 -NEXTPAGE SF8 -PREVSCRN SF15-REORG F14-CHG-KEY F12-DELETE SF14-CHG FILE SF6-PREVPAGE SF13-SAVENEW SF16-LOGOFF Table entry added successfully. 0104
CO-ach
SuperFile
SCat DEFINITION
96/04/06 21:24 Page 01 OF 01
INITIAL SCat: __________________________________ FUTURE SCat: \system.$volume.ACHDATA.SCATTXSE ALTERNATE SCat FILE NAMES 0: __________________________________ 1: __________________________________ 2: __________________________________ 3: __________________________________ 4: __________________________________ 5: __________________________________ 6: __________________________________ 7: __________________________________ Audited? (Y or N) Y
KEY KEY KEY U N NULL SPEC LEN OFST K V VALUE __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___ __ ___ ____ _ _ ___
10.
Explanation: Exit the SFONLINE Instruction: SF16
CO-ach 11.
Explanation: Alter the file code of the newly created SCAT files from 19314 to 19315. Instruction: At TACL VOLUME $x.ACHDATA FUP ALTER SCATTXN, CODE 19315, AUDIT ( Ignore open error 4 ) FUP ALTER SCATTXSE, CODE 19315, AUDIT FUP ALTER SCATTXSR, CODE 19315, AUDIT FUP ALTER SCATTXTR, CODE 19315, AUDIT FILEINFO SCATTX* Expected results: The subvolume should now contain the following files:
$volume.ACHDATA SCATTXN SCATTXNSE SCATTXNSR SCATTXNTR Code 19315A 19315A 19315A 19315A EOF Last Modification Owner RWEP Pext SExt 4096 7-Sep-97 10:34:30 146,253 NCCC 4 4 4096 7-Sep-97 10:34:30 146,253 NCCC 4 4 4096 7-Sep-97 10:34:30 146,253 NCCC 4 4 4096 7-Sep-97 10:34:30 146,253 NCCC 4 4
12.
Explanation: For an existing install, it is recommended to purge the TXN files that will not be used since the TXN files are now SuperFiled. Instruction: At TACL: VOLUME $x.ACHDATA FUP PURGE (TXN, TXN0, TXN1, TXN2) (answer Y to question)
CO-ach 13.
Explanation: Create the SCAT TXN and alternate key data files. The TXN files indicated by the SCATTXN file are configured the same as the TXNA file without alternate keys. The alternate key files indicated by SCATTXSE, SCATTXSR, and SCATTXTE will be identical to the original alternate keys. Use the AC24FUP.TXN file as a template for the ACHDATA.TXNFUP create file. Instruction: At TACL: FUP DUP $x.AC24FUP.TXN, $x.ACHDATA.TXNFUP EDIT ACHDATA.TXNFUP Make the changes shown on the following page n delete the bolded text n insert the italicized text
< SCHEMA PRODUCED DATE - TIME : 3/07/97 15:48:45 < SECTION TXN-REC < Record TXN-REC created on 03/07/97 at 15:13 < This is the TRANSACTION File. < Created 03/07/97 to merge the DTRAN and HISTORY files for Point < CDC Release 2.4. The Primary Key is the Audit Key. < SR is the Account Key, TR is the Trace Key and SE < is the Settlement Key. The Distribution Key < resides in the programmatically controlled TXND < 'alternate key' file. RESET SET ALTKEY ( "SR", KEYOFF 18, KEYLEN 60, FILE 0, UNIQUE, NULL " " ) SET ALTKEY ( "TR", KEYOFF 78, KEYLEN 74, FILE 1, UNIQUE, NULL " " ) SET ALTKEY ( "SE", KEYOFF 152, KEYLEN 18, FILE 2, UNIQUE, NULL " " ) SET NO ALTCREATE SET ALTFILE ( 0, TXN0 ) SET ALTFILE ( 1, TXN1 ) SET ALTFILE ( 2, TXN2 ) SET TYPE K SET KEYLEN 18 SET REC 674 SET BLOCK 4096 SET IBLOCK 4096 SET EXT( 184, 20 ) SET AUDIT SET MAXEXTENTS 100 SET AUDITCOMPRESS CREATE TXN CREATE TXN000 and CREATE TXN001 RESET SET TYPE K ______________________________________________________________________________ Last Modified - 02/24/99 Applied Communications, Inc. E-12
CO-ach
SET KEYLEN 62 SET REC 80 SET BLOCK 2048 SET IBLOCK 2048 SET EXT( 36, 4 ) SET AUDIT SET MAXEXTENTS 100 SET AUDITCOMPRESS CREATE TXN0 RESET SET TYPE K SET KEYLEN 76 SET REC 94 SET BLOCK 2048 SET IBLOCK 2048 SET EXT( 36, 4 ) SET AUDIT SET MAXEXTENTS 100 SET AUDITCOMPRESS CREATE TXN1 RESET SET TYPE K SET KEYLEN 20 SET REC 38 SET BLOCK 2048 SET IBLOCK 2048 SET EXT( 36, 4 ) SET AUDIT SET MAXEXTENTS 100 SET AUDITCOMPRESS CREATE TXN2
CREATE TXNSR0 and CREATE TXNSR1
CREATE TXNTR0 and CREATE TXNTR1
CREATE TXNSE0 and CREATE TXNSE1
Expected results: The ACHDATA.TXNFUP create file should now look like this:
RESET SET TYPE K SET KEYLEN 18 SET REC 674 SET BLOCK 4096 SET IBLOCK 4096 SET EXT( 184, 20 ) SET AUDIT SET MAXEXTENTS 100 SET AUDITCOMPRESS CREATE TXN000 CREATE TXN001 _____________________________________________________________________________ Last Modified - 02/24/99 Applied Communications, Inc. E-13
CO-ach
RESET SET TYPE K SET KEYLEN 62 SET REC 80 SET BLOCK 2048 SET IBLOCK 2048 SET EXT( 36, 4 ) SET AUDIT SET MAXEXTENTS 100 SET AUDITCOMPRESS CREATE TXNSR0 CREATE TXNSR1 RESET SET TYPE K SET KEYLEN 76 SET REC 94 SET BLOCK 2048 SET IBLOCK 2048 SET EXT( 36, 4 ) SET AUDIT SET MAXEXTENTS 100 SET AUDITCOMPRESS CREATE TXNTR0 CREATE TXNTR1 RESET SET TYPE K SET KEYLEN 20 SET REC 38 SET BLOCK 2048 SET IBLOCK 2048 SET EXT( 36, 4 ) SET AUDIT SET MAXEXTENTS 100 SET AUDITCOMPRESS CREATE TXNSE0 CREATE TXNSE1
CO-ach 14. Explanation: Build the SCAT data file. Instruction: At TACL FUP /IN ACHDATA.TXNFUP/ Fileinfo ACHDATA.TXN*
Expected results: The subvolume should now contain the following files: $volume.ACHDATA
TXN000 TXN001 TXNFUP TXNSE0 TXNSE1 TXNSR0 TXNSR1 TXNTR0 TXNTR1 Code EOF Last Modification Owner RWEP PExt SExt 0A 0 7-Sep-97 10:34:39 146,253 NCCC 94 10 0A 0 7-Sep-97 10:34:39 146,253 NCCC 94 10 101 3218 7-Sep-97 10:34:42 146,253 NCCC 2 2 0A 0 7-Sep-97 10:34:42 146,253 NCCC 10 2 0A 0 7-Sep-97 10:34:30 146,253 NCCC 10 2 0A 0 7-Sep-97 10:34:41 146,253 NCCC 10 2 0A 0 7-Sep-97 10:34:41 146,253 NCCC 10 2 0A 0 7-Sep-97 10:34:40 146,253 NCCC 30 4 0A 0 7-Sep-97 10:34:40 146,253 NCCC 30 4
15.
Explanation: The SuperFiled TXN file set has been created. Change the DEFTABLE to indicate the new SuperFile TXN file. Instruction: If the pathway is not up and running, start it. At TACL: OBEY AC24OBEY.PATHCOOL OBEY AC24INST.DEFTABGL n F4 (Read) the first record (the Global Base record) n F2 (Page Down) several times to page 6 n Enter $x.ACHDATA.SCATTXN in the DF-TXN-FILENAME n Press F14 (UPDATE) Record updated OK n Press SF16 (EXIT)
CO-ach Building a SuperFiled TXND file.
The TXND file is a key sequenced file with no alternate key files. To create a SuperFiled TXND file, or a SPDS (SuperFile Partitioned Data Set), one (1) SCAT file must be built; for the TXND file. The following steps detail how to create the SCAT file to reside on $x.ACHDATA and also detail how to place the SPDS on $x.ACHDATA. In a production environment, use different volumes for these files. 1. Explanation: Create the TXND SCAT file. Instruction: At TACL VOLUME $x.SUPRFILE SFONLINE (the following screen will display) n F15 (LOGON)
SuperFile LOGON 96/04/06 13:06 Page 01 OF 01
Please press function key F15 to log on to the SuperFile PATHWAY environment. The SuperFile LOGON function ensures that no more than one user may access the SuperFile PATHWAY environment at any given time. If your LOGON request is denied, the SuperFile Server is already in session with another user/terminal.
*********************************************************************** F15-LOGON SF16-LOGOFF BLOCK
CO-ach 2.
Explanation: The SCAT Definition screen will display, as shown below, with spaces in the fields. Instruction: Fill in the fields as shown. Replace the lower case letters with the correct system and volume names. Always fully qualify the filenames as the defaults may not be accurate.
SuperFile
SCat DEFINITION
96/04/06 16:15 Page 01 OF 01
INITIAL SCat: __________________________________ FUTURE SCat: \system.$volume.ACHDATA.SCATTXND ALTERNATE SCat FILE NAMES 0: __________________________________ 1: __________________________________ 2: __________________________________ 3: __________________________________ 4: __________________________________ 5: __________________________________ 6: __________________________________ 7: __________________________________ Audited? (Y or N) Y U K _ _ _ _ _ _ _ _ N V _ _ _ _ _ _ _ _ NULL VALUE ___ ___ ___ ___ ___ ___ ___ ___
KEY KEY KEY SPEC LEN OFST __ ___ ____ __ ___ ____ __ ___ ____ __ ___ ____ __ ___ ____ __ ___ ____ __ ___ ____ __ ___ ____
Please enter the fully qualified names of the initial and future SuperFile Catalogs and then press a function key. *********************************************************************** F2 -PRNTSCat SF1-CREATE SF2-READ SF8 -PREVSCRN SF15-REORG F3 -HELP SF13-SAVENEW SF16-LOGOFF LOGON Successful. 0101 BLOCK
CO-ach
3.
Explanation: Create the TXND SCAT file. Instruction: Press SF1 to create the HISTORY SCAT file. The following screen will display:
SuperFile I: LOW KEY/FILENAME DEFINITION 98/04/22 14:33 Page 01 OF 03
F: \system.volume.ACHDATA.SCATTXND IDX KEYLEN USER DATA FILE NAME/LOW KEY VALUE --- -- ----------------------------------
IDX 0
USER DATA FILE NAME/LOW KEY VALUE
****************************************************************************** F2 -PRNTSCat F11-ADD SF2-READ F6 -NEXTPAGE SF8 -PREVSCRN SF15-REORG F14-CHG-KEY F12-DELETE SF14-CHG FILE SF6-PREVPAGE SF13-SAVENEW SF16-LOGOFF FUTURE SCAT file created successfully.
0103
CO-ach
4.
Explanation: Define the SuperFiled TXND files or the SPDS. Instruction: n Enter \system.$volume.ACHDATA.TXND000 in the USER DATA FILE NAME field n Enter 000 in the LOW KEY VALUE field which is on the next line at the first position. n Press F11 (ADD) INSTALL NOTE: The 001 is ACIs value, client value will vary based upon their data. n Enter \system.$volume.ACHDATA.TXND001 in the USER DATA FILE NAME field. n Enter 001 in the LOW KEY VALUE field n Press F11 (ADD) Expected results: The following shows how the screen will look after adding both entries:
SuperFile I: IDX --1 000 2 001 3 \system.$volume.ACHDATA.TXND001 LOW KEY/FILENAME DEFINITION 98/04/22 14:33 Page 01 OF 03
F: \system.volume.ACHDATA.SCATTXND KEYLEN USER DATA FILE NAME/LOW KEY VALUE ---------------------------------3 \system.$volume.ACHDATA.TXND000
IDX 0 001
USER DATA FILE NAME/LOW KEY VALUE \system.$volume.ACHDATA.TXND001
****************************************************************************** F2 -PRNTSCat F11-ADD SF2-READ F6 -NEXTPAGE SF8 -PREVSCRN SF15-REORG F14-CHG-KEY F12-DELETE SF14-CHG FILE SF6-PREVPAGE SF13-SAVENEW SF16-LOGOFF Table entry added successfully. 0104
CO-ach
5.
Explanation: Save the changes to the new TXND SCAT file. Instruction: Press SF13. Expected results: The SCAT for the TXN file is complete. Next, create the alternate key SCAT files. Explanation: Exit the Superfiles Online System. Instruction: SF16 Explanation: Alter the file code of the newly created SCAT files from 19314 to 19315. Instruction: At TACL: VOLUME $x.ACHDATA FUP ALTER SCATTXND, CODE 19315, AUDIT FILEINFO ACHDATA.SCATTXND Expected results: The subvolume should contain the following files:
6. 7.
$volume.ACHDATA SCATTXND Code 19315A EOF Last Modification Owner RWEP PExt SExt 4096 7-Sep-97 10:34:30 146,253 NCCC 4 4
8.
Explanation: For an existing install, it is recommended to purge the TXND files that will not be used since the TXND files are now superfiled. Instruction: At TACL VOLUME $x.ACHDATA FUP PURGE TXND (answer Y to question)
CO-ach 9.
Explanation: Create the SCAT TXND file. The TXND file indicated by the SCATTXND file are configured the same as the TXND file. Use the AC24FUP.TXND file as a template for the ACHDATA.TXNDFUP create file. Instruction: At TACL FUP DUP $x.AC24FUP.TXND, $x.ACHDATA.TXNDFUP EDIT ACHDATA.TXNDFUP Make the changes shown on the following page n delete the bolded text n insert the italicized text
< SCHEMA PRODUCED DATE - TIME : 3/07/97 15:48:49 < SECTION TXND-REC < Record TXND-REC created on 03/07/97 at 15:13 < This is the TRANSACTION DISTRIBUTION File. < Created 03/07/97 to merge the DTRAN and HISTORY files for Point < CDC Release 2.4. The Primary Key is the Distribution < Key. This file is a programmatically controlled < 'alternate key' file to the TXN file. It also < contains the data necessary to enable Distribution < (PSX050) to format NACHA using only the TXND data. < This enables continued high performance by PSX050 < as the additional I/O to read TXN is not needed. RESET SET TYPE K SET KEYLEN 50 SET REC 506 SET BLOCK 4096 SET IBLOCK 4096 < Note that the extents are twice as large as TXN's extents. This < is an example of sizing TXND for Memopost on every TXN record. SET EXT( 368, 40 ) SET AUDIT SET MAXEXTENTS 100 SET AUDITCOMPRESS CREATE TXND CREATE TXND000 and CREATE TXND001
CO-ach
Expected results: The ACHDATA.TXNDFUP create file should now look like this:
RESET SET TYPE K SET KEYLEN 50 SET REC 506 SET BLOCK 4096 SET IBLOCK 4096 < Note that the extents are twice as large as TXN's extents. This < is an example of sizing TXND for Memopost on every TXN record. SET EXT( 368, 40 ) SET AUDIT SET MAXEXTENTS 100 SET AUDITCOMPRESS CREATE TXND000 CREATE TXND001
10.
Explanation: Build the SCAT data files. Instruction: At TACL FUP /IN ACHDATA.TXNDFUP/ FILEINFO ACHDATA.TXND* Expected results: The subvolume should now contain the following files:
$volume.ACHDATA TXND000 TXND001 TXNDFUP Code 0A 0A 101 EOF Last Modification Owner RWEP PExt SExt 0 7-Sep-97 11:38:10 146,253 NCCC 184 20 0 7-Sep-97 11:38:10 146,253 NCCC 184 20 954 7-Sep-97 11:40:11 146,253 NCCC 2 2
CO-ach 11.
Explanation: The SuperFiled TXN file set has been created. Change the DEFTABLE to indicate the new SuperFile TXN file. Instruction: If the pathway is not up and running, start it. At TACL: OBEY AC24OBEY.PATHCOOL OBEY AC24INST.DEFTABGL n F4 (Read) the first record (the Global Base record) n F2 (Page Down) to page 2 n Enter $x.ACHDATA.SCATTXND in the DF-TXND-FILENAME n Press F14 (UPDATE) Record updated OK n Press SF16 (EXIT)
CO-ach Appendix F
Modification History
MODIFICATION HISTORY Rev Date 08/14/97 08/18/97 09/02/97 Initials DMG DMG DMG History Converted documents to Table Format Section 1 - Added additional modules where compile warnings can be expected. Section 1 - CO-ach Install 1. Added restore of CO-ach system. 2. Removed step for fup alter (done programatically) 3. Moved purge of spoolcom to after a check for compiles. Section 1 - CO-ach Install 1. Step 6 emphasized use of Upper Case. 2. Step 9 clarification of assign for DataExpress users 3. Step 13 changed results of ac24inst.deftable to 286 4. Step 15 separate instructions for DataExpress, added spooler name ($s) and increased Object files checked from 224 to 234 5. Step 16 added warning for TACLLIB ddl 6. Step 26 added information about possible Pathcom error. Appendix E - Configuring CO-ach with Superfile 1. Updated in new format 2. Multiple changes due to DTRAN / HISTORY files no longer used, i.e., TXN Section 1 - CO-ach Install 1. Updated with cosmetic changes 2. Numbering changes
Applied Communications, Inc. F-1
09/03/97
DMG
09/16/97
DMG
09/24/97
DMG
Last Modified - 03/24/99
CO-ach 09/30/97 DMG
Modification History Appendix E - Configuring CO-ach with Superfiles 1. Corrected Key Len for SCATTXSE (18) 2. Cosmetic changes Appendix D - Installing CO-ach with Superfile 1. Added Last Modified in footer 2. Updated list of modules to compile.
10/06/97
DMG
Section 1 - CO-ach First Time Installation Procedures 1. Corrected references to step numbers 2. Consistency in restore commands 3. Spelling error Section 6 - Configuring RDF Report 1. Changed 23 references to 24 2. Added Last Modified footer Appendix A - Custom CIF Installation 1. Added Last Modified footer
10/08/97
DMG
10/09/97
DMG
Section 6 - Configuring RDF Report 1. Added verbage requiring that the production systems volume name must mach the remote systems volume name. Section 1 - CO-ach Installation 1. Moved Warning message regarding the monitoring the spooler. 2. Added note the utility CHECK_COMPILES. You will get different results based upon features purchased and/or compile options. Section 1 - CO-ach Install 1. Added title to Step 3 - Restore Superfiles 2. Step 14 - Added NOTE regarding dummy sfutil. Section 1 - CO-ach Install 1. Step 1 - added volume designation, i.e., $x
10/09/97
DMG
10/15/97
DMG
10/22/97
DMG
______________________________________________________________________________ Last Modified - 03/24/99 Appplied Communications, Inc. F-2
CO-ach
Modification History 2. Step 19 - Added more explicit instructions regarding editing of pathconf & enabconf Section 1 - CO-ach Install 1. Corrected step number for CCIF reference in Step 14. Appendix A - Custom CIF Installation 1. Reworded Step 3 regarding compiles. 2. Corrected PSXS103 TO PSXS0103 Appendix B - Pre-Funding Installation 1. Reworded Step 3 regarding copiles 2. Removed CF54 & CF53 modules for compiles they are contained within CF03 & CF04.
10/24/97
DMG
11/11/97
DMG
12/30/97
DMG
Section 1 - CO-ach Install 1. Corrected step 5 for the pending file output subvols. Section 6 - Configuring RDF Report 1. Changed verbiage on page 6-4 to add specific reference to backup system name. Appendix E - Configuring CO-ach with Superfiles 1. Changed Keylen from 0 to 1 on Step 4. 2. Corrected SCAT files names on Step 11 3. Clarified the TXND file status on Step 14. Section 1 - CO-ach Install Doc 1. Corrected step number references regarding adding optional featuresin Step 14, i.e., steps 24 through 28 2. On Step 15, adding the RSKPROC to the list of COBOL 390 warnings. 3. On Step 15, corrected the CHECK_COMPILES output. Section 5 - Reports Doc 1. GENERAL NOTES - step 2. Changed the note regarding running RPT040 on the RDF system to
Applied Communications, Inc. F-3
5/8/98
CHB
5/12/98
DMG
5/18/98
DMG
CO-ach
Modification History indicate it should be based on the clients business needs.
06/08/98
DMG
Section 4 - Extended Configuration 1. Removed note regarding the number of PSX062s that could be configured. Appendix E - Configuring CO-ach with Superfiles 1. Added Step 11 which involves modifying the DEFTABLE to include the TXND file. Appendix E - Configuring CO-ach with Superfiles 1. Modified Step 5. Changed LOW KEY VALUE for TXND001 to 001. This is ACIs value, the clients value will vary depending upon their data. 1. Section 4 & 5 - correct spacing for the footers. 1. Section 1 - Added a step for updating the PCONFIG especially for clients that will not be running the IVP. Section 1 - CO-ach Install Doc 1. Step 14 - Added page break 2. Step 21 - Removed pathcool since a pathcold was already performed 3. Step 21 - Added fup alter of datetyd, audit 4. Step 15 - Added ENABLE Warning Section 1 - CO-ach Install Doc 1. Step 21 - Corrected the Expected Results on the FUP LOADs. Section 1 - CO-ach Install Doc 1. Step 21 - Corrected the Expected Results. Section 3 - NetBatch-Plus Installation. 1. Step 3 - Changed AC23 to AC24 Section 5 - Report Control
06/18/98
DMG
07/21/98
DMG
08/19/98 10/23/98
DMG DMG
12/12/98
DMG
01/21/99
DMG
03/09/99
DMG
______________________________________________________________________________ Last Modified - 03/24/99 Appplied Communications, Inc. F-4
CO-ach
Modification History 1. Modified the Report Data Creator table to reflect PSX042 - Distribution Processing and PSX060 General Ledger Appendix E - Superfile 2.1 Configuration 1. Step 9 - Added a bold reminder regarding the pressing the F13 key to ADD the record. 2. Added Step 11 - Added to the section on Building a SuperFiled TXND file .
03/24/99
DMG
Section 3 - NetBatch-Plus Installation. 1. Step 4 - Used new TODAY param value Section 7 - GO-LIVE Reminder 1. Removed reference to Section 8 2. Change AC23XTRA to AC24XTRA Appendix A - Custom CIF Installation 1. AC24COPY & AC24MACS Appendix B - Prefunding Installation 1. Should be PSXS0067 Appendix D Superfile Install 1. Step 2 - Removed obsolete files (HISTINQ & ITXNI).
08/09/99
DMG
F-5

ACI Book

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ACI Book

Uploaded by

Copyright:

Available Formats

CO-ach

______________________________________________________________________________ 07/97 Applied Communications, Inc. 2

______________________________________________________________________________ 07/97 Applied Communications, Inc. 3

Applied Communications, Inc.

______________________________________________________________________________ 07/97 Applied Communications, Inc. 4

First Time CO-ach Installation

Last Modified 02/24/99

Applied Communications, Inc.

First Time CO-ach Installation

Last Modified 02/24/99

Applied Communications, Inc.

First Time CO-ach Installation

Last Modified 02/24/99

Applied Communications, Inc.

CO-ach 3. Restore Superfile

First Time CO-ach Installation

Last Modified 02/24/99

CO-ach AC24OBEY.TACLCONF. Errors:

First Time CO-ach Installation

First Time CO-ach Installation

Last Modified 02/24/99

Applied Communications, Inc.

Last Modified 02/24/99

Applied Communications, Inc.

First Time CO-ach Installation

CO-ach AC24INST.CHKP50C AC24INST.DEFTABLE AC24INST.ENTRYCTL AC24INST.RSKPEND AC24INST.SAUD0 AC24INST.SAUD1 AC24INST.SAUD2

Last Modified 02/24/99

Applied Communications, Inc.

CO-ach 13. Prepare For System Compilation.

First Time CO-ach Installation

Last Modified 02/24/99

Applied Communications, Inc.

First Time CO-ach Installation

Last Modified 02/24/99

Applied Communications, Inc.

Last Modified 02/24/99

Applied Communications, Inc.

For example, at the TACL prompt:

Last Modified 02/24/99

Applied Communications, Inc.

First Time CO-ach Installation

Last Modified 02/24/99

Applied Communications, Inc.

First Time CO-ach Installation

Last Modified 02/24/99

First Time CO-ach Installation AC24INST.PATHCONF - 697 records AC24INST.ENABCONF - 93 records

Last Modified 02/24/99

Applied Communications, Inc.

CO-ach n PENDC-ENTRY n Fkey: n Fkey:

Last Modified 02/24/99

Applied Communications, Inc.

First Time CO-ach Installation

Last Modified 02/24/99

Applied Communications, Inc.

CO-ach 23. Perform The Installation Cleanup

First Time CO-ach Installation

Last Modified 02/24/99

Applied Communications, Inc.

CO-ach 25. Installing the Optional Products.

First Time CO-ach Installation

Last Modified 02/24/99

Applied Communications, Inc.

CO-ach 28. __ Installing The SUPERFILE Option.