Pups Guide

8/18/2019 Pups Guide

1/14

Ford Credit

PUPS

Implementation


2/14

Ford Credit PUPS Implementation

Background 4

PUPS Overview 4

Login 5

PUPS Migration Process 6

Approvers 6

Training 7

Support 7

Build Team Off-Hours Coverage for the COMPASS Platform COCS Off-Hours Coverage for !ega"# Appli"ations

PUPS Tool Support

Syste Maintenance !

Main"rae #e$ete %e&uests !

Security !

$oles %

Post Migration Audit %

're&uent$y Asked (uestions )'A(s* +

T#pe of "hange &'

'or Approvers On$y ,-

'or Su.itters On$y ,/

Su(mitting Builds &)

Produ"tion *mergen"ies &)

Auto $elin+ &)Changing the Migration $e,uest &)

Se"urit# &)

var...apps"onversiontmps"rat"h/0)&)%1&%&2do" Page 0!ast revision3 1&4'0


3/14


%evision 0istory

Author 5ate 5es"ription

Be"+# Million ')'66 Initial $evision for laun"h of COMPASS appli"ation

on Fa"ilit# 72Be"+# Million ')'6'' Updated for Fa"ilit# A Implementation

Be"+# Million '808'' Updated for 9C!A and 9C!7 a"tivities

Be"+# Million &'0''' Updated to in"lude timings for Produ"tion releases2

Bo( !eggett &&00'' Updated to in"lude *lement T#pe CA9C!2Bo( !eggett ')00'& Updated to in"lude *nvironment :I: in A"tivit# FCA&2

var...apps"onversiontmps"rat"h/0)&)%1&%&2do" Page )!ast revision3 1&4'0


4/14


Background

