Region Setup

8/22/2019 Region Setup

1/18

REGION SETUP / REGION RE-FRESH

Region Setup is setting a complete new region which are called as TEST REGIONS and

are similar to Production. They are other ways like replicate to that of production.

Poland is one of the sites which does a lot of testing to implement new things.

Classification: GE Internal


2/18

Poland has different Regions like:

Regions Naming Convention

Development D

Vinci VTesting T

MBS Testing M

Acceptance A

BugFix B

Production P

Different Types Of Testing:

There are different types of testing like System testing and integration testing and user

acceptance testing.

The flow we follow is

A- For Acceptance Testing

B-BugFix Region

And other testings will be done in the regionsM-For MBS

V-Vinci used for YogurtFee

T-TestingD-Development

P-Production

Currently we are using

T-As BugFix

B-As Acceptance Testing

To test the new implementations or the fixes or enhancements we have to set up a newregion i.e from the scratch then the region will be ready for testing.



3/18

Steps To Setup Region For testing

1) Initializing the modulesCMS

LTS

ASMMBS

Done By: CSC

Note:

TRM, ITS, SSC should not be initialized.No Load libraries or parmlibs to be altered.

Changes in OPC also not required at this stage

Never initialize LMRT, AMSR

2) After that we need to put header as 0s and the trailer as 9s in all the files.

The files which need to be initialized areCMS

3) All the PCTs, FCTs,PPTs should be defined.

4) All the connect Direct Jobs JCL has to be changed- DMBATP1 has to changed to DMBATD1

- PROC=GCFIPL3P has to be changed to PROC=GCFIPL3Z

- PROC=GCFIPL2P has to be changed to PROC=GCFIPL2Z

5) copy MMOLZ file from production

6) The falcon data set name in CICS has to be in sync with the Region.

7) Now setting up the system level parameters. This will be done through screens

Set the CMS module thru the screen ARQSFAS-OFSP

MBS-MBMY

LTS-LTMS

All the fields must have the same values as in Production whereas Last and Next



4/18

Processing date will be provided by the business.

We will just take a look about how we can set them in CMS, MBS, LTS and also FAS.

Note:

For Dry batches, the PROBE parameter should be switched off, i.e. the parameter will

be set to N, once the dry batches are over, it will set back to P.

We can change this option thru screen ARAS 02. The field is ACS ACTIVE will be P

when it on and when off it will be N.



5/18

CMS

We will set the system level parameters in the screen ARAS which is to add the parameters

of system level record and will apply to all the organizations which is 101 (Only 1 For

Poland ).

We will Add SYSTEM LEVEL record thru ARAS 01. ARQS is for viewing.

Note:

1.And usually we can add the system level records only during the region setup

and after we cant add a record and there will only 2 options available which are to modify



6/18

and to view.

2. When we cant edit the date through screens then from the backend we will edit the file

AMCR.

Steps need to be changed in ARAS

The date format should be changed to 1.

Date will sent by the business and that needs to be edited in fields DATE LASTPROCESSED and NEXT PROCESSING DATE.

These will be the changes which will be done with respective the regions we are setting

up and rest are in sync with Production

Probe will changed to N from P for all the dry runs only.

FAS:

Fas control parameters will be done through the screen OFSP .

Here the CONSOLE TERMINAL ADDRESS is 187 for T region but in the

production that is not defined.

And the rest fields are same as production.



7/18

MBS:

MBS parmaetization is done thru MBMY and MBQY is for viewing.

The dates should be changed for the fileds. DATE LAST PROCESSED and DATE

NEXT PROCESSED.

All the dates should be same as CMS.



8/18

LTS:

LTS can be maintained through the screen LTMS where it to modify and LTQS is for

viewing.

Go to page02 where we can edit the dates in LTMS 02.

Fields are LAST PROCESSING, NEXT PROCESSING and also DATE FORMAT

should be changed to 1. DATE FORMAT is changed to 1 from Backend LMSC fileis edited as it can be seen.

All the modules should be edited as of CMS and that will provided by the business.



9/18

With all the above settings in the screens, now the region is setup with system levelrecords.

8) Now all the screens are setup and now its time to initialize files for specific

modules.

All the below files should be having correct header and trailer with the date sent bybusiness.

CMS:

*PLVPGE.CMS.PODX.KE

*PLVPGE.CMS.PORA.KE*PLVPGE.CMS.PORO.KE*PLVPGE.CMS.POTC.KE

*PLVPGE.POL.PODX.POLREF.KE

Note: * can be any region A,B,T,M,V

TRM:

*PLVPGE.TRM.NUVATMC.KE



10/18

*PLVPGE.TRM.NUVBNCP.KE

*PLVPGE.TRM.NUVBWIN.KE

*PLVPGE.TRM.NUVBWSB.KE*PLVPGE.TRM.NUVCOMM.KE

*PLVPGE.TRM.NUVDCPX.KE

*PLVPGE.TRM.NUVEXTC.KE*PLVPGE.TRM.NUVINPD.KE

*PLVPGE.TRM.NUVINSC.KE

*PLVPGE.TRM.NUVITBK.KE*PLVPGE.TRM.NUVPDBK.KE

*PLVPGE.TRM.NUVPDSB.KE

*PLVPGE.TRM.NUVPODC.KE

*PLVPGE.TRM.NUVSBDY.KE*PLVPGE.TRM.NUVSVBW.KE

*PLVPGE.TRM.NUVTCKT.KE


MBS:

*PLVPGE.MBS.MMAHZ.KE*PLVPGE.MBS.MMHTZ.KE

