Installation of PTF02002
Automatic copy of objects in the ACP(Acceptance)
library to the user acceptance test libraries (UAT).
After restoring the
downloaded ptf software into the FENIX library, use the DSPPGM (Display
Program) or DSPOBJAUT (Display Object Authority) command to identify the owner
of the following programs in the system library (FENIXQQQ), where QQQ
is the FENIX environment acronym. Delete the programs.:
Rename the
following files in the same libarary (FENIXQQQ):
1.
SCL076 a SCL076XX;
Re-activate the
system (option 1, F17 y F18).
The new versions of
the programs and files will appear in library FENIXQQQ.
Change the
ownership of the programs to what they previously were. Copy the renamed files
(XX) over the new files also in FENIXQQQ using the FORMAT(*MAP *DROP) copy
options.
Messages files:
This PTF contains a
message file which will have to be merged into the FENIX message file, SCLMSGF,
in the FENIX library.
This is done by
using the AS/400 Merge Message File command, MRGMSGF, as follows:
Command
Entry JAXWARD Type command, press Enter. ===> MRGMSGF FROMMSGF(FENIX/PTF02002EN)
TOMSGF(FENIX/SCLMSGF)_____________ ___________________________________________________________________________ |
Updating FENIX message file SCLMSGF
This PTF includes
an enhancement to option 2 (Application Definition Maintenance) which
provides for the maintenance of the UAT environment definition.
Once an application
has been selected for maintenance via option 2, enter F14 to display the
following screen:
SCL140 **** Test ABC System Environment **** 12/03/02 FENIX User Acceptance Test Environment
17:53:05 JAXWARD
*Enquiry Apl:
HUMANR Desc: Human Resources
Application for ABC
UAT
number: 1 Descr: UAT Now allows for LCase too
UAT Bib. Base de datos : UATHUM1 UAT Object Library
: UATHUM1 Data *USE Authority : QUSER Object *USE
Authority : QPGMR
Data Owner : JSMITH Object Owner : LISA
Data Authorisation List: HUDTAAUTL Object Authorisation List: HUOBJAUTL
Data Auth. Ref. Object : Object Auth. Ref. Object : Data Auth. Ref. Obj.Type: Object Auth. Ref. Obj.Type: Data Auth. Ref. Library : Object Auth. Ref. Library :
Copy data sources to UAT : Y
Lib: UATDTASR1
Replace UAT data objects : Y
Replace UAT objects :
Y Delete UAT backout data objects : Y Delete UAT backout
objects : Y Delete UAT Accepted data objs(A-P): N
Delete UAT Accepted objects :
N ______________________________________________________________________________
F3=Exit F9=Add
F5=Change
F11=Delete
F12=Cancel |
Definition of UAT environments
The new fields
permit the following:
Copy of data
sources to a UAT given library
By default = N(No).
If = Y(Yes), a source of data objects entering UAT will also be copied to the
given library (Lib:).
Replace data /
non-data objects in UAT
Bu defaout = N(No).
If = Y(Yes), the objects will be placed in the corresponding UAT library
replacing existing objects and without notifying the user.
If set to N(N=No)
and a version exists in the UAT library, then it is not replaced. The promotion
is terminated with a message being sent to the user. The object is not promoted
to T(Test).
Delete data /
non-data objects at Backout
By default = N(No).
If = Y(Yes), the object will be deleted from the corresponding UAT library when
objects are returned from test(T) to 'U' for backout (usually when the object
has failed acceptance testing).
If = N(N=No), the
object remains in the UAT library.
Delete data /
non-data objects accepted in UAT(A-P)
By default, =
N(No). If = Y(Yes), the object will be deleted from the corresponding UAT
library when an accepted objeto is promoted to production (promotion from
stsatus A a P).
If = N(N=No), the
object is left in the UAT.
This feature is
optional once installed and needs to be activated if used by turning on special
indicator number 028 - Automatic copy of objects to UAT during promotion to
status T(Test). Set the indicator to Y(=Yes) to activate.
The special
indicators are set via opción 99 (Modify System Setup Special Indicators).
NOTE: Before a physical file
is replaced in any UAT environment, all the associated logical files will be
automatically deleted. This means that any logicals associated with the
physical file being promoted will also have to be promoted (to T) after the
physical or manually re-created. FENIX ensures that any logicals also being
promoted in the same request are promoted in the correct sequence.