APPLYING USERMOD

Sounds confusing ??

PTF's , Usermod , Sysmod ....

Are they same .... are they different ??

Why are we Applying it ...

The requirement

CR 27963

Need to APPLY Usermod : (M400005) while manufacturing z/OSMF V2R1 orders.

Usermod :

A Sysmod which is not yet PTF

Not officially released by IBM

In Beta stage

This "would-be" PTF was supposed to configure few changes / work on some patches like overriding files etc.(for V2R1 z/OSMF)

That would happen after Jan 2016 , but we won't get much time after that.

The requirement

CR 27963

Need to APPLY Usermod : (M400005) while manufacturing z/OSMF V2R1 orders.

Usermod :

A Sysmod which is not yet PTF

Not officially released by IBM

In Beta stage

This "would-be" PTF was supposed to configure few changes / work on some patches like overriding files etc.(for V2R1 z/OSMF)

That would happen after Jan 2016 , but we won't get much time after that.

SYSMODS

SYSMOD (System Modification) is the actual package of elements and control information for SMP/E to install and track system modification

Types of SYSMOD

FUNCTION

PTF (Program Temporary Fix)

APAR (Authorized Program Analysis Report)

USERMOD

Work they do..

Introducing an element into the system

Preventing or fixing problems with an element

Customizing an element

Keeping track of the elements of the system

PTF Tested fix for a problem from IBM

Usermod For Changing / updating the default behavior or functionality

How we started

CPPDEV.HSMA210.SPE4.FIXES(M400005) was downloaded from z/OS build system and the same was used while manufacturing

N phase changes

After SMPCNTL changes , N phase jobs we updated in spool.

Bottleneck point

In PB phase

We went again to SMPCNTL and updated all members (having instances of Usermod) with
these 4 pre-requisite PTF's .

Restarted the job from failed step (like ACPTS31 or ACPTS40) .

Got the issue for three PTF's which were SUPed : UI27788,UI28590 and UI30955

Tried more with SMPCNTL regarding these 3 SUPed PTF's

Order failed again for new PTF :UI31219

Edited SMPCNTL again for this PTF > Restarted the job

Order failed again

SMPCNTL was not the same anymore

Changes in this dataset were difficult to track

Turned out to be more tedious way

What we missed

Pre-requisite PTFs (UI28962, UI31002, UI32098 and UI90028) are already present in CBCACHE datasets

They are already having well defined Apply / Accept definitions.

They have predefined sequence of flow during
manufacturing

We just introduced those PTF's (prerequsites) in MLIMIT member in K phase .

The correct way

Forcing the pre-requisite PTF's in K phase

Order SMPCNTL update

SMPCNTL members were populated with Usermod : CPPDEV.HSMA210.SPE4.FIXES(M400005)

N phase jobs in spool were updated with Usermod instance > Submitted

P phase was activated from spool

P phase jobs ran successfuly

Before activating Q phase , we can check status of USERMOD in CSI :

Activate Q phase now

Relax and let the order build complete

Click to edit the title text format