*PLVPGE.MBS.MMH1Z.KE

*PLVPGE.MBS.MMH2Z.KE*PLVPGE.MBS.MMH3Z.KE

*PLVPGE.MBS.MMICZ.KE

*PLVPGE.MBS.MMOLZ.KE

*PLVPGE.MBS.MMPHZ.KE*PLVPGE.MBS.MMS1Z.KE

*PLVPGE.MBS.MMTDZ.KE

*PLVPGE.MBS.MMTHZ.KE*PLVPGE.MBS. .KE


Now the with all the above settings 1st DRY BATCH IS READY.

Some tips for 1St batch :

There will date and time stamp problem in the jobs before date roll will starts and allthe interface jobs.

Eg: Jobs like05J, ZPD1, 22A

Solution : These jobs will be foce completed.



11/18

We will have problems like READ ERROR IN AMBS or AMRT

Solution: Force completed by emptying the files which are having data.

Reason: All the input files should be empty, and no data should be present in the files

except trailer or header as per required.

There will a job LD10 saying AMMX File problem.

Solution: Skip the step which was abending and rerun the job.

Remember all the input files should have proper date and 1 file BASEII.ICTF should

be empty.

The 1st Dry Batch will be completed successfully .

Note: With the execution of the 1st batch all the dates will be set at the system level for allthe master files.

READY FOR 2nd BATCH

Steps for setting the region which be ready for 2nd Dry Run.

1) Set the parameters at Org and logo level in all the modules.

2) We do the same for the rest modules like the CMS.



12/18

CMS:

We will set the 2nd level by setting the org and logo.

Org level record is added in the screen ARAO , ARAL.

Org:

We will edit the fields like CURRENCY CODE to 985CURRENCY CODE is the field which will identify the currency of the country and

this is previously defined in the SSC of the screen SCQU.

Fileds like NOD, PER ITEM NOD, PERCENT NOD will be automatically displayedand when we enter it goes to a screen for the confirmation. If sure then press ENTER.

All the rest fields will be same as production.

Logo: Logo can be changed through backend by copying the files from production for

temporary due to less time.

Through backend we will copy all the parameters from production files to region files

The files are:*PLVPGE.CMS.AMAM.KE Activity recap

*PLVPGE.CMS.AMCP.KE Credit Plan Master

*PLVPGE.CMS.AMCR.KE System Control for logo

*PLVPGE.CMS.AMFS.KE Field Security*PLVPGE.CMS.AMGL.KE General Ledger

*PLVPGE.CMS.AMMC.KE Monetary Transaction codes

*PLVPGE.CMS.AMRT.KE Rate Tables*PLVPGE.CMS.AMSD.KE Store Demographics

Note:1) * can be any region A,B,T,M,V

2)Copy only the Org related information into the files.



13/18

Now the CMS module is ready with org/logo parameters.

END of CMS Change.

LTS :



14/18

Change the LTS through the screen LTAO as of production

Org:

Org is added as of CMS is done and with sync with production.

All the rest parameters are copied by copying the files from Prod.

The files are:*PLVPGE.LTS.LMLM.KE Letter Master

*PLVPGE.LTS.LMLV.KE Letter Variables

*PLVPGE.LTS.LMRD.KE Resquestor directory*PLVPGE.LTS.LMSC.KE Letter system record for logo

END of LTS Change.

MBS:



15/18

Need to change according to the production .

Note: PER ITEM NOD field may be 3 then we need to change it to 2 and this

should be done in MBAO Page05.

Org:Done as in production.

All the rest parameters are copied from Prod into the below files.

*PLVPGE.MBS.MMFS.KE Field security

*PLVPGE.MBS.MMGD.KE Give RateTables, Discounts

*PLVPGE.MBS.MMTC.KE MBS tran codes

Note: And all the parameters will be set when the NBO files will be uploaded by

business

END of MBS Change.



16/18

ASM:

Same change taking from production.

Field PER ITEM NOD need to be changed when its 3.

Org is done by the screen.

All the rest parameters will be copied into the below filesFiles are :

*PLVPGE.ASM.AMAC.KE Action Codes

*PLVPGE.ASM.AMOR.KE ASM Org*PLVPGE.ASM.AMSR.KE Customer Representatives

END of ASM Change.



17/18

FAS:

For FAS we need to changed the field DEFAULT MERCHANT ORG/NBR

because it will not accept the merchant as they are not still setup.

Note: For logo to be defined all the FAS files need to be copied.

END of FAS Change

2) TRAMS files will be initialized by running and JCL,



18/18

DPLVPGE.TRM.V811.JCLLIB(TRMINIT)

When the JCL runs it will initialize all the files And all the files which need to be doneare declared in the JCL.

3) ITS files which are to be initialized.

*PLVPGE.ITS.ITLANQ.KE*PLVPGE.ITS.ITLCTQ.KE

*PLVPGE.ITS.ITLPRQ.KE

*PLVPGE.ITS.ITLREJ.KE

*PLVPGE.ITS.ITMMST.KE

Now system is ready for the 2nd Batch

Note: At this point of time the batch should not have any date related problems since the

system is set up with the dates.

3rd Batch:

Tha batch will be run after the changes are done, along with 1 account which will be

provided by the business.After the batch is completed the account should be either posted or declined.

Then the dry batches are compiled successfully.

Note:

1) After all the dry batches are over , its time switch on the PROBE in ARQS,ARQO in

page 02 and 04 resp.

2) Any new parameters to be included can be done after the 3rd batch.3) Before initializing any file take the backup.

End of Region Setup


Documents

Region Setup