Changing the binary directory (BINDIR) used by the SMP/E APPLY

Resolving The Problem

Changing the SMP/E settings related to the E2E bindir (eqqBINDIR):

If the HFS or zFS which is updated when PTFs are applied
which affect the E2E bin directory members needs to be changed,
the following procedure may be used.

This example assumes that the install was done with the default bin directory,
/usr/lpp/TWS/V8R2M0/bin.

This proedure will change the directory for SMPE APPLY jobs to
/u/tws82bin/usr/lpp/TWS/V8R2M0/bin.

Note: The same procedure could be used for TWS z/OS 8.1 as well- just
change the appropriate file names.

Procedure for changing bindir used by SMP/E:

(1) create an HFS or zFS file to hold the new bin directory.

The example below is for a zFS file:

//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE TWSZ.V8R2M0.NEW.BINDIR.ZFS CLUSTER
IF LASTCC=8 THEN SET MAXCC=0
DEFINE CLUSTER (NAME(TWSZ.V8R2M0.NEW.BINDIR.ZFS) VOLUMES(xxxxxx) -
LINEAR MEGABYTES(20 20) SHAREOPTIONS(2))
/*
//FORMAT EXEC PGM=IOEAGFMT,
// PARM=('-aggregate TWSZ.V8R2M0.NEW.BINDIR.ZFS -compat ')
//SYSPRINT DD SYSOUT=*

(2) MOUNT the new HFS or zFS at the new bindir mount point
(/u/tws82bin):

MOUNT FILESYSTEM('TWSZ.V8R2M0.NEW.BINDIR.ZFS') TYPE(ZFS)
MODE(RDWR) MOUNTPOINT('/u/tws82bin') UNMOUNT

(3) Update the appropriate BPXPRMxx member in your system
parmlib to contain the mount from step (2). This ensures
that the mount will still be effective after an IPL

(4) From TSO OMVS, issue MKDIR commands to create the
directory structure from the new mountpoint up to the
lpp level.

For this example, /u/tws82bin/usr/lpp :


ROOT:/ #>cd /u
ROOT:/u #>mkdir tws82bin
ROOT:/u #>cd tws82bin
ROOT:/u/tws82bin #>
ROOT:/u/tws82bin #>mkdir usr
ROOT:/u/tws82bin #>cd usr
ROOT:/u/tws82bin/usr #>mkdir lpp

Do NOT create any additional directory levels or the EQQISMKD job
will fail to create the necessary directories.


(5) Run the EQQISMKD job, with the following input:
//SYSTSIN DD *
PROF MSGID
EQQMKDIR /u/tws82bin
/*

This job will create all the rest of the bin directory levels
that are required. For example, the output of this job will
contain:

EQQMKDIR /u/tws82bin
The EXEC to create the directories has begun.
It will run for a couple of minutes.

Created the following directories:
==================================
/u/tws82bin/usr/lpp/TWS/
/u/tws82bin/usr/lpp/TWS/V8R2M0
/u/tws82bin/usr/lpp/TWS/V8R2M0/bin
/u/tws82bin/usr/lpp/TWS/V8R2M0/bin/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/catalog
/u/tws82bin/usr/lpp/TWS/V8R2M0/catalog/C
/u/tws82bin/usr/lpp/TWS/V8R2M0/catalog/C/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/codeset
/u/tws82bin/usr/lpp/TWS/V8R2M0/codeset/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/config
/u/tws82bin/usr/lpp/TWS/V8R2M0/config/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Africa
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Africa/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/America
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/America/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/America/Indiana
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/America/Indiana/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Antarctica
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Antarctica/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Arctic
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Arctic/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Asia
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Asia/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Atlantic
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Atlantic/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Australia
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Australia/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Brazil
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Brazil/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Canada
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Canada/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Chile
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Chile/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Etc
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Etc/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Europe
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Europe/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Indian
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Indian/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Mexico
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Mexico/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Mideast
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Mideast/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Pacific
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/Pacific/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/SystemV
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/SystemV/IBM
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/US
/u/tws82bin/usr/lpp/TWS/V8R2M0/zoneinfo/US/IBM

Following directories already exist:
====================================
No directories already existed

Problems creating following directories:
========================================
No problems while creating directories

Created the following symlinks:
===============================
No symlink commands attempted



Deleted the following symlinks:
===============================
No unlink commands attempted


Additional messages:
====================
No additional messages

End of EXEC.
The EQQMKDIR EXEC has completed with Return Code 0

(6) Modify the EQQDDDEF job, changing only the last step
as follows:

//DEFPATH EXEC PGM=GIMSMP,REGION=4096K
//SMPCSI DD DSN=TWSZ.SMPE.V8R2M0.GLOBAL.CSI,
// DISP=SHR
//SMPCNTL DD *
SET BDY(TGT1) . /* change -PathPrefix- */
ZONEEDIT DDDEF.
CHANGE PATH('/usr/lpp/TWS/V8R2M0/'*,
'/u/tws82bin/usr/lpp/TWS/V8R2M0/'*).
ENDZONEEDIT.
/*


The only change is to the SMPCNTL input-- the CHANGE PATH
is modified to specify the new BIN directory name as shown
above. Run the EQQDDDEF job with this modification.

Note: Only the DEFPATH step needs to be run. If you run the
entire job, the earlier steps will end with RC=08 but this can
be ignored as long as the DEFPATH step gets RC=0.

The DEFPATH step will cause the DDDEFS for SEQQ0001 through SEQQ0024
to have the dataset names changed from /usr/lpp/TWS/V8R2M0
to /u/tws82bin/usr/lpp/TWS/V8R2M0.

(7) At this point, the new bin directory is still empty.
To populate it, if you have not already applied the latest
available fix pack PTFs (USS port), then RECEIVE these PTFs.
(for example, for fix pack6 you would
RECEIVE PTFs UQ96309 and, UQ96295.)

Once the RECEIVE is done (or if the PTFs were previously
APPLIED) run the APPLY for the fix pack PTFS plus the FMID JWSZ203
with the REDO option- this will cause
the new binary directory to be populated.

For example for fix pack6, the APPLY would be:
APPLY S(JWSZ203,UQ96309,UQ96295)
BYPASS(HOLDSYS(ACTION,DB2BIND,DOC,DEP))
REDO.

The reason that the JWSZ203 FMID must be applied is that it contains
the zoneinfo directory contents (these are not part of each fix pack PTF).

(8) From TSO OMVS, issue a change directory (cd) to the new
binary directory. then issue command ls -la .
The output should look something like this (the file sizes
and dates will be different depending on your fix pack
level):

drwxr-xr-x 3 OMVSKERN OMVS 672 Mar 18 20:21 .
drwxr-xr-x 7 OMVSKERN OMVS 416 Mar 16 23:09 ..
drwxr-xr-x 2 OMVSKERN OMVS 640 Mar 18 20:21 IBM
-rwxr-xr-x 2 OMVSKERN OMVS 2281472 Mar 18 20:21 batchman
-rwxr-xr-x 2 OMVSKERN OMVS 1548 Mar 18 20:21 config
-rwxr-xr-x 2 OMVSKERN OMVS 3398 Mar 18 20:21 configure
-rwxr-xr-x 2 OMVSKERN OMVS 1232896 Mar 18 20:21 evtsize
-rwxr-xr-x 2 OMVSKERN OMVS 1487 Mar 18 20:21 execscr
-rwxr-xr-x 2 OMVSKERN OMVS 2355200 Mar 18 20:21 mailman
-rwxr-xr-x 2 OMVSKERN OMVS 1982464 Mar 18 20:21 netman
-rwxr-xr-x 2 OMVSKERN OMVS 1823 Mar 18 20:21 refresh
-rwxr-xr-x 2 OMVSKERN OMVS 1470464 Mar 18 20:21 starter
-rwxr-xr-x 2 OMVSKERN OMVS 3538944 Mar 18 20:21 translator
-rwxr-xr-x 2 OMVSKERN OMVS 2064384 Mar 18 20:21 writer


(9) Now that the new BINDIR is populated, if you want the E2E
environment to run from this new bindir, you will need to
change the BINDIR parm in your TOPOLOGY statement:


TOPOLOGY BINDIR('/u/tws82bin/usr/lpp/TWS/V8R2M0')

Also you may need to change any other JCL which uses the
bin directory, for example, the EQQPCS05 job:

//ALLOHFS EXEC PGM=BPXBATCH,REGION=4M
//STDOUT DD PATH='/tmp/twspcs05out',
// PATHOPTS=(OCREAT,OTRUNC,OWRONLY),PATHMODE=SIRWXU
//STDIN DD PATH='/u/tws82bin/usr/lpp/TWS/V8R2M0/bin/config',
// PATHOPTS=(ORDONLY)
//STDENV DD *
eqqBINDIR=/u/tws82bin/usr/lpp/TWS/V8R2M0

The E2E server must be cycled if the TOPOLOGY parms were modified.

If however, you want the E2E environment to continue using the
old bindir name, no parmlib or JCL changes are required.
However, when you apply new maintenance that affects the
binary directory for E2E, you will need to copy the
bindir pointed to by the SMP/E APPLY job to your
"production" bin directory, for example, by using DFDSS
dump and restore.