PUPS is the ne. Ford Credit standard tool for (uilding and migrating mainframe "ode2

The PUPS ;Produ"tion Update Pro"essing S#stem< appli"ation .as developed (# the Material Planning = !ogisti"s

;MP=!< group at Ford Motor Compan#2 PUPS has (een implemented in the follo.ing Ford Motor Compan#

lo"ations3 Material Planning = !ogisti" ;MP=! Bra?il> Argentina> Pur"hasing and Finan"e> .ith and estimated1'' developers trained to use the tool (# August> &6662

The purpose of this do"ument is to des"ri(e the PUPS Implementation at Ford Credit2 It is a supplement to the

do"umentation handed out at the training session2 $efer to #our training handouts for spe"ifi" information on usingthe PUPS appli"ation2

PUPS Overview

PUPS Organi?ation

Activity is the highest level in PUPS and is dedi"ated to a group of programs that share the same migration path2

Modu$e further defines an a"tivit#2 1$eents and Peop$e are atta"hed to a module2

1$eents are the programs .ithin the module2

Peop$e are the developers and approvers authori?ed to .or+ .ithin the module2

PUPS supports four environments> Test> Integration> *du"ation and Produ"tion2 This "hart sho.s ho. the PUPSenvironments "orrespond to the COMPASS Platform and !ega"# Appli"ation environments2

'aci$ity Activity #escription Modu$e #escription PUPS

1nvironents

Fa"ilit# A FCA& @on-IMS programs for

!ega"#

Appli"ations

A!! All Sour"eCode

T StagingI Integration

* ualit# Assuran"e

P -- Produ"tion

Fa"ilit# A FCA0 IMS programs for

!ega"#

Appli"ations

A!! All Sour"e

Code

T Staging

I -- Integration

* ualit# Assuran"eP -- Produ"tion

Fa"ilit# A 9C!A Produ"tion 9C! A!! Produ"tion P -- Produ"tion


Activity

Modu$e

Peop$e1$eents


5/14


9C!

Fa"ilit# 7 CMP7 COMPASS

Platform

;5evelopment<

A!! COBO!

Programs

T Staging

I -- Integration

* F$STP -- ualit# Assuran"e

Fa"ilit# 7 CMP7 COMPASS

Platform;5evelopment<

$PC $PC Shell

Programs

T Staging

I -- Integration* *du"ationF$STP -- ualit# Assuran"e

Fa"ilit# 7 9C!7 Produ"tion 9C! A!! Produ"tion

9C!

P -- Produ"tion

Fa"ilit# H CMPH COMPASSPlatform

;Produ"tion<

A!! COBO!Programs

I StagingP -- Produ"tion

Fa"ilit# H CMPH Produ"tion 9C!

monitored (#

TS=O

$PC $PC Shell

Programs

I Staging

P -- Produ"tion

Fa"ilit# H 9C!H COMPASS

Platform

;Produ"tion<

A!! Produ"tion

9C!

P -- Produ"tion

Login

5uring the set-up period on ea"h fa"ilit#> it .ill (e ne"essar# to use the follo.ing "list upon login32"cr$a37coc$ist)dev*2

This "list .ill eventuall# (e"ome the Ford Credit development "list 2"cd.acoc$ist)dev*2



6/14


PUPS Migration Process

Step Action %esponsi.$e Party

& Modif# sour"e "ode

• Sear"h for other developers .ho have the "ode "he"+ed out

• Che"+ out the element

• Modif# the element

• Cop# the sour"e "ode to the staging li(rar#3

Fa"ilit# A3 FCUB!52P$O52STA7I@72!IB$A$DFa"ilit# 73 FCUB!52STA7I@72!IB$A$D

;$efer to Main Steps For Developers Using PUPS Migration Tool do"ument

handed out at PUPS Training2<

5eveloper

0 Build Migration $e,uest 5eveloper

) Approve migration re,uest ;see Approver se"tion for re,uirements for ea"h

environment2<

Approver

4 Su(mit the migration Su(mitter

1 Monitor the :In-Flight: s"reen for (uild status> "ompletion and failures2 5evelopers>Su(mitter

At this time> the su(mitter role is handled (# t.o separate teams3 The Build Team and COCS2 The Build Team is

responsi(le for migrations that o""ur on Fa"ilit# 7 and H for the COMPASS platform2 COCS is responsi(le forlega"# appli"ation migrations on Fa"ilit# A2

Approvers

1nvironent Approver Process

IT Su(mitter The su(mitters .ill monitor the In-Flight s"reen and .illapprove and su(mit Migration $e,uests for the ITenvironment2

F$ST TM The TM Team .ill monitor the In-Flight s"reen and

.ill approve Migration $e,uests for the F$ST

environment2 This is a COMPASS environment andeEists onl# on Fa"ilit# 72

A Proe"t !eader or Supervisor A Migration $e,uests .ill (e approved (# the

appli"ationGs Supervisor or Proe"t !eader on the In-

Flight s"reen2

P$O5 Proe"t !eader or Supervisor COMPASSFor migration re,uests to the Produ"tion environment on

Fa"ilit# H3

• Complete the CM$ form• 7et a signature s#stems and (usiness approvers

• 5eliver to the Build Team2

!ega"# Appli"ations

For migration re,uests to the Produ"tion environment on

Fa"ilit# A3 Su(mit a PUPS Build $e,uest2

@ote3 If #our "hanges re,uire "oordination of 9C! and



7/14


1nvironent Approver Process

CA "hanges #ou must fill out a PM$ form and su(mit

it to COCS2

Training MP=! provides training to ea"h appli"ation team upon implementation of PUPS2 Training for ne. developers is

provided upon re,uest through 9oe Moone# ;9MOO@*D&< at MP=!2

Support

Bui$d Tea O""0ours overage "or te OMPASS P$at"or

The Build Team is availa(le 04E for emergen"# (uilds to "orre"t an immediate pro(lem in the Production

environment2 Conta"ts are listed in order (elo.2 The developer is responsi(le for su(mitting the ne"essar#

paper.or+ and signatures the follo.ing (usiness da#2

ontact P%O'S 8#

Primar# 5ut# Anal#st FCBTP$IMSe"ondar# 5ut# Anal#st FCBTS*C5

OS O""0ours overage "or Legacy App$ications

ontact P%O'S 8#

PUPS Too$ Support

hen developers have a pro(lem using the PUPS tool the# should first loo+ to mem(ers of their team for assistan"e2On"e this resour"e is eEhausted> "onta"t the Build Team2

ontact 9o sou$d ake contact #S 8# or Mai$ing List

Mem(ers of the appli"ation team 5eveloper

• COMPASS Platform the Build

Team2

• !ega"# Appli"ations -- Computer

Operations2

5eveloper COMPASS Platform

f"/(ldteam...2"lient2ford2"om

!ega"# Appli"ations9BO@50

5U@CA@&

Appli"ation Infrastru"ture -- Te"hni"al

Support

Build Team or COCS 9MCCO@@4

$A!!*@)&MP=! Te"hni"al Servi"es A*ST8

$CHA!*!A

$H*@$D&

9MOO@*D&

System Maintenance

S#stem maintenan"e is "oordinated (# the Appli"ation Infrastru"ture -- Te"hni"al Support team2

var...apps"onversiontmps"rat"h/0)&)%1&%&2do" Page !ast revision3 1&4'0


8/14


Mainframe Delete e!uests

Sour"e "ode "an (e deleted (# "reating a delete re,uest ;J6' Build 5elete $e,uest - 5elete *lement from the

Appli"ation ea"h user must have the follo.ing3

• A C5S re"ord2 PUPS uses information from C5S to populate its data ta(les2

• A $ACF I5 that allo.s the user a""ess to the appropriate Fa"ilit#2 The $ACF I5 must also (elong to the 7roup

FCUFC&2 hen re,uesting ne. $ACF I5s> it is a good idea to model the I5 after one that alread# uses

PUPS2

• A PUPS se"urit# re"ord2 The spe"ifi" privileges given to PUPS users depends upon the role of the user ;See

Belo. *lmupd T> Approve> Conta"ts

ApproverTM Approve

5eveloper Che"+out> $e,uest> Can"el> *lmupd T

Su(mitter Che"+out> $e,uest> Can"el> Approve> Su(mit> *lmupd T> *lmupd I> *lmupd *> *lmupd

P> Se"urit#

Post Migration Audit

The 7AO re,uires that &'K of all migration re,uests and &''K of all emergen"# re,uests have a :Compare $eport:generated2 Therefore> ever# 66th Produ"tion migration re,uest and all emergen"# re,uests .ill (e flagged2 The

Compare $eport must (e revie.ed and approved (# a supervisor or proe"t leader (efore the sour"e "ode "an (e

migrated again2

"re!uently Asked #uestions $"A#s%

What is needed to create a Migration request from the TEST environment?

An#time #ou modif# sour"e "ode> PUPS eEpe"ts the $ACF of the "he"+out> migration re,uest and the o.ner of the

sour"e "ode in the staging li(rar# to (e the same2 If #ou do not have the "ode "he"+ed out and the sour"e "ode in the

staging li(rar# does not (elong to #ou> PUPS .ill not allo. #ou to "reate a migration re,uest2

The order is as follo.s3

&2 Che"+ out the sour"e "ode

02 Cop# the "ode into the staging li(rar#)2 Create a migration re,uest

Che"+out $ACF

var...apps"onversiontmps"rat"h/0)&)%1&%&2do" Page %!ast revision3 1&4'0

$ACF


9/14


Migration O.ner of Sour"e

$e,uest in Staging !i(rar#



10/14


My Project Leader is not in today. How can find out who e!se can a""rove my

request?

To find a list of approvers for #our a"tivit#> go to the User Se"urit# Maintenan"e s"reen ;J00 use the .ho ;.< a"tion to (ring up the C5S re"ord2

What is the "rocess for adding new code to P#PS?

To add sour"e "ode to PUPS3

&2 Create an element profile2 This defines the element to the PUPS tool2

02 Che"+ out the program using the :n: ;ne.< a"tion2

Tips3

• Onl# one developer "an "he"+ out a ne. program2

• Program sour"e "ode "annot eEist in the staging li(rar#2

When are $hec%out &ecords needed?

Che"+out re"ords are re,uired .hen sour"e "ode is (eing modified2 Che"+ out re"ords are not re,uired .henmigrating from one se"ure environment to another ;i2e2> :I: to :*: the Build Team "an approve and su(mit the re,uest2

What are the E!ement Ty"es?

*lement T#pes are3 Bat"h> Online> Su(routine> Cop#li(> In"lude> CA9C!2 The element t#pe .ill (e retrieved (#

the tool if the *lement @ame is uni,ue .ithin the a"tivit#2

When can $)MP*SS changes 'e moved into Production?For COMPASS Appli"ation Full $eleases and ee+l# Produ"tion $eleases3

Type o" cange #ate:Tie re$eased toProduction

Te signed M% ust .e

received .y;

MPP ee+l# $elease 0341 AM ednesda# COB Monda#

BMP ee+l# $elease %3'' AM - &3'' PM Frida# COB ednesda#

*mergen"# FiEN Upon $e,uest

var...apps"onversiontmps"rat"h/0)&)%1&%&2do" Page &'!ast revision3 1&4'0


11/14


N $is+ assessments are re,uired for all emergen"# fiEes and CM$s that are re"eived after the "ut-off2

Pre-$elease erifi"ation in S#stems S or Bran"h UPre-release verifi"ation is used primaril# to verif# that the PC portion of the COMPASS appli"ation (uilt properl#2hen the Business and S#stems agree> non-disruptive MPPs "an (e (uilt one .ee+ earl# for verifi"ation purposes2

$emem(er3 There is onl# one set of Produ"tion li(raries Pre-release verifi"ation o""urs in Produ"tion2

have a MPP change that didn+t su'mit. $an you just 'ui!d it during the day?

@o MPPs are intera"tive programs and must (e moved to Produ"tion at a time .hen the COMPASS Bran"hes and

Servi"e Centers are not using the s#stem2 Most of the MPPs "annot (e "hanged during (usiness hours .ithoutris+ing Produ"tion2

Within P#PS, some deve!o"ers are notified when their jo's com"!ete and others are

not. How can 'e notified when jo's com"!ete?

The notifi"ation is a fun"tion of TSO> not PUPS2 ithin PUPS> #ou "an "he"+ the notifi"ation setting (# t#ping TSO

P$OFI!* at the "ommand line2 The notifi"ation is a toggle> #ou .ill see either I@T*$COM or line2 The notifi"ation

is a toggle> #ou .ill see either I@T*$COM or @OI@T*$COM ;among other settings in the profile t#pe TSO P$OFI!* I@T*$COM at the "ommand line2

How can get a hardco"y of the $om"i!e Listing and $om"are &e"ort?

There is a ne. utilit# "alled :PUPS Print: that allo.s a developer to print OUT!IST or COMPA$* datasets2 The

utilit# "an (e a""essed from the TSO main panel (# sele"ting Appli"ations ;O< and PUPS Print ;PC element name and report t#pe2

When migrating 'oth co"y'oo%s and "rograms in P#PS, how can get the "rograms

to -wait- for the co"y'oo%s to finish "rocessing?

First> (uild the migration re,uest for the "op#(oo+Q neEt> (uild the re,uest for the "alling program2 hen the "alling

program is re,uested> PUPS .ill notif# the user that the "alling program .ill .ait for the "op#(oo+ to (e migrated2

Please note3 This a"tion .ill not o""ur the first time a "op#(oo+ is migrated as the *lement Cross $eferen"e is

updated upon ea"h (uild2

When does the $L swee" jo' run?

The s.eep o( runs Monda# through Saturda# at )3)' PM on Fa"ilities A> 7 and H2 The Build Team "he"+s the

PUPS in-flight ,ueue at )3'' PM2 At this time> the last 9C! o(s of the da# are su(mitted to the s.eep li(rar#2

t+s after /0/1 PM and need a $L change for tonight+s run. How can get this

done?

After )3)' PM> there are t.o things #ou must do2 &< Su(mit a re,uest for a :spe"ial: that .ill run for that evening2;Spe"ials are handled (# TS=O as per their pro"ess


12/14


"or Approvers Only

To approve a migration re,uest #ou must (e set-up as an approver in the PUPS tool2 The steps are3

&2 !og on

02 At the COMPASS 5evelopers C!IST menu> ta+e the default option2

)2 *nter PM at the options line to start the PUPS Migration tool2

42 7o to the In-Flight S"reen ;J&'<

12 Sear"h for Migration re,uests .ithin the a"tivit# and module2

• Use LPF& to (ring up the in,uir# s"reen

• *nter A"tivit#2 !eave Module (lan+ and #ou .ill pi"+ up re,uests for an# module .ithin #our a"tivit#2

82 Su(mitters3 !oo+ for Migration re,uests .here the :TO: environment is :I:

TM3 !oo+ for Migration re,uests .here the :TO: environment is :*:Supervisors and

Proe"t !eaders3 !oo+ for Migration re,uest .here the :TO: environment is :P:and for lega"# appli"ations .here :TO: environment is :*:

2 A"tions ;AC "olumn the# "an re"all the status from Su(mitted to Approved .ithout losing the

approval2

%2 hen the appropriate a"tion has (een ta+en> use LPF) to (a"+ out of the s"reen2

var...apps"onversiontmps"rat"h/0)&)%1&%&2do" Page &0!ast revision3 1&4'0


13/14


"or Su&mitters Only

At this time> the su(mitter role is handled (# t.o separate teams3 The Build Team and COCS2 The Build Team isresponsi(le for migrations that o""ur on Fa"ilit# 7 and H for the COMPASS platform2 COCS is responsi(le for

lega"# appli"ation migrations on Fa"ilit# A2

Su.itting Bui$ds

&2 The Build Team and COCS .ill monitor the In-Flight s"reen ;J&'< for ne. Migration $e,uests for their

respe"tive appli"ations2

02 For migration re,uests to the Integration environment> the Build Team and COCS .ill approve2 All other

environments> the su(mitters .ill .ait for the authori?ed approver to approve the migration re,uest2 ;See

se"tion:For Approvers Onl#:


14/14


var...apps"onversiontmps"rat"h/0)&)%1&%&2do" Page &4!ast revision3 1&4'0

Pups Guide

Documents

Transcript of Pups Guide