Professional Documents
Culture Documents
Table of Contents
1. 2. Introduction..................................................................................................................................... Initial Software distribution...............................................................................................................
2.1. 2.2. 2.3. 3. 3.1. 3.2. 3.3. 3.4. 3.5. 4. 4.1. 4.1.1.
Mainframe Installation Package.......................................................................... PC Installation Package...................................................................................... Documentation..................................................................................................... Software Updates.................................................................................................... Mainframe Full File Replacement........................................................................ PC Upgrade and Full Repository Replacement.................................................. Mainframe Delta Updates.................................................................................... PC Delta and Upgrades....................................................................................... Auto Update Run Control Option (AUTOUPDT)................................................. Client Options for EP Updates................................................................................ Mainframe............................................................................................................ Using DUF automatically maintained LOADLIB on mainframe.......................
4.1.2. Using DUF with Change Management (CM) maintained LOADLIB on mainframe...................................................................................................................... 4.2. 4.2.1. 4.2.2. 5. 6. 6.1. 6.2. 6.3. 6.4. 7. 7.1. 7.2. 8. 8.1. PC........................................................................................................................ DUF TC54 processing...................................................................................... Installing PC Updates.......................................................................................
Files Created during Mainframe Installation........................................................... Mainframe Incoming Job EP4IN Overview............................................................. Submit Dynamic JCL on Mainframe.................................................................... Building New Load Modules on Mainframe......................................................... Load Module Effective Date and Testing on Mainframe..................................... Mainframe Return Codes for Incoming Job Steps.............................................. Mainframe Incoming JOB and Procedure EP4IN................................................... EP4IN Job............................................................................................................ Mainframe EP4IN PROCEDURE DUF steps................................................... Using Change Management Tools (EP4INCM Job) on Mainframe........................ JOBLIB.................................................................................................................
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 3 ___________________________________________________________________________________________
8.2. 8.3. 8.4. 9. 9.1. 9.2. 9.3. 9.4. 9.5. 10. 10.1. 10.2. 10.3. 10.4. 11.
EPTBLUPD.......................................................................................................... EPCHGMGT Utility............................................................................................. EPTBLSPT........................................................................................................... Classifying Updates Mandatory or Optional on Mainframe................................. Release Timeline................................................................................................. Release Table...................................................................................................... Mainframe Mandatory Updates........................................................................... When updates can either be mandatory or optional on mainframe.................... Synchronizing EP4.0 Software release levels on Mainframe............................. PC Edit Package Incoming Processing.................................................................. PC Load Module Effective Date and Testing................................................... PC Return Codes for Incoming Processing..................................................... Using Change Management Utility (EPCHGMGT) on PC............................... Creating individual repository files from master repository (EPTBLSPT)........
Classifying Updates Mandatory or Optional on PC............................................. Release Timeline.............................................................................................. Release Table.................................................................................................. PC Mandatory Updates.................................................................................... When updates can either be mandatory or optional on PC............................. Synchronizing EP4.0 Software Release Levels on PC.................................... Repository tables.............................................................................................. Core components............................................................................................. Workstation components..................................................................................
Verifying PC installs................................................................................................
Appendix A: Examples of EPCHGMGT log messages - Mainframe.................................. Appendix B: Examples of EPCHGMGT log messages - PC............................................... Appendix B: Examples of EPCHGMGT log messages - PC............................................... Appendix C: Examples of Visa Broadcast message EPTBLUPD return code =04........ Appendix D: EPTBLSPT sample log messages..................................................................
1. Introduction
Edit Package (EP) Release 4.0 became generally available in August 2010. Release 4.0 maintains the basic functionality of EP Release 3.0; however unlike previous versions of EP, version 4.0 is distributed in Object Code Only (OCO). Updates for mainframe clients are distributed as Object decks, and as Microsoft install (MSI) files for PC clients. With the OCO distribution method, the EP source code is not available to the client. The Dynamic Update Facility (DUF) is a new feature that is used by the client to keep EP software up to date. The purpose of this document is to provide clients with the information necessary to utilize DUF in the most appropriate manner for their unique environment. DUF was designed to automatically provide updated EP software to clients so they would always have the most current EP version. This guide will describe the various ways that DUF may be used by the client to maintain EP software.
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 5 ___________________________________________________________________________________________
2.3. Documentation
The following Edit Package Release 4.0 user documentation is also available on VOL. Migration Implementation Guide Operations Guide PC EP Users Guide Reports Messages Run Control Options Quick Reference Guide
3. Software Updates
After the initial installation of Release 4.0, most program module and repository file updates will be provided via TC54 transactions which will be included in the incoming interchange files. Updates to program modules and Repository files for Release 4.0 will include an effective date on which the updates will automatically become active. However, there will be occasions where TC54 updates are not possible due to volume constraints. In this case, software updates will be available either as downloads from VOL, or on a CD-ROM by request through a Visa regional client support representative. The software updates from VOL must be applied using the EP4U140 utility, instead of through an incoming run. This process is described in detail later in this document.
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 7 ___________________________________________________________________________________________
The difference between two consecutive versions of the BIN and ARDEF tables are called daily delta updates and they are sent daily via TC54s to clients worldwide. When there is a change to the EP software files due to a mandatory or optional change, updates will be generated. For more information on Classifying Updates Mandatory or Optional, refer to Section 9.
Using the run control option AUTOUPDT: Requesting table updates automatically using the run control option AUTOUPDT includes the following steps:
1. The client must turn on the AUTOUPDT run control option (AUTOUPDT=YES) to alert Visa that they wish to use the automatic table update feature; Refer to Appendix A- Edit Package Release 4 Operations Guide for more information. Default value for AUTOUPDT is YES. 2. The client must run an outgoing to provide Visa with the current status of their tables. Note, that the status reported to Visa indicates the current software release levels based on what Visa has sent to the client not what the client has chosen to implement in their production environment. .
___________________________________________________________________________________________ Visa *Confidential*
3. Visa will create the table updates required to bring the clients tables up to date, based on the current version of tables at Visa and the clients table versions. 4. The client must process an incoming EP run to process table updates. The EP-299 Report generated must indicate a successful table update for the run. 5. Mainframe clients must allocate enough space for TC 54 work files to accommodate mainframe full file replacements which is approximately 750,000 TC 54 records. PC clients must have sufficient space to hold cumulative upgrades from the last mandatory full install which is approximately 300,000 TC 54 records.
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 9 ___________________________________________________________________________________________
4.1. Mainframe
During an incoming run, the Dynamic Update Facility (DUF) will automatically convert the TC54s to object modules and link-edit control cards. In addition, DUF will automatically link the object modules and create load modules in accordance with the DLLBUILD table defined in the Repository Value Table. The DLLOAD table in the Repository Value contains the effective date of each load module. The effective date dictates the date on which this particular module will begin to be used (loaded and executed). That effective date is often coordinated with repository updates which are required to be effective on the same date. Release 4.0 provides two software update options to processing centers using mainframe.
4.3. Using DUF with Change Management (CM) maintained LOADLIB on mainframe
For clients who wish to use change management software to track their changes, this option provides the client with alternate JCL for Incoming Job (EP4INCM) created by the mainframe install utility EP4U010. The JOBLIB statement which by default points to the DUF maintained LOADLIB should be changed to the LOADLIB created and maintained by the clients change management tool such as Endevor or CMAN. The DUF steps are similar to the default job EP4IN, however, there are two additional steps: 1. EPTBLUPD will create object and link-edit control libraries which can be used by the client to stage the object modules and link-edit control cards into their change management files, such as ENDEVOR and CMAN 2. EPTBLSPT includes a report detailing the current status of the load modules in the production
___________________________________________________________________________________________ Visa *Confidential*
LOADLIB compared to what is defined in the EP DLLOAD repository value table. EPTBLSPT also assures that repository value table updates are coordinated with the load modules that actually exist in the production LOADLIB. For more information about this option, refer to the following sections Section 6- Mainframe Incoming Job EP4IN Overview Section 7- Mainframe Incoming Job and Procedure EP4IN Section 8- Using Change Management Tools on mainframe
When using the CM option, it is the clients responsibility to ensure that the implementation of production updates are performed in a timely manner to satisfy EP processing requirements and to stay in synch with Visas software release levels. For more information, refer to: Section 9 Classifying Updates Mandatory or Optional
4.4. PC
The PC EP software includes the repository files, core components similar to the mainframe and workstation components that support the user interface, data entry and file transfer interfaces to Extended Access Server (EAS) and Direct Exchange (DEX).
For more information refer to Section 10 PC Edit Package Incoming Processing Software updates are normally sent via TC54s. However, there may be occasions when upgrades are provided as software downloads from VOL or optionally through CD-ROMs. Software upgrades from VOL or CD-ROM are provided as a self-extracting file (RAR) file which will create three files just like DUF TC54 process.
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 11 ___________________________________________________________________________________________
EBTBLSPT JCL procedure executed by INSTALL to load individual Repository tables from the combined Repository table
&APPL.&BUILD.JCL
PDS
EP4IN Incoming EP 4.0 example JCL using TC formats and DUF option
EP4INCM
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 13 ___________________________________________________________________________________________
Incoming EP 4.0 example JCL using TC formats and CM option
EP4INVM Incoming EP 4.0 example JCL using VML format and DUF option
EP4INVCM Incoming EP 4.0 example JCL using VML format and CM option
&APPL.&BUILD.OBJ &APPL.&BUILD.LCTL
PDS PDS
EP4IN EP 4.0 Incoming procedure used by EP4IN job above (DUF option)
EP4INCM EP 4.0 Incoming procedure used by EP4INCM job above (CM option)
EPLINK00 is a procedure in use to create the object modules in the dynamic JCL submitted by the internal reader if any load modules will be built
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 15 ___________________________________________________________________________________________
EPLINK01 is a procedure use to create LOAD modules in the dynamic JCL submitted by the internal reader if any load modules will be built
EPLINK99 is a procedure use to run Table Split program and take a backup of a newly created Master Repository
EPTBLSPT is a procedure use to run Table Split program which loads individual repository files from Master Repository during the installation
EP4.0 data repository Account Range Table EP4.0 data repository BIN table EP4.0 data repository definition table EP4.0 data repository profile table EP4.0 data repository value table file EP4.0 repository codebase table file
GDG
Combined repository table file which includes the ARDEF, BIN, CODEBASE, DEFINITIONS, PROFILE, and VALUE repository tables Customized run control options file contains the options selected during install Rules Object Library not currently used Rules Load Library not currently used Log created by EPTBLSPT that the shows the records counts of each of the repository table generated from the combined repository tables
&APPL.&BUILD.REPOSIT.OVERRIDE
Sequential
TC54EXT
Return Codes:
RC=00 - Successful Repository Table update RC=03 - Successful S /W Updates processing , and Dynamic job to update load library was submitted RC=04 - Review Visa Broadcast Message RC=06 - Table or S/W update process fail Table Update process STEP04: EPTBLUPD
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 17 ___________________________________________________________________________________________
The following describes the key job processes: 1. The input file to incoming processing may include financial and non-financial transactions. Nonfinancial transactions may include EP Updates TC54s. 2. The incoming program will select and write TC54 Extract records to a TC54EX file. 3. The table update program (EPTBLUPD) will process the TC54 Extract file and will create the following output files: o o o JCLOUT dynamic JCL DLLOUT link edit control cards and object code from &APPL.&BUILD.REPOSIT.VALUE.TABLE NEW MASTER REPOSITORY
&APPL.&BUILD.REPOSIT.PROFILE.TABLE
Sequential
&APPL.&BUILD.REPOSIT.VALUE.TABLE
Sequential
&APPL.&BUILD.REPOSIT.CODEBASE.TABLE
Sequential
VLdllbuildC****00000010 DLL Build Table VLdllbuildC****00000020 System (MVS / PCW) VLdllbuildC****00000030 | DLL Disposition VLdllbuildC****00000040 | | Task Date VLdllbuildC****00000050 | | | VLdllbuildC****00000060 | | | VLdllbuildREPCTFB01 20110129 MVS SHR 20110128 VLdllbuildREPCTFP01 20110129 MVS SHR 20110128 VLdllbuildREPFM001 20101105 MVS SHR 20101104 VLdllbuildREPHIST 20110129 MVS SHR 20110128 VLdllbuildREPRPT001 20110129 MVS SHR 20110128 VLdllbuildREPRUL001 20101105 MVS SHR 20101104 VLdllbuildREPRUL002 20101228 MVS NEW 20101227 VLdllbuildREPTBLSPT 20110129 MVS SHR 20110128 VLdllbuildREPTBLUPD 20110129 MVS SHR 20110128
For example, EPRUL002 load module will be created by the dynamic JCL with an effective date 2010/12/28, since it has a disposition of NEW.
Eff Date VLdlload VLdlload VLdlload Vldlload Vldlload Vldlload Vldlload Vldlload Vldlload VLdlload VLdlload Repbuildtc Repbuildtc Repbuildtc Reprule Reprule Reprule Reprule Reprule Reprule Reprulcob Reprulcob 20100101 20110615 20111015 20101105 20110228 20110415 20110520 20110615 20111015 20101105 20110228
Load epctfb01 epctfb02 epctfb02 eprul001 eprul002 eprul003 eprul004 eprul005 eprul006 epcob001 epcob002
PC
Load Parm dd:EPOUT dd:EPOUT dd:EPOUT TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0)
P P
MODULE(EPCOB001) MODULE(EPCOB002)
Using the above example, EPRUL002 was built on 12/28/2010. The system will start loading and executing EPRUL002 when the run date equals the effective date (run date is 2011/02/28). The future effective dating of EPRUL002 will enable clients to perform testing using the new module prior to the implementation date. In this example, clients can execute the new module built on 2010/12/28 by using the TABLEDATE option of 2011/02/28 and RUNMODE =TEST from 2010/12/28 up to a few days before the implementation date of 2011/02/28.
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 19 ___________________________________________________________________________________________
1. Step02: EPzOS: Return code= 16: Load module(s) with type M-Mandatory was not found in the production load library. The incoming ran was not successful. Refer to section 9 Classifying Updates Mandatory or Optional. 2. Step03: IDCAMS: Return code = 05. This means that the incoming processing was successful but the input file does not contain TC54s. All succeeding steps after STEP03 pertaining for TC54 processing will be bypassed. 3. Step04: EPTBLUPD: Return code = 00. The TC54 repository updates were successfully processed. Repository updates include BIN, ARDEF, value, codebase, profile and repository definitions.
4. Step04: EPTBLUPD: Return code = 03. The TC54s updates include software updates and they were successfully processed. The DLLOUT and JCLOUT files were successfully created. 5. Step04: EPTBLUPD: Return code = 04. The TC54 updates include a message or instructions from Visa. The message will be written to the EP-299 report. For example: The message may instruct the client to check the Visa Online (VOL) EP Release 4 for Upgrade instructions for a given effective date. For example refer to Appendix C. 6. Step04: EPTBLUPD: Return code = 06. The TC54s update process failed. 7. Step05: With DUF option, the dynamically created JCL from JCLOUT is submitted automatically. The job in this JCL will update the load library. For example, the job log will contain this information:
18.53.02 JOB10968 18.53.02 JOB10976 18.53.02 JOB10976 -STEP04 EP4IN EPTBLUPD ON INTRDR 03 24409 9.31 29.65 231K
EDIT PACKAGE 4
USERID @VLUN
In this example JOB10976 (Dynamic JCL-JCLOUT) created by the EP4IN incoming processing JOB10968 TENEP40 was submitted when EPTBLUPD has a return code of 3.
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 21 ___________________________________________________________________________________________
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 23 ___________________________________________________________________________________________
8.
The default EP4IN job that is created during the mainframe installation is a fully integrated process which automatically updates the EP files and program executables created during the install process. These files and executables are the same files used during the incoming, i.e.: the TC54s are extracted and are applied dynamically to the files maintained by EP (including the load library). This means that the Incoming Job is executed from the Load Library maintained by the EP automatic DUF Process.
EP4IN Job
EDIT &APPL.&BUILD.JCL(EP4IN) - 01.02 Columns 00001 00080 Command ===> Scroll ===> CSR ****** ********************************* Top of Data ********************************** 000001 //TENEP40 JOB (R811392,85075,EP40),'EDIT PACKAGE 4', 000002 // CLASS=J, 000003 // MSGCLASS=X, 000004 // REGION=0M 000005 //* 000006 /*JOBPARM LINES=9999 000007 //* 000008 //JOBLIB DD DSN=&APPL.&BUILD.RULES.LOAD,DISP=SHR 000009 // DD DSN=&APPL.&BUILD.LOAD,DISP=SHR 000010 //*
Since new load modules are created with a future effective date, the client can test using the load modules by using TABLEDATE=ccyymmdd and RUNMODE=TEST run control option where ccyymmdd is the production implementation date. With the default DUF option, the default EP4IN job is a fully integrated process that automatically manages the updates to the EP system (not only repository updates but also load module updates) received through TC54s. There is an option for clients to use their own Change Management tools such as Endevor or CMAN. In this scenario, the JOBLIB for Incoming job will be pointing to the Endevor maintained Load Library instead of the Load Library that is automatically maintained by EP. DUF continues to automatically manage repository updates but the method and timing of the updating the load modules is controlled by the user. With the CM option, the alternate job (EP4INCM) and procedure (EP4INCM) are similar to the default EP4IN job and procedure except for the differences discussed in sections: 8.1 through 8.4. Figure 1-2 shows the Incoming Process using Change Management Option.
8.1. JOBLIB
JOBLIB will point to the Change Management tool maintained Load Library which means that the Edit Package will execute load modules from the this library instead of the DUF maintained library.
EDIT
&APPL.&BUILD.JCL(EP4INCM) - 01.02
Command ===> Scroll ===> CSR ****** ********************************* Top of Data ********************************** 000001 //TENEP40 JOB (R811392,85075,EP40),'EDIT PACKAGE 4', 000002 // CLASS=J, 000003 // MSGCLASS=X, 000004 // REGION=0M 000005 //* 000006 /*JOBPARM LINES=9999 000007 //* 000009 //JOBLIB DD DSN=YOUR.ENDEVOR.LOAD,DISP=SHR 000010 //*
8.2. EPTBLUPD
During incoming processing with TC54s in the input file, ETBLUPD will create a Dynamic JCL (JCLOUT) which will perform the following procedures as the default processes: EPLINK00 creates the temporary DUF combined Link Edit Control Card and Object library from DLLOUT file EPLINK01 uses the combined Link Edit Control Card and Object library and executes the Linkage Editor to create load modules and place them into the LOADLIB created by the install process (&APPL.&BUILD.LOAD).
For CM option, EPTBLUPD will also create: OBJOUT a sequential file that will contain all the Object modules for new or updated load modules and IEBUPDTE control cards for updating the Object library. A later IEBUPDTE step will update the Object Library (OBJPDS) LCTLOUT a sequential file that will contain all the Link Edit Control Cards for new or updated load modules and IEBUPDTE control cards for updating the Link-control library. A later IEBUPDTE step will update Linker Library (LCTLOUT) The client can use the Object Library and Link Edit Control Library created by EPTBLUPD to stage the changes into their Change Management tool (like Endevor) to update their production Libraries. In addition, EPTBLUPD can be used as a utility that will allow clients to request all the object modules and linker cards for all the load modules. When EPTBLUPD is used as utility, object and linker cards are generated from the current repository files and TC54 input file is set to dummy.
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 25 ___________________________________________________________________________________________
The current process of writing to the Incoming Hold File (ENVINF) information about what repository codebase version was sent to the client will not change. 2. Report on exception conditions and assign appropriate return codes: Log the load module versions that are defined in the DLLLOAD table but which are not found in their Change Management tool created library. Issue a return of 4 to alert the clients that there are pending M-Mandatory updates that must be staged to their Change Management tool. Issue a return of 2 to alert the clients that there are pending E-Evaluate updates that have not been staged to their Change Management tool. Issue a return of 0 when there are no pending updates that have not been staged to their Change Management tool.
8.4. EPTBLSPT
The master repository files are files that contain all the individual repository files. ETBLSPT will split the new master repository into individual repository files and create a backup master repository file.
Repository Account Range Table Repository BIN table Repository definition table Repository profile table Repository value table file Repository codebase table file
&APPL.&BUILD.REPOSIT.PROFILE.TABLE &APPL.&BUILD.REPOSIT.VALUE.TABLE
Sequential Sequential
&APPL.&BUILD.REPOSIT.CODEBASE.TABLE
Sequential
environment during the outgoing and incoming run, the processing will end with a return code of 16. All value and definition table entries in the master repository file with effective dates equal to that of the release with implementation type of E (evaluate) will be written to the individual repository value and definitions table, if all load modules for the release are present in the production load libraries. Note, if the there are missing E modules for the effective date, the corresponding value and definitions table entries from the master repository are excluded from the individual value and definition tables. This will keep the individual repository tables used for the run in sync with the load modules in the current production environment as well as prevent an abnormal termination of the run because there are missing E modules in the production. For example, the DLLOAD table in the individual repository value table will not include E modules missing in the production environment.
Return codes
EPTBLSPT will issue a return code of 0 if all the load modules defined in the DLLOAD table are present in the production environment. EPTBLSPT will issue a return code of 2 if one or more load modules for a release with implementation type of E Evaluate are missing from the production environment. EPTBLSPT will issue a return code of 4 if one or more load modules for a release with implementation type of M Mandatory are missing from the production environment. For EPTBLSPT sample log messages, refer to Appendix D.
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 27 ___________________________________________________________________________________________
Figure 1-2 shows the Incoming Process using Change Management Option:
TC54EXT
Return Codes:
RC=00 - Successful Repository Table update RC=03 - Successful S/W Updates processing, Object and Link edit control cards ready for Staging to Change Management Tools RC=04 - Review Visa Broadcast Message RC=06 - Table or S update process fail /W Table Update process STEP04: EPTBLUPD
JCLOUT executes procs: EPLINK00 - Creates DUF object library EPLINK01 - Links object modules IEBUPDTE IEBUPDTE
Return Codes :
RC=00 - Successful RC=02 - There are missing E modules From load library RC=04 - There are missing M modules From load library , SPLIT MASTER REPOSITORY FILE EPTBLSPT
REPOSITORY PROFILE
Description Release 4.0 initial distribution November 2010 Maintenance Release February 2011 Maintenance Release April 2011 Business Release
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 29 ___________________________________________________________________________________________
VLrelease VLrelease VLrelease 20110520 20110615 20111015 20110507 20110531 20110827 E-Evaluate E-Evaluate M-Mandatory OCT Pilot Message Set Business Requirements June 2011 Maintenance Install October 2011 Business Release
In addition, if the April 2011 Business Release required changes to rules, the DLLOAD table will be updated to add EPRUL003 with an effective date of the release. Since the April 2011 Business Release is mandatory, EPRUL003 must be present in the production environment for the required effective date.
Imp VLdlload VLdlload VLdlload Vldlload Vldlload Vldlload Repbuildtc Repbuildtc Repbuildtc Reprule Reprule Reprule Eff Date 20100101 20110615 20111015 20101105 20110228 20110415 Load epctfb01 epctfb02 epctfb02 eprul001 eprul002 eprul003 Type CTF CTF CTF PC Load Parm dd:EPOUT dd:EPOUT dd:EPOUT TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) Type M E M M M M
In this example, the EPRUL003 load module must be present in the production library when the run date equals 2011/04/15, otherwise the EP run will fail with a return code of 16.
the EP-299 report with a brief description of the change and its effective date. Depending on the type of change, an upgrade document may also be made available on VOL. 3. Visa will include a new entry in the release table with an implementation type of E Evaluate.
Release Effective Date VLrelease VLrelease VLrelease 20110228 20110415 20110520 CPD Distribution Date 20110131 20110225 20110507 Implementation Type M-Mandatory M-Mandatory E-Evaluate
Description February 2011 Maintenance Release April 2011 Business Release OCT Pilot Message Set Business Requirements
In addition, if the May 2011 Business Release required changes to rules, the DLLOAD table in the master repository will be updated to add EPRUL004 with an effective date of 05/20/2011. Since May 2011 Business Release must be evaluated by the clients, EPRUL004 will have an effective implementation type of E Evaluate.
Imp Eff Date Vldlload Vldlload Vldlload Reprule Reprule Reprule 20110228 20110415 20110520 Load eprul002 eprul003 eprul004 Type PC Load Parm TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) Type M M E
For clients using the DUF maintained LOADLIB on mainframe: When the DUF maintained LOADLIB is used in production (EP4IN), the load module EPRUL004 will be automatically created when the TC54s are processed. The return code of 3 indicates the successful processing of updates.
For clients using the Change Management maintained LOADLIB on mainframe: The client should EVALUATE the upgrade document and determine if the update must be implemented in their production environment before the effective date of the change.
Mandatory change for the client for the given effective date When the LOADLIB used in Incoming is updated via a Change Management tool (EP4INCM) like Endevor or CMAN, then it is the clients responsibility to insure that the load module is present in their production library before the given effective date. Refer to Section 8 - Using Change Management Tools for more information.
Optional change for the client for the given effective date The clients may opt not to implement the change for the given effective date, but they should implement the new release as soon as time permits. Visa recommends that clients should implement the releases within the 45-day window or sooner since EP release levels will be synchronized for the April and October business release.
___________________________________________________________________________________________ Visa *Confidential*
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 31 ___________________________________________________________________________________________
Using the example of EPRUL004 with an effective date of 05/20/2011, if a client runs an outgoing with a system date of 05/20/2011 and their production load library does not contain EPRUL004, the system will load and execute EPRUL003 since it is the load module with an effective date equal to that of the Mandatory release. If for some reason EPRUL003 is not found in the clients production load library, the system will issue a return code of 16. In the next scenario, Visa issued EPRUL005 effective 06/15/2011 for June 15, 2011 release. The DLLOAD table in the master repository contains the following entries.
Imp Eff Date Vldlload Vldlload Vldlload Vldlload Reprule Reprule Reprule Reprule 20110228 20110415 20110520 20110615 Load eprul002 eprul003 eprul004 eprul005 Type PC Load Parm TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) Type M M E E
Client A implemented May 20, 2011 release with EPRUL004 effective 05/20/2011 but did not implement June 15, 2001 release. When Client A runs outgoing on 06/15/2011, EP will not find EPRUL005 in the production library and it will load and execute the module EPRUL004. Client B did not implement May 20, 2011 and June 15, 2011 releases. When Client B runs outgoing on 06/15/2011, EP will not find EPRUL005 and EPRUL004. EP will load and execute the mandatory module EPRUL003.
Visa has issued EPCTFB02 with an effective of June 15, 2011 to fix the Japan TCR2 ASCII/EBCDIC conversion. Since June 2011 release has an implementation type of E Evaluate , the installation and execution of EPCTFB02 is mandatory for some clients and optional for others on June 15, 2011.
___________________________________________________________________________________________ Visa *Confidential*
Imp Eff Date VLdlload VLdlloa d Repbuildtc Repbuildtc 20100101 20110615 Load epctfb01 epctfb02 Type CTF CTF PC Load Parm dd:EPOUT dd:EPOUT Type M E
When the October 2011 Business Release Enhancements are distributed sometime in the last 2 weeks of August 2011, Visa will not re-issue EPCTFB02 since it was first distributed before the 06/15/2011 and no changes were required for this module. Visa will update the DLLOAD table in the master repository to add EPCTFB02 with effective 10/15/2011 and since October 2011 is a mandatory release, EPCTFB02 must be implemented in production before 10/15/2011.
Imp Eff Date VLdlload VLdlload VLdlloa d Repbuildtc Repbuildtc Repbuildtc 20100101 20110615 20111015 Load epctfb01 epctfb02 epctfb02 Type CTF CTF CTF PC Load Parm dd:EPOUT dd:EPOUT dd:EPOUT Type M E M
Visa will not be re-distributing EPCTFB02 for the following reasons when the module becomes mandatory: 1. Some members may have opted to implement EPCTFB02 before the 06/15/2011 and re-issuing the modules might raise questions as to whether we have made additional changes. 2. Re-issuing EPCTFB02 again in August will increase the TC54 updates for October 2011 when in fact the module was not changed Visa recommends that the output of the DUF process that creates the PDS for the object and link library be put on DISK management class that allows a longer retention period for clients who are opting not to implement the optional changes to their Change Management system right away.
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 33 ___________________________________________________________________________________________
Figure 1-3 shows the key processes related to Dynamic Update Facility (DUF) during PC EP Incoming Processing
10.1.
Incoming Process
TC54EXT
Return Codes:
RC=00 - Successful Repository Table update RC=03 - Successful S /W Updates processing, PCDLLOUT.exe is ready for execution to Install software updates RC=04 - Review Visa Broadcast Message RC=06 - Table or S/W update process fail Table Update process
PCDLLOUT (EXECUTABLE)
Load epctfb01
Type CTF
PC
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 35 __________________________________________________________________________________________
VLdlload VLdlload Vldlload Vldlload Vldlload Vldlload Vldlload Vldlload VLdlload VLdlload
Repbuildtc Repbuildtc Reprule Reprule Reprule Reprule Reprule Reprule Reprulcob Reprulcob
20110615 20111015 20101105 20110228 20110415 20110520 20110615 20111015 20101105 20110228
epctfb02 epctfb02 eprul001 eprul002 eprul003 eprul004 eprul005 eprul006 epcob001 epcob002
CTF CTF
dd:EPOUT dd:EPOUT TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) P P MODULE(EPCOB001) MODULE(EPCOB002)
Using the above example, EPRUL002 was built on 12/28/2010. The system will start loading and executing EPRUL002 when the run date equals the effective date (run date is 2011/02/28). The future effective dating of EPRUL002 will enable clients to perform testing using the new module prior to the implementation date. In this example, clients can execute the new module built on 2010/12/28 by using the TABLEDATE option of 2011/02/28 and RUNMODE =TEST from 2010/12/28 up to a few days before the implementation date of 2011/02/28.
Repository Account Range Table Repository BIN table Repository definition table Repository profile table Repository value table file Repository codebase table file
profile.rco.txt repository.VALUE.txt
Sequential Sequential
repository.codebase.txt
Sequential
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 37 __________________________________________________________________________________________
transactions. For the PC implementation, certain value and definition table entries in the master repository table may or may not be written to the individual repository value and definition tables. All value and definition table entries in the master repository file with effective dates equal to that of the release with implementation type of M (mandatory) will be written to the individual repository value and definitions table. Note that if there are missing M (mandatory) load modules from production environment during outgoing and incoming run, the processing will end with return code of 16. All value and definition table entries in the master repository file with effective dates equal to that of the release with implementation type of E (evaluate) will be written to the individual repository value and definitions table, if all load modules for the release are present in the production load libraries. Note if there are missing E modules for the effective date, the corresponding value and definitions table entries from the master repository are excluded from the individual value and definition tables. This will keep the individual repository tables used for the run in sync with the load modules in the current production environment as well as prevent an abnormal termination of the run because the there are missing E modules in the production. For example, the DLLOAD table in the individual repository value table will not include E modules missing in the production environment.
Return codes
EPTBLSPT will issue a return code of 0 if all the load modules defined in the DLLOAD table are present in the production environment. EPTBLSPT will issue a return code of 2 if one or more load modules for a release with implementation type of E Evaluate are missing from the production environment. EPTBLSPT will issue a return code of 4 if one or more load modules for a release with implementation type of M Mandatory are missing from the production environment. For EPTBLSPT sample log messages, refer to Appendix D.
11.1.Release Timeline
The Technical Letter for the semi-annual Business Release includes a Release Timeline table. The table is a high-level calendar of events for the implementation of changes to the BASE I, V.I.P., and BASE II Systems. EP software availability dates are included in this table. Acquirers and issuers should include these dates in project planning for the release and schedule implementation activities accordingly.
11.2.Release Table
The Release table in the repository.value.txt contains the information about each software release such as the release description and effective date, CPD distribution date and implementation type. The implementation type determines if a release must be implemented before the release effective date (Mandatory) or evaluated to determine if implementation can be done after the effective date (Evaluate). For example a release table may contain the following information:
Release Effective Date VLrelease VLrelease VLrelease VLrelease 20100101 20101105 20110228 20110415 CPD Distribution Date 20100101 20101031 20110131 20110225
Description Release 4.0 initial distribution November 2010 Maintenance Release February 2011 Maintenance Release April 2011 Business Release
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 39 __________________________________________________________________________________________
OCT Pilot Message Set Business Requirements June 2011 Maintenance Install October 2011 Business Release
In addition, if the April 2011 Business release required changes to rules, the DLLOAD table will be updated to add EPRUL003 with an effective date of the release. Since the April 2011 Business Release is mandatory, EPRUL003 must be present in the production environment for the required effective date.
Imp Eff Date VLdlload VLdlload VLdlload Vldlload Vldlload Vldlload Repbuildtc Repbuildtc Repbuildtc Reprule Reprule Reprule 20100101 20110615 20111015 20101105 20110228 20110415 Load epctfb01 epctfb02 epctfb02 eprul001 eprul002 eprul003 Type CTF CTF CTF PC Load Parm dd:EPOUT dd:EPOUT dd:EPOUT TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) Type M E M M M M
In this example, the EPRUL003 load module must be present in the production library when the run date equals 2011/04/15, otherwise the EP run will fail with a return code of 16.
2. Issue a return code of 3 for EPTBLUPD (STEP04 in the EP4IN proc) and display a text message on the EP-299 report with a brief description of the change and its effective date. Depending on the type of change, an upgrade document may also be made available on VOL. 3. Visa will include a new entry in the release table with an implementation type of E Evaluate.
Release Effective Date VLrelease VLrelease VLrelease 20110228 20110415 20110520 CPD Distribution Date 20110131 20110225 20110507 Implementation Type M-Mandatory M-Mandatory E-Evaluate
Description February 2011 Maintenance Release April 2011 Business Release OCT Pilot Message Set Business Requirements
In addition, if the May 2011 Business Release required changes to rules, the DLLOAD table in the master repository will be updated to add EPRUL004 with an effective date of 05/15/2011. Since May 2011 Business Release must be evaluated by the clients, EPRUL004 will have an effective implementation type of E Evaluate.
Imp Eff Date Vldlload Vldlload Vldlload Reprule Reprule Reprule 20110228 20110415 20110520 Load eprul002 eprul003 eprul004 Type PC Load Parm TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) Type M M E
The client should EVALUATE the upgrade document and determine if the update must be implemented in their production environment before the effective date of the change.
Mandatory change for the client for the given effective date While the incoming processing of TC54s created all necessary files for installing the upgrade, it is the clients responsibility to insure that software upgrade is installed in their production environment.
Optional change for the client for the given effective date The clients may opt not to implement the change for the given effective date, but they should implement the software upgrade as soon as time permits. Visa recommends that clients should implement the upgrades within the 45-day window or sooner since EP release levels will be synchronized for the April and October Business Release. Exception Processing and use Fallback Load Modules
Imp Eff Date Vldlload Vldlload Vldlload Reprule Reprule Reprule 20110228 20110415 20110520 Load eprul002 eprul003 eprul004 Type PC Load Parm TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) Type M M E
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 41 __________________________________________________________________________________________
Using the example of EPRUL004 with an effective date of 05/20/2011, if a client runs an outgoing with a system date of 05/20/2011 and their production environment does not contain EPRUL004; the system will load and execute EPRUL003 since it is the load module with an effective date equal to that of the Mandatory release. If for some reason EPRUL003 is not found in the clients production environment, the system will issue a return code of 16. In the next scenario, Visa issued EPRUL005 effective 06/15/2011 for June 15, 2011 release. The DLLOAD table in the master repository contains the following entries.
Imp Eff Date Vldlload Vldlload Vldlload Vldlload Reprule Reprule Reprule Reprule 20110228 20110415 20110520 20110615 Load eprul002 eprul003 eprul004 eprul005 Type PC Load Parm TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) Type M M E E
Client A implemented May 20, 2011 release with EPRUL004 effective 05/20/2011 but did not implement June 15, 2001 release. When Client A runs outgoing on 06/15/2011, EP will not find EPRUL005 in the production environment and it will load and execute the module EPRUL004. Client B did not implement May 20, 2011 and June 15, 2011 releases. When Client B runs outgoing on 06/15/2011, EP will not find EPRUL005 and EPRUL004. EP will load and execute the mandatory module EPRUL003 Client C did not install the upgrade for EPRUL004 (May 20, 2011 release), but installed the upgrade that contained EPRUL005 on 2011/05/21 (June 15, 2011 release). When the outgoing runs on 2011/05/21, system will find EPRUL004 and will execute this module since it is effective 2011/05/20. When Client C runs outgoing on 06/15/2011, EP will load and execute EPRUL005. In this example note, that PC EP upgrade for June 15, 2011 release is a cumulative upgrade from the last mandatory release, hence, it also contained EPRUL004.
Visa has issued EPCTFB02 with an effective of June 15, 2011 to fix the Japan TCR2 ASCII/EBCDIC conversion. Since June 15, 2011 release has an implementation type of E Evaluate, the installation
and execution of EPCTFB02 is mandatory for some clients and optional for others before June 15, 2011.
Imp Eff Date VLdlload VLdlloa d Repbuildtc Repbuildtc 20100101 20110615 Load epctfb01 epctfb02 Type CTF CTF PC Load Parm dd:EPOUT dd:EPOUT Type M E
If there are no updates required to EPCTFB02 for the October 2011, Visa will update the DLLOAD table in the master repository to add EPCTFB02 (same version as that of the June 15, 2011 release) with an effective 10/15/2011. Since October 2011 is a mandatory release, EPCTFB02 becomes mandatory for the October 2011 release. When the October 2011 Business Release Enhancements are distributed sometime in the last 2 weeks of August 2011, the PC upgrade for October 2011 will include EPCTFB02. When the client installs the October 2011 release, their environment will have all the required modules for the release.
Imp Eff Date VLdlload VLdlload VLdlloa d Repbuildtc Repbuildtc Repbuildtc 20100101 20110615 20111015 Load epctfb01 epctfb02 epctfb02 Type CTF CTF CTF PC Load Parm dd:EPOUT dd:EPOUT dd:EPOUT Type M E M
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 43 __________________________________________________________________________________________
12.Verifying PC installs
As noted previously the PC upgrade installation package may consist of updates to the following components: Repository Tables Core components Workstation components
12.1.Repository tables
The upgrade package will include instructions on how to verify that the clients production environment contains the required repository table versions. For example, the client can verify successful installation of the upgrades by using the test files provided and running an Outgoing run. The Processing Log report (EP-199) includes information about the various repository versions and effective dates. This can be compared with the expected repository table versions as noted in the upgrade document.
12.2.Core components
The upgrade package will include instructions on how to verify that the clients production environment contains the necessary core components. For example, the client can verify successful installation of the upgrades by using the test files provided and running an Incoming run. The Processing Log report (EP-299) will include log messages from the Change Management Utility (Appendix B: Examples of EPCHGMGT log messages PC) regarding the status of the core modules.
12.3.Workstation components
The upgrade package will include instructions on how to verify that the clients production environment contains the necessary workstation components. The PC EP About.log contains information about the installed core and workstation components. The client must compare the About.log-Current Edit Package Information from their installed version with the expected core and workstation component versions upon successful upgrade installation.
EPWIN400 Version - 4.00.0004 - Date - 2/25/2011 11:38:50 AM EPMF Version - 4.00.0003.02 - Date - 2/9/2011 3:22:08 PM
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 45 __________________________________________________________________________________________
System date 03/25/2011; All modules required modules were found in the production load library return code = 0. DLLOAD table includes an entry for EPRUL003.
Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Input Repository sorted in 0 passes. 10 = 'dlload R' MVS records found in Value Table. BLDL RC(0) Reason(0) Module -------EPCTFP01 EPVMLP01 EPCTFB01 Effective Date -------20100101 20100101 20100101 Status ------FOUND FOUND FOUND
System date 04/16/2011; Visa has issued an updated DLLOAD table with EPRUL004 which was not found in the production load library return code =2
Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Input Repository sorted in 0 passes. 12 = 'dlload R' MVS records found in Value Table. BLDL RC(2) Reason(0) Module -------EPCTFP01 EPVMLP01 EPCTFB01 EPVMLB01 EPFM001 EPRPT001 EPRUL001 EPRUL002 EPRUL003 EPRUL004 Effective Date -------20100101 20100101 20100101 20100101 20100101 20100101 20101105 20110228 20110415 20110520 Status ------FOUND FOUND FOUND FOUND FOUND FOUND FOUND FOUND FOUND MISSING
-------Required Required Required Required Required Required Required Required Required EVALUATE
System date 05/16/2011; Visa has issued an updated DLLOAD table with EPRUL005 which was not found in the production load library return code = 2
Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Input Repository sorted in 0 passes. 12 = 'dlload R' MVS records found in Value Table. BLDL RC(2) Reason(0) Module -------EPCTFP01 EPVMLP01 EPCTFB01 EPVMLB01 EPFM001 EPRPT001 EPRUL001 Effective Date -------20100101 20100101 20100101 20100101 20100101 20100101 20101105 Status ------FOUND FOUND FOUND FOUND FOUND FOUND FOUND
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 47 __________________________________________________________________________________________
System date 08/28/2011; Visa has issued an updated DLLOAD table with EPRUL006 which was not found in the production load library return code = 4
Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Input Repository sorted in 0 passes. 13 = 'dlload R' MVS records found in Value Table. BLDL RC(4) Reason(0) Module -------EPCTFP01 EPVMLP01 EPCTFB01 EPVMLB01 EPFM001 EPRPT001 EPRUL001 EPRUL002 EPRUL003 EPRUL004 EPRUL005 EPRUL006 Effective Date -------20100101 20100101 20100101 20100101 20100101 20100101 20101105 20110228 20110415 20110520 20110615 20111015 Status ------FOUND FOUND FOUND FOUND FOUND FOUND FOUND FOUND FOUND MISSING MISSING MISSING
-------Required Required Required Required Required Required Required Required Required EVALUATE EVALUATE Required
An example of EPCHGMGT output with return code=04, showing the release tables:
2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 Epchgmgt-0135I Running As Job......... Starting on............ Program Compiled....... Platform Version.Build. Operating System....... Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I EPCHGMGT (Job ID: JOB09029) 2011/05/12 at 16:20 May 12 2011 at 16:18:48 Version 4.0 Program CEpchgmg V4.00.B0015 IBM z/OS 01.11.00
Input Repository table records loaded = 31 Input Repository table sorted in 0 passes. Input Dlload table sorted in 0 passes. 8 = 'RELEASE R' records found in Value Table. The following RELEASE VLRELEASE VLRELEASE VLRELEASE VLRELEASE VLRELEASE VLRELEASE VLRELEASE VLRELEASE R20100101 R20101105 R20110228 R20110415 R20110429 R20110515 R20110527 R20110615 records will be processed: 20091201 20101005 20110201 20110315 20110401 20110501 20110516 20110601 M M M M E E E E Base Release Another 2010 Release First 2011 Release April 2011 BE Another April 2011 Release RNT XXXX- OCT Pilot May Maintenance Durbin
23 = 'dlload
BLDL RC(4) Reason(0) Module -------EPCTFP01 EPVMLP01 EPWTFP01 EPCTFB01 EPVMLB01 EPWTFB01 EPFM001 EPNET001 EPOSIXMS EPRPT001 EPCOB001 EPCOB002 EPCOB003 EPCOB004 EPCOB005 EPCOB005 EPCOB006 EPRUL001 Effective Date -------20100101 20100101 20100101 20100101 20100101 20100101 20100101 20100101 20100101 20100101 20101105 20110228 20110415 20110429 20110527 20110527 20110615 20101105 Status ------FOUND FOUND MISSING FOUND FOUND MISSING FOUND MISSING MISSING FOUND MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING
-------REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED EVALUATE EVALUATE EVALUATE EVALUATE REQUIRED
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 49 __________________________________________________________________________________________
2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12 2011-05-12
16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42 16:20:42
Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I
The following Releases were processed: NumberOfModules Effective DateDist- E Found Missing Date -ributed M ------ ------- -------- -------- 6 0 0 1 1 0 0 0 0 5 2 2 1 1 0 2 2 2 20100101 20101105 20110228 20110415 20110429 20110515 20110527 20110527 20110615 20091201 20101005 20110201 20110315 20110401 20110501 20110516 20110516 20110601 M M M M E E E E E Description ---------------------------------------Base Release Another 2010 Release First 2011 Release April 2011 BE Another April 2011 Release RNT XXXX- OCT Pilot May Maintenance May Maintenance Durbin
Records with any of the following Effective Dates will be excluded from the Value and Definition Tables. Effective --Date--------20110429 20110527 20110615
Epchgmgt-0820I Edit Package 4.0 Compress / Table Update Category Count --------------------------------------Execution Resources Elapsed time.............. 0 Program CPU Seconds....... 0.02 System CPU Seconds........ 0.00 Memory in use............. 2,183,168 Return Code............... 6 File Usage Repository Input File..... 0
Epchgmgt-0820I
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 51 __________________________________________________________________________________________
System date 2011/04/07; Return code =2. Example DLLOAD table includes an entries for modules that have not been distributed. The following sample log messages were generated
2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 19:59:04 19:59:04 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I BLDL RC(2) Reason(0) Module -------EPCTFP01 EPVMLP01 EPWTFP01 EPCTFB01 EPVMLB01 EPWTFB01 Effective Date -------20100101 20100101 20100101 20100101 20100101 20100101 Status ------FOUND FOUND FOUND FOUND FOUND FOUND
2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07 2011-04-07
20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27 20:08:27
Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I Epchgmgt-0135I
EPFM001 EPNET001 EPOSIXMS EPRPT001 EPCOB001 EPCOB002 EPCOB003 EPRUL001 EPRUL002 EPRUL003 EPRUL004 EPRUL005 EPRUL006 EP4UT001
20100101 20100101 20100101 20100101 20101105 20110228 20110415 20101105 20110228 20110415 20110520 20110615 20111015 20100101
FOUND FOUND MISSING FOUND FOUND FOUND FOUND FOUND FOUND FOUND MISSING MISSING MISSING FOUND
REQUIRED REQUIRED
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 53 __________________________________________________________________________________________
Default allocation for memory table was not large enough to hold contents of DD(REPOSIT) DSN(C:\EPNGTESTFILES\TEN.PROD.EPNG.REPOSIT.TABLE.G0022V00.@WOVE) Initial estimate of 100 records and 6,400 bytes automatically replaced by actual of 737,279 records and 88,952,495 bytes. Input Repository table records loaded = 737,279 Input Repository table sorted in 4 passes. Input Dlload table sorted in 0 passes. 8 = 'RELEASE R' records found in Value Table. The following RELEASE 25RELEASE 25RELEASE 25RELEASE 25RELEASE 25RELEASE 25RELEASE 25RELEASE 25RELEASE R20100101 R20101105 R20110228 R20110415 R20110429 R20110515 R20110527 R20110615 records will be processed: 20091201 20101005 20110201 20110315 20110401 20110501 20110516 20110601 M M M M E E E E Base Release Another 2010 Release First 2011 Release April 2011 BE Another April 2011 Release RNT XXXX- OCT Pilot May Maintenance Durbin
23 = 'dlload
R' records found in Value Table. records will be processed: 20100101 20100101 20100101 20100101 20100101 20100101 20100101 20100101 20100101 20100101 20101105 20110228 20110415 20110515 epctfp01 epvmlp01 epwtfp01 epctfb01 epvmlb01 epwtfb01 epfm001 epnet001 eposixmsg eprpt001 epcob001 epcob002 epcob003 epcob004 CTF VTF WTF CTF VTF WTF dd:EPIN dd:VML dd:WTF dd:EPOUT dd:EPOUT 3 MODULE(EPCOB001) MODULE(EPCOB002) MODULE(EPCOB003) MODULE(EPCOB004)
The following dlload 25dlload 25dlload 25dlload 25dlload 25dlload 25dlload 25dlload 25dlload 25dlload 25dlload 25dlload 25dlload 25dlload 25dlload Reparsetc Reparsevml Reparsewtf Repbuildtc Repbuildvml Repbuildwtf Repfilemgr Repnetwork Reposixmsg Repreport Reprulcob Reprulcob Reprulcob Reprulcob
2/2/2012 Edit Package Release 4.0 Software Distribution and Updates 55 __________________________________________________________________________________________
2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13
00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00
EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I
25dlload Reprulcob 25dlload Reprulcob 25dlload Reprule 25dlload Reprule 25dlload Reprule 25dlload Reprule 25dlload Reprule 25dlload Reprule 25dlload Reputil BLDL RC(4) Reason(0) Module -------EPCTFP01 EPVMLP01 EPWTFP01 EPCTFB01 EPVMLB01 EPWTFB01 EPFM001 EPNET001 EPOSIXMS EPRPT001 EPCOB001 EPCOB002 EPCOB003 EPCOB004 EPCOB005 EPCOB006 EPRUL001 EPRUL002 EPRUL003 EPRUL004 EPRUL005 EPRUL006 EP4UT001 Effective Date -------20100101 20100101 20100101 20100101 20100101 20100101 20100101 20100101 20100101 20100101 20101105 20110228 20110415 20110515 20110527 20110615 20101105 20110228 20110415 20110515 20110527 20110615 20100101
MODULE(EPCOB005) MODULE(EPCOB006) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP) FIELDS(0) TRACE(DUMP)
Status ------MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING MISSING
-------REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED REQUIRED EVALUATE EVALUATE EVALUATE REQUIRED REQUIRED REQUIRED EVALUATE EVALUATE EVALUATE REQUIRED
The following Releases were processed: NumberOfModules Effective DateDist- E Found Missing Date -ributed M ------ ------- -------- -------- 0 0 0 0 0 0 11 2 2 2 0 2 20100101 20101105 20110228 20110415 20110429 20110515 20091201 20101005 20110201 20110315 20110401 20110501 M M M M E E Description ---------------------------------------Base Release Another 2010 Release First 2011 Release April 2011 BE Another April 2011 Release RNT XXXX- OCT Pilot
2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13 2011-05-13
00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:00 00:34:01 00:34:01 00:34:01 00:34:01 00:34:01 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22 00:34:22
EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I EPTBLSPT-0135I
0 0
2 2
20110527 20110615
20110516 20110601
E E
Records with any of the following Effective Dates will be excluded from the Value and Definition Tables. Effective --Date--------20110515 20110527 20110615 DD: REPOSIT , DSN: C:\EPNGTESTFILES\TEN.PROD.EPNG.REPOSIT.TABLE.G0022V00.@WOVE, Sorted in 0 passes. 0 Override records read. 0 Records deleted by Override. 0 Records modified by Override. 0 Records inserted by Override. Count --------26 5.75 2.34 111,136,768
EPTBLSPT-0820I Edit Package 4.0 Table Split Utility Category ------------------------------------Execution Resources Elapsed time..................... Program CPU Seconds.............. System CPU Seconds............... Memory in use....................
Rec Count *Byte Count Files ------------ -----------Repository....(in).. 737,279 88,952,495 ARDEF Table...(out). 79,261 7,926,100 BIN Table.....(out). 71,440 7,144,000 CODEBASE Table(out). 16 1,002 CODEOBJ.......(out). 547,874 76,511,102 DEF Table.....(out). 477 28,944 PROFILE Table.(out). 122 7,104 VAULE Table...(out). 36,859 2,438,052 'Evaluate' Releases with DEF Table VALUE Table uninstalled modules Recs Deleted Recs Deleted ------------------------ ------------ -----------20110515 0 50 20110527 0 66 20110615 4 123 * Byte Count: note that this excludes any record overhead bytes: such as CR/LF in Windows, Record/Block descriptor words in z/OS.