The Wonderful World of new PSB's…….

1. Fill out IMS SYSGEN request for the new PSB (http://www.fcmis.ford.com/fcusdadba/dbaindex.htm)(http://www.fcmis.ford.com/fcusdadba/dbaindex.htm

2. Create PUPS PSB member - PUPS option 20…. (type PSBBATCH, CMPG)- you can copy the profile from an existing PSBBATCH member- create it as a “BA”, it will create the “BT” when you assemble it

3. Checkout your PSB -- PUPS option 1

4. Create your PSB, in FCU@BLD.CMPG.TEST.PSB

5. Submit your PSB to be assembled (just submit using the PUPS option 3 – compile)

6. You will need to migrate the PUPS PSB (type PSBBATCH) member though each environment (INTE, FRST, QA) This PUPS move is how the PSB will be gen'd for each environment

7. You will need to move the PSB to PROD at least 1 week prior to the time that you are launching your program. It will move from FRST, but it does require a CMR.If it is a new program and you can do it sooner, that is probably better, but the bottom line is that the gen's are done on the weekend, so if you put in a new PSB on the same day as your program (M-F), you will not be able to run it until after the weekend (unless you can get Tech Support to "gen" it sooner)

The Wonderful World of PSB changes……

1. Checkout your PSB -- PUPS option 1

2. Modify the member in FCU@BLD.CMPG.TEST.PSB - if you are adding GSAM's, you need to do it at the bottom (like a DB2 table)

3. Submit your PSB to be assembled (just submit using the PUPS option 5 – compile)

4. You will need to migrate the PUPS PSB (type PSBBATCH) member though each environment (INTE, FRST, QA) This PUPS move is how the PSB will be gen'd for each environment

5. You will need to move the PSB to PROD at least 1 week prior to the time that you are launching your program. It will move from FRST, but it does require a CMR.If it is a new program and you can do it sooner, that is probably better, but the bottom line is that the gen's are done on the weekend, so if you put in a new PSB on the same

day as your program (M-F), you will not be able to run it until after the weekend (unless you can get Tech Support to "gen" it sooner)

Things to think about when you are creating a new PSB……

When you are creating your PSB by copying from another PSB, you need to know if the one you are copying from is defined as “serial” or “parallel”, and you need to know how your PSB will function.

“serial” - the program will not be shared, or have the need to run the program at the Same time by more than one job “parallel” - the program will/could be shared by multiple jobs To find out how an existing PSB is defined do the following:

In addition, it affects your ability to make changes to the PSB in PIT while you are coding/testing. If the PSB is defined as parallel and you need to add a GSAM, it will not be picked up until the next refresh (weekends)….or you have to ask that the PSB be refreshed (Jim Scherer…who asks Ford to do it) to pick up the changes. If it is defined as serial, the change will take effect immediately without anyone doing a refresh.

There are two datasets one that shows what is currently set up, the other shows the changes that are waiting to be made the next time IMS is brought down (usually on a Sunday). Simply do a find on the PSB you’re looking for.

APPLCTN PSB=YGA220BA,PGMTYPE=BATCH,SCHDTYP=SERIAL this is a serial PSB APPLCTN PSB=YGA300BA,PGMTYPE=BATCH,SCHDTYP=PARALLEL this is a parallel PSB

----------------------------------------------------------------------For Facility G, PIT & IT

IMST8.STAGE1.LIST Shows what currently exists IMST8.STAGE1.LIST.NEW Shows changes that are about to be made

For FRSTIMST2.STAGE1.LIST IMST2.STAGE1.LIST.NEW

For QAIMSE8.STAGE1.LIST IMSE8.STAGE1.LIST.NEW

---------------------------------------------------------------------For Facility H

IMS8.STAGE1.LIST IMS8.STAGE1.LIST.NEW