Migration and Fallback issues for TWSz 9.2 ( TWSZOS920 )

Answer

For general issues with TWSz (COMPID 5697WSZ01 ) migration please refer to technote 1608030:

http://www.ibm.com/support/docview.wss?uid=swg21608030

There are some specific issues involving TWSz 9.2 which will be discussed here;

(1) EQQJOBS – new/changed samples - these SEQQSAMP members should be reviewed after running EQQJOBS:

 EQQBENCO
• New sample to encrypt passwords in the OSLCOPTS statement contained in
the EQQPARM library member as specified by the OSLCPARM keyword in the
OPCOPTS statement. E.g. : OSLCPARM(STDOSLC).

 EQQSMLOG
• New sample to repro the inactive MLOG into a GDG data set.

 EQQPCS12
• New sample to allocate dthe GDG root where to archive the MLOG if you are
using the new switch MLOG function

 EQQPCS02
• Old sample allocating new data set for alternate MLOG (EQQMLOG2) used by
the new switch MLOG function

(2) Started task JCL changes
 The only change is related to the switch MLOG new function that requires
the usage of an alternate MLOG data set.
 This function is applicable both to tracker and controller: if used the
related started task must contain the DD statement EQQMLOG2 pointing
to the alternate MLOG data set.

(3) VSAM migration

Note: In general problems with fallback to the previous release can be avoided if new
features are NOT implemented until you are confident that a "backwards" migration
will not be needed.

 VSAM records layout is not changed in TWSz 9.2.0 but migration is

needed anyway because we need to:

• Update header FMID/release value

This value is used to check that the product is using the correct version of data sets.

• Parallel Server limit increase

The field containing parallel server value was big enough to store new limit but check
must be added to avoid fallback problems

• Changes occurred in previous release

Migrating from 8.6.0 to 9.2.0 we need to apply the layout changes of 9.1.0

 The migration of AD data set has a new trace message (EQQIC66I) to

show the id of the just migrated single application

• Trace is defaulted to YES but can be removed setting the value to NO in the

EQQICNVS sample

(A) VSAM migration - Application Data base (AD)

ADR migration (TWSz 8.6.0  TWSz 9.2.0)
• Resolution criteria defaulted to Closest preceding
• Mandatory option defaulted to No.

ADR fallback (TWSz 9.2.0  TWSz 8.6.0)
• New resolution criteria are converted to Closest Preceding, Mandatory option is converted to "NO", and Msg EQQIC63W is issued

EQQIC63W APPLICATION &AD HAS EXTERNAL OR CONDITIONAL PREDECESSORS
EQQIC63I USING RESOLUTION OPTIONS THAT CANNOT BE ROLLED BACK: THEY WILL BE
EQQIC63I CONVERTED TO OLD CRITERIA (CLOSEST PRECEDING, NO MANDATORY)

• New value blank for deadline is defaulted to 002400: Msg EQQIC65W is issued

EQQIC65W APPLICATION &AD HAS A RUN CYCLE WITH BLANK DEADLINE THAT CANNOT
EQQIC65I BE ROLLED BACK: DEADLINE WILL BE SET TO 002400

• New value blank for input arrival time will cause AD skip: Msg EQQIC64W is issued

EQQIC64W APPLICATION &AD HAS A RUN CYCLE WITH BLANK INPUT ARRIVAL AND
EQQIC64I CANNOT BE ROLLED BACK: APPLICATION WILL BE SKIPPED


(B) VSAM migration – Workstation data base (WS)

WS migration (TWSz 8.6.0, TWSz 9.1.0  TWSz 9.2.0)
• No new defaulting is needed.
 WS fallback (TWSz 9.2.0  TWSz 8.6.0)
• New run cycle groups are supported only from 9.1.0 on, so they cause the record skip and Msg
EQQIC59W is issued:

EQQIC59W A FALLBACK CANNOT BE PERFORMED ON RUN CYCLE GROUP &RGNAM.
EQQIC59I IT IS NOT SUPPORTED IN EARLIER VERSIONS OF THE PRODUCT.
EQQIC59I THE RECORD IS SKIPPED.

WS fallback (TWSz 9.2.0  TWSz 8.6.0, TWSz 9.1.0)
• A value of parallel server greater than 99 is not supported in previous releases so it is defaulted to 99 and Msg EQQIC67W is issued:

EQQIC67W IN THE FALLBACK PROCESS OF THE WORKSTATION DATABASE, THE NUMBER OF
EQQIC67I PARALLEL SERVERS DEFINED FOR SOME &WSNAM INTERVALS WAS FORCED TO 99
EQQIC67I BECAUSE THE 99 LIMIT WAS EXCEEDED.

(C) VSAM migration – Long Term Plan data base (LTP)

LTP migration (TWSz 8.6.0  TWSz 9.2.0)
• LTP header LTPREMSHIFT is defaulted to 0
• LTP occurrence Mandatory pending predecessor number is defaulted to 0.

LTP fallback (TWSz 9.2.0  TWSz 8.6.0)
• Mandatory pending predecessors are removed and the dependency referring to them are marked as
deleted. Msg EQQIC69W is issued:

EQQIC69W LTP OCCURRENCE &APPL &IA HAS MANDATORY PENDING PREDECESSORS:
EQQIC69I THEY HAVE BEEN MARKED AS DELETED.

• Blank deadlines are not supported in 8.6.0 and defaulted to 2071-12-31 24.00: Msg EQQIC60W is
issued:

EQQIC60W INPUT LTP OCCURRENCE &APPL &IA HAS A BLANK DEADLINE. IT IS SET
EQQIC60I TO A DEFAULT VALUE (2071-12-31 24.00)

(D) VSAM migration – Current Plan data base (CP)

CP migration (TWSz 8.6.0 , TWSz 9.1.0  TWSz 9.2.0)
• No new defaulting is needed.

CP fallback (TWSz 9.2.0  TWSz 8.6.0)

• Mandatory pending occurrences (status M) are not supported in TWSz 8.6.0 and are skipped: Msg
EQQIC61W is issued:

EQQIC61W INPUT CURRENT PLAN OCCURRENCE &AD &IA HAS A MANDATORY PENDING
EQQIC61I STATUS. IT IS NOT SUPPORTED IN EARLIER VERSION. THIS OCCURRENCE IS
EQQIC61I SKIPPED

• Operation having mandatory pending predecessors are not supported in TWSz 8.6.0 and cannot be
skipped. For this reason migration is not stopped but fails with RC=8: Msg EQQIC62E is issued:

EQQIC62E ROLL-BACK MIGRATION NOT POSSIBLE. JOBS IN MANDATORY PENDING
EQQIC62I STATUS MUST BE REMOVED. CHECK FOLLOWING OPERATION:
EQQIC62I &AD &IA &OPER FAILURE


CP fallback (TWSz 9.2.0  TWSz 8.6.0, TWSz 9.1.0)

• A value of parallel server greater than 99 is not supported in previous releases so it is defaulted to 99
and Msg EQQIC68W is issued:

EQQIC68W IN THE FALLBACK PROCESS OF THE CUURENT PLAN, THE NUMBER OF
EQQIC68I PARALLEL SERVERS DEFINED FOR SOME &WSNAM INTERVALS WAS FORCED TO 99
EQQIC68I BECAUSE THE 99 LIMIT WAS EXCEEDED.
NEW

(E) VSAM migration – XD data base

XD migration (TWSz 8.6.0 , TWSz 9.1.0  TWSz 9.2.0)
• No new defaulting is needed.

XD fallback (TWSz 9.2.0  TWSz 8.6.0)
• New records XD03 and XD12 are not supported in TWSz 8.6.0 and are simply skipped.