Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
IMS Installation
Workshop
Presentations
IBM SILICON VALLEY LABORATORY
IMS SOFTWARE SERVICE DELIVERY
555 BAILEY AVENUE
SAN ...
 The objectives this workshop are:
 Review IMS packaging, Installation and IVP dialog process for IMS
 Discuss IMS migr...
IMS Packaging
IMS Packaging
4
Packaging
• No major changes in packaging since IMS 8.1
• Installation via CBPDO, ServerPac or CustomPac
• All FMIDs ar...
5
Job to allocate target and distribution libraries split up into two jobs
• DFSALOC1 – Allocate target and distribution ...
6
Only IRLM 2.3 (FMID HIR2230) provided
•Works with all supported releases of IMS
 IVP Dialog Changes – V13
 Variables ...
7
SMP/E Processing
•Always RECEIVE current Enhanced HOLDDATA prior to SMP/E processing
–For complete descriptive informat...
Installation
Installation
 The IMS product can be distributed by a variety of methods. Which are as follows:
CBPDO - DBS Feature distribution tape...
 Installation Documentation Precedence
•Documentation provided with CBPDO, ServerPac, etc.
•PSP Bucket
• Contains the lat...
 The following is a list of the SMP/E Setup and SMP/E sample jobs provided:
 DFSALA - Allocate and initialize new CSI da...
Optional jobs provided to install IMS in its own unique SMP/E environment
(GLOBAL Zone)
• DFSALA - Allocate and initializ...
 JCL provided in Program Directory to unload sample jobs to perform
SMP/E processing and setup
 Each job contains instru...
14
The following is an example of the instructions for customization of the sample
jobs:
//* NOTES: */
//* 1) REVIEW THE S...
IMS IVP Dialog
IMS IVP Dialog
 The following are input datasets used by the IVP dialog:
IMS.SDFSISRC - Contains sample application and
miscellaneous s...
 The following are output datasets used by the IVP dialog:
 IMS.INSTALIB - JCL for the jobs to be run
 IMS.INSTATBL - I...
18
EX 'IMS.SDFSEXEC(DFSIVPEX)' 'HLQ(IMS)'
IVP Export
IVP Variable Export Utility
Command ===>
Enter the following informat...
19
Exported dataset can be modified using ISPF to change variables in mass
• Can use ISPF edit command for example to cha...
 The IVP dialog is started by issuing the following command from ISPF option 6:
• EX 'IMS.SDFSCLST(DFSIXC01)' 'HLQIV(iii)...
When the dialog is started for the first time for each release the
following type of panel will be displayed:
==== === ===...
Copyright Panel
Information Management System (IMS) Version 14.1
Licensed Materials - Property of IBM
"Restricted Material...
 Select the highest number representing the system you wish to install
 The option selected will be used in determining ...
Help
------------------------------------------------------------------------------
IVP Sub-Option Selection - DBT
Command...
Sub - Option Change Verification Panel
Help
------------------------------------------------------------------------------...
Table Merge Request Panel
Help
------------------------------------------------------------------------------
IVP Table Me...
VG Table Merge in Progress Panel
IVP VG Table Merge In Progress - DBT
Table Merge Progress Indicator
Variable Gathering Ta...
Table Merge Has Completed Panel
Help
------------------------------------------------------------------------------
IVP Ta...
Global Update in Progress Panel
IVP Variable global change In Progress - DBT
Global update in progress for . . : IXUMRXB
P...
INSTALL/IVP Phase Selection #1 Panel
Help
------------------------------------------------------------------------------
I...
IVP Import function an Action Code in Variable Gathering
IVP Import
IVP Variable Gathering (LST Mode) - DBT .. Row 1 to 8 ...
When Imp action selected:
IVP Import - 2
IVP Export File Name
Command ===>
Enter the name of the IVP Export Dataset, then ...
IVP Import - 3
IVP Variable global change In Progress - DBT
Global update in progress for . . : IXUACBA
Please do not inte...
INSTALL/IVP Phase Selection #1 Panel
Help
------------------------------------------------------------------------------
I...
Variable Gathering (LST Mode) Panel
Help
-------------------------------------------------------------------------------
V...
Variable Gathering (ENT Mode) Panel
Help
---------------------------------------------------------------------------------...
--------------------------------------------------------------------------------------------------------------------------...
INSTALL/IVP Phase Selection #1 Panel
Help
------------------------------------------------------------------------------
I...
File Tailor ALL Request Panel
Help
_____________________________________________________________________________
File Tail...
File Tailoring in Progress Panel
File Tailoring in progress - DBT
File Tailoring Progress Indicator
Current Row . . . . . ...
FT ALL has completed Panel
Help
__________________________________________________________________________________
FT ALL ...
File Tailoring (LST Mode) Panel
Help
-------------------------------------------------------------------------------------...
FT Complete Verification Panel
Help
_____________________________________________________________________________
FT Compl...
INSTALL/IVP Phase Selection #1 Panel
Help
------------------------------------------------------------------------------
I...
Execution (LST Mode)
Help
-----------------------------------------------------------------------------------------------
...
Edit Job Panel
_________________________________________________________________________________
EDIT IMS.INSTALIB(IV3C202...
EX Complete Verification Panel
Help
________________________________________________________________________________
EX Co...
 The IVP Dialog process consists of multiple steps. First item for each step describes the step.
 The following lists al...
IVP 'A' Series
The items within the 'Ax' series of steps are used to perform
initialization for the IVP Dialog
There are ...
The "IVP" is an elaborate set of examples built around several sample
applications and several different types of executio...
The "Dx" series of EXAMPLES identify the JOBs and TASKs which the user
must perform in order to establish the interfaces b...
Honorable Mentions - Continued
•IV_D401T - TASK - IPL MVS with MLPA or CLPA OPTION
–Be sure to IPL with this CLPA to make...
The "Ex" series of steps identify the JOBs and TASKs which the user must perform in
order to prepare the sample applicatio...
The "Fx" series of steps identify the JOBs and TASKs which the user must
perform during the execution of the "DBB" (Batch)...
The "Hx" series of steps identify the JOBs and TASKs which the user must
perform during the execution of the "DBT" (DB/DC)...
IMS Migration
Considerations
Migration Considerations
57
Verify software and hardware requisites
•Program Directory
Migration/Coexistence maintenance
•REPORT MISSINGFIX (FIXC...
58
Upgrade RECONs
•CHANGE.RECON UPGRADE
– Can use CHECKUP
System definition (ALL)
ACBGEN
Possible changes to procedure...
59
Monitor changes in storage utilization (CSA/ECSA/PRIVATE/EPRIVATE)
• May need to adjust IMS pool sizes
• Take SVC dump...
60
Recommend initial migration be done without implementing optional new functions.
•Once stable in production then take ...
61
SECURITY macro removed from SYSGEN (V13)
•Parms in DFSPBxxx and DFSDCxxx
•Exits DFSCSGN0, DFSCTRN0, DFSCTSE0 no longer...
62
 Database Versioning
• If migrating an IMS system that uses database versioning to IMS 14, you must preserve
in the ca...
63
 HALDB Support for 8G OSAM
• All IMS systems must be at IMS 14 or later and the MINVERS value in the RECON data
set mu...
64
 APPC/IMS Flood Control
• In IMS 14, the new APPC/IMS flood control function is active by default and the IMS
system w...
65
 OTMA
• Dynamic Storage for OTMA Descriptors
– In IMS 14, the value that is displayed in the error messages DFS2384W a...
66
CQS (Shared Queues)
•IMS V14 cannot register with a pre IMS V14 CQS
•IMS V13 cannot register with a pre IMS V13 CQS
•I...
67
Database Recovery Utilities
• IMS V14 Database Recovery utility (DFSURDB0) and Database
Change Accumulation utility (D...
68
Fallback
A system may fallback to a previous release after upgrade
• Upgraded RECONs are used
• Additional considerati...
69
The following SVC's are used by IMS
• T2 DFSVC200 (IGCxxx)
–Downward compatible. Can use the one from the highest leve...
70
IMS Utility DFSUSVC0 can be used to update both the IMS T2 and IMS T4 SVC
dynamically
• Lasts for the life of the IPL
...
71
 IMS 14 is the last version of IMS to support Remote Site Recovery (RSR).
 IMS 14 systems and later do not support th...
72
 IMS 14 is the last version of IMS to support the IMS Connect LOCAL option for
connections between IMS Connect and IMS...
73
Contact the IMS Level 2 for assistance
•We are here to help and your success is our reason for being
Migration/Install...
IMS Definition
IMS Definition
The direction of the IMS product is the eventual removal of SYSGEN
•IMS V10 introduced Dynamic Resource Definition (DRD)
...
 IMS SYSGEN consists of multiple phases which are as follows:
Coding of the IMS macros which will define the system (sta...
 The level of SYSGEN are specified in the 'SYSTEM' keyword of the
'IMSCTRL' macro
 The following illustrates the differe...
MODBLKS
MODBLKS Level SYSGEN
 Generates control blocks
members for resources to
be added online using
online change (e.g....
MODBLKS
CTLBLKS Level SYSGEN
CTLBLKS
Generates modules for all
IMS control blocks
Normally done to define
network defini...
MODBLKS
NUCLEUS Level SYSGEN
CTLBLKS
Generates an IMS nucleus
for the control region
Also used to create a new
IMS nucle...
MODBLKS
ON-LINE Level SYSGEN
CTLBLKS
Generates all modules
and procedures needed
for the online environment
NUCLEUS
ON-LI...
BATCH Level SYSGEN
BATCH
Generates modules and
procedures needed to
build a complete batch
system
MODBLKS
ALL Level SYSGEN
CTLBLKS
NUCLEUS
ON-LINE
BATCH
ALL
Must be done during initial installation
MSVERIFY Level SYSGEN
Builds blocks for the MSC Verification Utility
•Unique in that not used to build for a running syst...
 In addition to being required for LGEN, the preprocessor can be
used to verify the system definition
• The following are...
 Two types of systems can be configured which will
determine how stage 1 is run
 Standard System
 LGEN System
–Strictly...
The stage 2 jobs must be run in the order created
Recommend using ONEJOB parm on IMSGEN macro
Return code of '0' is exp...
 JCLIN pointing to the target zone should be run after every
Sysgen for libraries maintained by SMP/E
• The SMP/E target ...
 IMS V10 introduces Dynamic Resource Definition (DRD)
• Usage is optional
–Manages same resources as could be managed by ...
 Dynamic Resource Definition (DRD)
•DRD and Online Change mutually exclusive
•PROCLIB member specification MODBLKS=DYN to...
 Dynamic Resource Definition (DRD)
–Changes made online are logged to retained across warm start
–Changes can be exported...
 To enable your IMS to use DRD (from System Definition Guide):
• Shut down IMS normally.
• Change MODBLKS=OLC to MODBLKS=...
• Cold start IMS, specifying DFSDF=xxx in the control region execution
parameters
– xxx identifies the suffix of the DFSDF...
 The IMS Repository can be used to store DRD definitions instead of RDDS
 Next step in the evolution of DRD
 Enables mu...
 Focus is on improving the systems management and resource management
aspects of handling IMS resource definitions
• For ...
• Consolidation of resource definitions in a single place
• DRD definitions are the initial implementation of the IMS repo...
Repository Function Usage
IMS 12 and above, the resource and descriptor definitions for Dynamic
Resource Definition (DRD)...
Repository Support for DRD Function
DRD users in IMS 11 moving to IMS 12 or above
•Can use existing RDDSs from IMS 11 for...
Repository Population
Rep
MODBLKS
Utility
Utility
RDDS
Direct from MODBLKS
IMS
Temp RDDS
Export command
RM
Direct from RDDS
Repository Components - 1
A Common Service Layer (CSL) IMSplex configuration consists of:
•Operations Manager (OM)
–Used ...
Repository Components - 2
•Structured Call Interface (SCI)
–Used for communications within the CSL
–Not used for communica...
Repository Components - 3
•Batch utilities
–Batch ADMIN utility (FRPBATCH)
Commands for managing IMSRSC repositories
Fun...
Repository Migration Overview
From DRD with RDDSs to DRD with Repository
•Create non-system RDDS that contains current de...
Repository Architecture
Operations
Manager
(OM)
IMS
Control
Region
Repository
Server
(RS)
SCI
SCI
X
C
F
X
C
F
RS Catalog R...
General IMS Maintenance
Recommendation
General IMS Maintenance Recommendation
106
This general product maintenance recommendation provides guidelines
that when implemented are intended to produce a m...
The following are factors that cause system Integrity/Stability issues:
•Yet to be discovered code defect
–Simulate produ...
108
The general IMS maintenance recommendation for an IMS production system:
Initial IMS production system base implemen...
 Ongoing IMS production system service level
 Fully tested fixes for significant** software problems encountered
 Fully...
 PTF-in-error (PE) – Designation assigned to PTF’s that were
provided to correct a problem but have either not corrected ...
 All APARs that address issues containing one or more of the following conditions
are marked HIPER:
 Causes an IPL or re...
 It is recommended that Enhanced HOLDDATA be used to identify exposures to
HIPER and PE PTF's
• Ensure that a current cop...
 ++HOLD statements for PE, HIPER and FIXCAT
Downloadable and provided with install/service orders
The ‘full.txt’ or ‘fu...
The following shows an example of a job that can be used to download and
RECEIVE a current copy of the Enhanced Holddata:
...
IBM maintains a Security Portal that contains information on Security or Integrity fixes
IBM treats information about Se...
 On the Security Portal Web site IBM provides:
•The current ASSIGN file to enable system programmers to install
security/...
Expand Security/Integrity HOLDDATA statements
++ HOLD (HDB9910) FMID(HDB9910) REASON(AM11111) ERROR
DATE(14364) COMMENT(S...
Perform risk assessment on processed PE'd PTFs for which the
system is susceptible
Courses of action can include:
–Remov...
 Each UPGRADE level includes SUBSET entries for each IMS FMID within that release. The
SUBSET for each installed FMID nee...
120
IMS release 14.1 UPGRADE name = IMS1400
 The SUBSET names (IMS related FMIDs):
CHG/INDEX HMK1400 JMK1401 JMK1402
JMK...
121
IMS release 13.1 UPGRADE name = IMS1300
 The SUBSET names (IMS related FMIDs):
CHG/INDEX HMK1300 JMK1301 JMK1302
JMK...
122
Goal: Enhance the way service is tested and delivered for z/OS, by
providing a single coordinated service recommendat...
123
Consolidated Service Test - 2
All APARS included regardless of severity
Testing of quarterly RSUs:
Three 30-day tes...
Consolidated Service Test - 3
Quarterly CST reports available consisting of:
CST hardware environment
Software environm...
125
RSU Contents
Quarterly
RSU1512
– Available January 2016
All service through the end of September 2015 not already m...
Achieving IMS Maintenance Recommendation
 Current IMS Maintenance Upgrade Technique
 Obtain current service using ShopzS...
Achieving IMS Maintenance Recommendation -
Cont.
 Caution: SYSMODs in APPLY status may be regressed by SYSGEN
–Either ACC...
IMS service can be processed using the standard SMP/E RECEIVE,
APPLY, ACCEPT processing
OR
SMP/E RECEIVE, 'ACCEPT BYPASS(A...
129
 z/OS Release 10 and SMP/E Release 3.5 introduce FIXCAT HOLDDATA to simplify identifying
required service from PSP bu...
130
 Fixcat -2
•IBM.TargetSystem-RequiredService.IMS.V10
Fixes required on other IBM products to allow them to run with ...
131
 The following are the z/OS software based FIXCAT categories supported by IMS:
•Category: IBM.TargetSystem-RequiredSe...
132
 Examples of non IMS specific categories
•IBM.ProductInstall-RequiredService
–HIPER
•IBM.Coexistence.z/OS.V2R2
•IBM.F...
133
 The following is an example of the REPORT MISSINGFIX command
which can be used to determine which service is needed ...
Hints and Tips for Successful
Implementation and Maintenance
of IMS
Hints & Tips
SMP/E GENERATE command
• Used to create JCL to build elements in target libraries from elements in distribution libraries...
 User Exit Packaging
• Optional user exits now in SDFSSMPL
• User exits created as ++SRC type part
• Allows line updates ...
DBRC for batch no longer specified in SYSGEN
•Default for DBRC in batch and utility regions is YES
•Module DFSIDEF0 can b...
The following is an for an SMP/E USERMOD for DFSIDEF0:
++ USERMOD (XYZUMOD) .
++ VER (P115)
FMID(HMK1400) .
++ JCLIN.
//IN...
139
The IMS Application Menu (DFSAPPL) can be used to invoke the growing number of IMS ISPF
applications
–EX 'IMS.SDFSEXE...
140
The IMS Interactive Dump formatter uses IPCS to format IMS Control blocks
 REXX EXEC DFSDFSRT is provided in IMS V9 a...
141
When DFSDFSRT is invoked under ISPF and the IPCS environment is not set up the
following type of messages will be enco...
142
Recommend running with at a minimum the following IMS internal traces:
•DL/I
•LOCK
•SCHD
•DISP
Recommend setting up ...
143
 The prefix name for APARs is now 'PI' (was ‘PM’)
 UI for PTF's (was ‘UK’)
 One APAR may result in multiple SYSMODS...
144
 The name of the APAR fix available on DLL/IBMLINK will vary
depending on the IMS release as follows:
• PIxxxxxz
– PI...
 The naming conventions for USERMODs will vary depending on the type of
USERMOD as follows:
 Fixtest for an APAR
–FIxxxx...
The naming conventions of the sysmod for usermods will vary
depending on the type of usermod as follows:
 Fixtest and re...
Always download and RECEIVE current Enhanced
HOLDDATA prior to SMP/E processing
•For complete descriptive information rel...
 Considerations
 Zone setup
–How to Implement Preventative Service
–SYSGENS when systems contain different levels of
ser...
 The simplest way to set up SMP/E is:
One TLIB, DLIB and set of datasets for each IMS system
– Easiest for the human to ...
 A second method is:
One TLIB Zone For Each IMS - Common DLIB Zone
–Service can be applied to each system selectively
–A...
 A third method is:
One DLIB and TLIB Zone for many systems
–Implement to all systems at one time or manage outside of
S...
 SMP/E APPLY encounters one of the following
warning messages:
GIM43401W aaaaaaaa bbbbbbbb IN SYSMOD cccccccc
WAS NOT IN...
IMS APARs and USERMODs prior to IMS V14 only PRE SYSMODS with
code dependencies. The PRE will specify the APAR as opposed...
 Determine if regression will actually take place by doing the following:
Look at the prereq on the sysmod, determine if...
Acknowledgements and Disclaimers
Availability. References in this presentation to IBM products, programs, or services do n...
Thank You
Prochain SlideShare
Chargement dans…5
×

IMS installation workshop

2 458 vues

Publié le

IMS Customer Internship held in San Jose, CA in April 2016.
By John Butterweck

Review IMS packaging, Installation and IVP dialog process for IMS

IMS migration considerations

Review and explain IMS maintenance recommendations

Publié dans : Technologie
  • Login to see the comments

IMS installation workshop

  1. 1. IMS Installation Workshop Presentations IBM SILICON VALLEY LABORATORY IMS SOFTWARE SERVICE DELIVERY 555 BAILEY AVENUE SAN JOSE, CALIFORNIA 95141
  2. 2.  The objectives this workshop are:  Review IMS packaging, Installation and IVP dialog process for IMS  Discuss IMS migration considerations  Discuss IMS Definition  Review and explain IMS maintenance recommendations  Hints & Tips for successful implementation and maintenance of IMS systems  IMS Installation Lab  Questions are good. We all learn from them so don’t hold back Introduction
  3. 3. IMS Packaging IMS Packaging
  4. 4. 4 Packaging • No major changes in packaging since IMS 8.1 • Installation via CBPDO, ServerPac or CustomPac • All FMIDs are installed using SMP/E RECEIVE, APPLY, ACCEPT –Conform to packaging standards –Results in multiple SMP/E messages indicating no target library for parts defined by SYSGEN Program Directory contains message id's –Sample jobs provided will process service as well as FMIDs Packaging
  5. 5. 5 Job to allocate target and distribution libraries split up into two jobs • DFSALOC1 – Allocate target and distribution libraries • DFSALOC2 – Allocate target and distribution libraries for IMS Java On Demand feature IMS target and distribution libraries (except SDFSRESL) delivered as PDSEs • Can be either PDSE or PDS IMS Classic Java APIs no longer supported. • Migrate to the IMS Universal JDBC Driver Minor changes in IMS IVP dialog • Renumbering of IVP Phase selection – Variable Export utility now option ‘1’ (was ‘A’) • IMS Version removed from some IVP panels • Some variables whose default value contained release number changed to have ‘XX’ as opposed to release – IVPXXCR1 for name of control region as opposed to IVP13CR1 • The PDFs versions of the IMS V14 library can be found at: – http://www-01.ibm.com/support/docview.wss?uid=swg27046437 V14 Changes
  6. 6. 6 Only IRLM 2.3 (FMID HIR2230) provided •Works with all supported releases of IMS  IVP Dialog Changes – V13  Variables added which are used to build proclib member HWSCFGxx for ISC link  The PDFs versions of the IMS V13 library can be found at: –http://www-01.ibm.com/support/docview.wss?uid=swg27038236 V13 Changes
  7. 7. 7 SMP/E Processing •Always RECEIVE current Enhanced HOLDDATA prior to SMP/E processing –For complete descriptive information relating to Enhanced Holddata see Internet address: http://service.boulder.ibm.com/390holddata.html •Be sure to resolve PE's during processing • Contact the IBM Support Center for assistance as needed SMP/E Processing
  8. 8. Installation Installation
  9. 9.  The IMS product can be distributed by a variety of methods. Which are as follows: CBPDO - DBS Feature distribution tapes SERVERPAC - DBS Feature pre-built SMP/E, DLIBs and TLIBs SYSTEMPAC – DBS Feature may be customized ShopZseries delivery schedules can be found at the following: https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp?action=glcrad Distribution Media
  10. 10.  Installation Documentation Precedence •Documentation provided with CBPDO, ServerPac, etc. •PSP Bucket • Contains the latest information •Program Directory •IMS Installation Documentation Precedence
  11. 11.  The following is a list of the SMP/E Setup and SMP/E sample jobs provided:  DFSALA - Allocate and initialize new CSI datasets (optional but recommended)  DFSALB - Initialize SMP/E zones allocated (optional but recommended) – Ensure ACCJCLIN is specified in DLIB zone before processing FMIDs  RECEIVE - Receive job provided by CBPDO – Program Directory contains instructions for obtaining the JCL  DFSALOC1 - Allocate target and distribution libraries  DFSALOC2 – Allocate target and distribution libraries for On Demand Feature  DFSZFSAL – Allocate a ZFS file system (optional)  DFSJSMKD - Invoke DFSJMKDR EXEC to allocate (mkdir) ZFS/HFS paths for IMS On Demand feature  DFSDDEF1 - Define SMP/E DDDEFs for core IMS  DFSDDEF2 - Define SMP/E DDDEFs for IMS On Demand  DFSAPPLY - SMP/E APPLY of FMID's and service – Be sure to resolve PE's  DFSACCEP - SMP/E ACCEPT of FMID's and service – Be sure to resolve PE's SMP/E Setup and SMP/E Jobs (CBPDO)
  12. 12. Optional jobs provided to install IMS in its own unique SMP/E environment (GLOBAL Zone) • DFSALA - Allocate and initialize new CSI • DFSALB - Initialize CSI zones, allocate SMP/E datasets, build DDDEF entries for SMP/E Recommend using these jobs • If these jobs are NOT used, be sure ACCJCLIN is set in the IMS distribution zone prior to ACCEPT processing –ACCJCLIN is set in sample job DFSALB –SMP/E OPTION and UTILITY entries added in sample job DFSALB Optional Sample Jobs (CBPDO)
  13. 13.  JCL provided in Program Directory to unload sample jobs to perform SMP/E processing and setup  Each job contains instructions for customization  Same variables in multiple jobs so may want to save in a separate file to use copy and paste – C #globalcsi IMS.V14.GLOBAL.CSI all – C targlib IMS14T all SMP/E Setup and SMP/E Jobs (CBPDO)
  14. 14. 14 The following is an example of the instructions for customization of the sample jobs: //* NOTES: */ //* 1) REVIEW THE SMP CONTROL STATEMENTS BEFORE SUBMITTING */ //* THIS JOB. */ //* 2) ADD A JOB CARD TO MEET YOUR SYSTEM'S REQUIREMENTS. */ //* 3) CHANGE #globalcsi TO THE DATASET NAME OF YOUR GLOBAL */ //* CSI DATA SET. */ //* 4) CHANGE targlib TO THE NAME OF YOUR TARGET ZONE. */ //* 5) REMOVE THOSE FMIDs THAT YOU DO NOT WISH TO APPLY FROM */ //* THE SELECT AND FORFMID OPERANDS OF THE APPLY STATEMENT. */ //* HMK1400 <======= FMID to be installed */ //* HIR2230 <======= FMID to be installed */ //* JMK1401 <======= FMID to be installed */ //* JMK1402 <======= FMID to be installed */ //* JMK1403 <======= FMID to be installed */ //* JMK1404 <======= FMID to be installed */ //* JMK1405 <======= FMID to be installed */ //* JMK1406 <======= FMID to be installed */ NOTE - The lower case characters. Be sure to specify 'CAPS ON' as appropriate path names need to be in lower case characters Sample Installation Job Customization (CBPDO)
  15. 15. IMS IVP Dialog IMS IVP Dialog
  16. 16.  The following are input datasets used by the IVP dialog: IMS.SDFSISRC - Contains sample application and miscellaneous source IMS.SDFSCLST - Contains TSO clists IMS.SDFSEXEC - Contains REXX execs IMS.SDFSMLIB - Contains ISPF message members IMS.SDFSPLIB - Contains ISPF panels IMS.SDFSSLIB - Contains ISPF file tailoring skeletons IMS.SDFSTLIB - Contains ISPF table members IMS.SDFSRTRM - Contains description members used by the IMS IVP dialog Note: These datasets are used by multiple IMS ISPF applications (e.g. SPOC, HALDB dialog, IMS dump formatter, etc.) The IVP Dialog Input Datasets
  17. 17.  The following are output datasets used by the IVP dialog:  IMS.INSTALIB - JCL for the jobs to be run  IMS.INSTATBL - ISPF tables used to keep track of customized variables  IMS.SDFSISRC – Sample customized in file tailoring phase based on options selected  ISPPROF - ISPF profile dataset The IVP Dialog Output Datasets
  18. 18. 18 EX 'IMS.SDFSEXEC(DFSIVPEX)' 'HLQ(IMS)' IVP Export IVP Variable Export Utility Command ===> Enter the following information, then press enter. _ 1. Select the IVP Environment 1. DBB - Database Management (Batch) 2. DBC - Database Management (DBCTL) 3. DBT - Database and Transaction Management (DB/DC) 4. XRF - DB/DC with Extended Recovery Facility (DB/DC with XRF) 5. DCC - Transaction Management (DCCTL) 2. Specify the IVP High Level Qualifier (IVP) of the INSTATBL dataset IMS13 ___________________________ 3. Specify the Export Dataset. (If the dataset does not exist, you will be prompted to create the dataset) 'IMS13.EXPORT'_____________________________________________
  19. 19. 19 Exported dataset can be modified using ISPF to change variables in mass • Can use ISPF edit command for example to change all occurrences of 13 to 14: C 13 14 all –Example of data from an EXPORT: <var>IXUUTLHQ</var> <val>IVPUTL14</val> <var>IXUEXEHQ</var> <val>IVPEXE14</val> <var>IXUSYSHQ</var> <val>IMS14.DBDC</val> <var>IXUDLBHQ</var> <val>IMS14.DBDC</val> <var>IXUSMPHQ</var> <val>IVPSMP14</val> <var>IXURLMHQ</var> <val>IVPRLM14</val> Can export variables from IMS V6 thru current IVP Export - cont.
  20. 20.  The IVP dialog is started by issuing the following command from ISPF option 6: • EX 'IMS.SDFSCLST(DFSIXC01)' 'HLQIV(iii) HLQDL(hhh) HLQSY(sss)’ –iii - High level qualifier for IVP output datasets –hhh - High level qualifier for IMS distribution library datasets –sss - High level qualifier for IMS system datasets –The clist parm of 'DEBUG' is available –Help is available for all panels by pressing 'PF1' –Parm 'HLQ' can be used to identify high level qualifier for IVP, system and distribution libraries EX 'IMS.SDFSCLST(DFSIXC01)' 'HLQ(IMS)' Invoking the IVP Dialog
  21. 21. When the dialog is started for the first time for each release the following type of panel will be displayed: ==== === === ==== == ==== ==== ==== ======== == ==== ==== === == == ===== ===== === == == ===== == === == == === == == === ==== === === === ========= ==== === = === == ===== Information Management System (IMS) IVP Dialog for IMS Version 14.1 ENTER to continue or END to exit Logo Panel
  22. 22. Copyright Panel Information Management System (IMS) Version 14.1 Licensed Materials - Property of IBM "Restricted Materials of IBM" 5635-A05 Copyright IBM Corp. 1974, 2014 All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP schedule contract with IBM Corp.
  23. 23.  Select the highest number representing the system you wish to install  The option selected will be used in determining the names for members to be placed in IMS.INSTALIB Initial Installation Environment Options Panel Help ------------------------------------------------------------------------------ IVP IVP Environment Options Command ===> Select the desired option and press Enter. Option . . 3 IVP Environments 1. DBB - Database Management (Batch) 2. DBC - Database Management (DBCTL) 3. DBT - Database and Transaction Management (DB/DC) 4. XRF - DB/DC with Extended Recovery Facility (DB/DC with XRF) 5. DCC - Transaction Management (DCCTL)
  24. 24. Help ------------------------------------------------------------------------------ IVP Sub-Option Selection - DBT Command ===> Select the desired Sub-Options and press ENTER /IRLM - Use IRLM in IVP Applications /FP - Use Fast Path in IVP Applications /ETO - Use Extended Terminal Option /CQS - Add CQS to CSL Applications RACF - Use RACF Security JAVA - Use JAVA Applications and Open Database PRA - Use Parallel RECON Access ICON - Use IMS Connect REPO – Use IMSRSC Repository COUT – Use CALLOUT Applications Note: Your Sub-Option selection affects the user variables, jobs, and tasks that will be presented. If you later change your selection, you must redo the IVP Table Merge, Variable Gathering, File Tailoring, and Execution processes. RACF is required when Java sub-option is selected. •Defaults for all but IRLM, FP and ETO are not selected Sub - Option Selection Panel
  25. 25. Sub - Option Change Verification Panel Help ------------------------------------------------------------------------------ Sub-Option Change Verification - DBT Command ===> The Sub-Options you have just chosen are not the same as the Sub-Options which were last active. If you change Sub-Options, Table Merge and the three Dialog Phases must be re-run from the beginning. From To Y Y - FP - Use Fast Path in IVP Applications (not available for DCCTL) Y Y - ETO - Use ETO (not available for Batch and DBCTL) N Y - CQS - Add CQS Applications (not available for Batch and DBCTL) N N - RACF - Use RACF Security (not available for Batch) N N - JAVA - Use JAVA Applications and Open Database N N - PRA - Use Parallel RECON Access (not available for Batch) N N - ICON - Use IMS Connect N N - REPO - Use IMS Repository N N - COUT - Use Callout Applications To confirm your change of Sub-Options: Press ENTER To return to the Sub-Option Selection menu: Press END  This panel appears because CQS was changed from the default of 'N' (no '/') to 'Y' on the previous panel
  26. 26. Table Merge Request Panel Help ------------------------------------------------------------------------------ IVP Table Merge Request - DBT Command ===> The IVP Dialog is driven from a set of ISPF tables which contain information about the variables, JOBs, TASKs and sequence of presentation you will need to perform the verifications. Since the tables will be updated by the dialog, working copies must be made the first time you use the dialog. If service is applied to your IMS system, or if you decide to use the IVP dialog to build a different environment, then either the existing copies must be updated or new copies created. Please indicate whether you wish to perform Table Merge/Create: 1 1. YES - Create / Update working tables from master tables. 2. NO - Use existing tables.
  27. 27. VG Table Merge in Progress Panel IVP VG Table Merge In Progress - DBT Table Merge Progress Indicator Variable Gathering Table . . : DFSIXBV3 Current Row . . . . . . . : IXULESPC Percent completed . . . . : 24 File Tailoring Table . . . . : DFSIXBF3 Current Row . . . . . . . : Patience Percent completed . . . . : 000 Execution Table . . . . . . : DFSIXBE3 Current Row . . . . . . . : Patience Percent completed . . . . : 000 Please do not interrupt this process.
  28. 28. Table Merge Has Completed Panel Help ------------------------------------------------------------------------------ IVP Table Merge has completed - DBT Command ===> The Table Merge process has completed and the Phase Complete flags have been turned off for all phases. If Table Merge has just been performed for the first time for this option, then the resetting of Phase Complete flags is of no special interest. If Table Merge has been performed for some other reason, then the resetting of Phase Complete flags will force you to revisit each of the phases in sequence (Variable Gathering, File Tailoring, and Execution). Make use of this opportunity to examine the tables for changes (the "!" indicator will be set in the action field for items which have been added or changed by service). Your position in each phase has been retained so that you may return to your last position after you have browsed for changes. Press ENTER to continue.
  29. 29. Global Update in Progress Panel IVP Variable global change In Progress - DBT Global update in progress for . . : IXUMRXB Please do not interrupt this process.
  30. 30. INSTALL/IVP Phase Selection #1 Panel Help ------------------------------------------------------------------------------ IVP IVP Phase Selection - DBT Command ===> Select the desired Phase and positioning option and press ENTER 2 1. Variable Export Utility (Export variables to a data set) VG - Variable Gathering - (Define user values for variables) 2. VG1 Start/Restart from the beginning of the phase 3. VG2 Start/Restart from the last known position within the phase FT - File Tailoring - (Create customized INSTALIB members) 4. FT1 Start/Restart from the beginning of the phase 5. FT2 Start/Restart from the last known position within the phase 6. FT3 Start/Restart from the beginning of a selected step EX - Execution - (Run the IVP jobs) 7. EX1 Start/Restart from the beginning of the phase 8. EX2 Start/Restart from the last known position within the phase 9. EX3 Start/Restart from the beginning of a selected step
  31. 31. IVP Import function an Action Code in Variable Gathering IVP Import IVP Variable Gathering (LST Mode) - DBT .. Row 1 to 8 of 222 Command ===> Scroll ===> CSR Action Codes: Chg Doc eNt Rfr Imp Exp -- CHG is default if item modified Variable = Value.................................................. Var-Title...................................................... I IXUIVPHQ = IMS IVP - High level DSNAME qualifier for IVP (IVP) data sets ! IXURLMHQ = IVPRLM13 IVP - High level DSNAME qualifier for IRLM (RLM) data sets * IXUDLBHQ = IMS IVP - High level DSNAME qualifier for IMS DLIB (DLB) data sets * IXUSYSHQ = IMS IVP - High level DSNAME qualifier for IMS System (SYS) data sets ! IXUEXEHQ = IVPEXE13 •Imports ALL variables from an exported dataset
  32. 32. When Imp action selected: IVP Import - 2 IVP Export File Name Command ===> Enter the name of the IVP Export Dataset, then press enter: Export Dataset: 'IMS13.EXPORT'____________________________________________ Provide the name of the previously exported dataset and press ENTER
  33. 33. IVP Import - 3 IVP Variable global change In Progress - DBT Global update in progress for . . : IXUACBA Please do not interrupt this process.
  34. 34. INSTALL/IVP Phase Selection #1 Panel Help ------------------------------------------------------------------------------ IVP Phase Selection - DBT Command ===> Select the desired Phase and positioning option and press ENTER 2 1. Variable Export Utility (Export variables to a data set) VG - Variable Gathering - (Define user values for variables) 2. VG1 Start/Restart from the beginning of the phase 3. VG2 Start/Restart from the last known position within the phase FT - File Tailoring - (Create customized INSTALIB members) 4. FT1 Start/Restart from the beginning of the phase 5. FT2 Start/Restart from the last known position within the phase 6. FT3 Start/Restart from the beginning of a selected step EX - Execution - (Run the IVP jobs) 7. EX1 Start/Restart from the beginning of the phase 8. EX2 Start/Restart from the last known position within the phase 9. EX3 Start/Restart from the beginning of a selected step
  35. 35. Variable Gathering (LST Mode) Panel Help ------------------------------------------------------------------------------- Variable Gathering (LST Mode) - DBT . Row 1 to 11 of 222 Command ===> Scroll ===> CSR Action Codes: Chg Doc eNt Rfr Imp Exp -- CHG is default if item modified Variable = Value.................................................. Var-Title...................................................... * IXUIVPHQ = IMS IVP - High level DSNAME qualifier for IVP (IVP) data sets IXURLMHQ = IVPRLM13 IVP - High level DSNAME qualifier for IRLM (RLM) data sets * IXUDLBHQ = IMS IVP - High level DSNAME qualifier for IMS DLIB (DLB) data sets * IXUSYSHQ = IMS IVP - High level DSNAME qualifier for IMS System (SYS) data sets N IXUEXEHQ = IVPEXE13 IVP - High level DSNAME qualifier for Execution (EXE) data sets IXUUTLHQ = IVPUTL13 IVP - High level DSNAME qualifier for Utility (UTL) data sets IXUVSMHQ = IVPVSM13 IVP - High level DSNAME qualifier for VSAM (VSM) data sets IXUSSCLS =
  36. 36. Variable Gathering (ENT Mode) Panel Help --------------------------------------------------------------------------------------- Variable Gathering (ENT Mode) - DBT Command ===> Scroll ===> PAGE Action. . . . ! Select one of: Chg Doc Lst Nxt Prv Rfr Imp Exp Name. . . . : IXUEXEHQ User Value. . IVPEXE13 Title . . . : IVP - HIGH LEVEL DSNAME QUALIFIER FOR EXECUTION (EXE) DATA SETS Blank-OK. . : N HLQ-Group . : VOL-Group . : BLK-Group . : -------------------------------------------------------------------------------- ********************************* Top of Data ********************************** This variable specifies the high level DSNAME qualifier (HLQ) to be used when allocating and referencing IMS Execution data sets. This grouping of user data sets includes: o PGMLIB, DBDLIB, QBLKS, DFSOLP00, DFSWADS0, ... Data sets associated with this HLQ variable belong to the "EXE" group. If this variable is changed, then the HLQ variables for ALL data sets belonging to this group will be changed accordingly. Although these data sets are covered by one DSNAME prefix, they are logically divided into two subgroups for allocation. Each of the subgroups occupies approximately the same amount of dasd space (at default values).  Press ENTER to remove box  PF3 to get back to Variable Gathering Lst Mode  PF3 again to get out of Variable Gathering
  37. 37. --------------------------------------------------------------------------------------------------------------------------------------- VG Complete Verification - DBT Command ===> You have just ENDed the Variable Gathering Phase of the IVP dialog. If you have completed your customization of the dialog variables, you may set the Variable Gathering Complete flag and proceed to the File Tailoring Phase. You may return to Variable Gathering at any time. If you have not completed your customization of the dialog variables, you should return to the Variable Gathering Phase. If Variable Gathering is complete: Press ENTER If Variable Gathering is NOT complete: Press END NOTE: After the phase complete flag has been set, this panel will no longer be di |---------------------------------------------------------------| enfor | DFSIX029: DFSIXX08 - Variable Gathering Phase ended for "DBT" | The p |---------------------------------------------------------------|  Press ENTER VG Complete Verification Panel
  38. 38. INSTALL/IVP Phase Selection #1 Panel Help ------------------------------------------------------------------------------ IVP Phase Selection - DBT Command ===> Select the desired Phase and positioning option and press ENTER 4 1. Variable Export Utility (Export variables to a data set) VG - Variable Gathering - (Define user values for variables) 2. VG1 Start/Restart from the beginning of the phase 3. VG2 Start/Restart from the last known position within the phase FT - File Tailoring - (Create customized INSTALIB members) 4. FT1 Start/Restart from the beginning of the phase 5. FT2 Start/Restart from the last known position within the phase 6. FT3 Start/Restart from the beginning of a selected step EX - Execution - (Run the IVP jobs) 7. EX1 Start/Restart from the beginning of the phase 8. EX2 Start/Restart from the last known position within the phase 9. EX3 Start/Restart from the beginning of a selected step
  39. 39. File Tailor ALL Request Panel Help _____________________________________________________________________________ File Tailor ALL Request - DBT Command ===> You are entering the File Tailoring Phase. For one of the following reasons, the File Tailoring Complete flag is not set: o You are entering File Tailoring for the first time. o You are re-entering File Tailoring and you did not cause the File Tailoring Complete flag to be set when you last exited this Phase. o The File Tailoring Complete flag was reset by Table Merge. If you wish, File Tailoring will be performed for ALL JOBs at this time. Please select one of the following: 1 1. YES - Perform the ALL action before going to File Tailoring 2. NO - Go directly to the File Tailoring Panels NOTE: YES is recommended the first time you enter File Tailoring for an Option and any time service is applied.
  40. 40. File Tailoring in Progress Panel File Tailoring in progress - DBT File Tailoring Progress Indicator Current Row . . . . . : IV3C201T Percent completed . . : 1 Please do not interrupt this process.
  41. 41. FT ALL has completed Panel Help __________________________________________________________________________________ FT ALL has completed - DBT Command ===> File Tailoring has completed the ALL action for members used by the DBT IVP option. * If you requested the ALL action upon entry to the File Tailoring Phase, then members were processed beginning at the top of the File Tailoring Table. * If you requested the ALL action on one of the File Tailoring panels, then members were processed from the point of request to the end of the File Tailoring Table. When you leave this panel, you will be returned to the File Tailoring LST MODE panel. The File Tailoring panels may be used at a later time to individually re-run file tailoring for one or more members. Press ENTER to continue
  42. 42. File Tailoring (LST Mode) Panel Help ----------------------------------------------------------------------------------------- File Tailoring (LST Mode) - DBT Row 1 to 23 of 533 Command ===> Scroll ===> CSR Action Codes: All brM brS Doc Edm eNt Ftl Member.. Skeleton Step Title......................................... IV3A001T IVPA001T A0 NOTE - Introduction - Dialog Set-up * IV3A301N DFSIXSA4 A3 CLIST - Offline Formatted Dump - IVP1/2/3/4 * IV3A302N DFSIXSA5 A3 CLIST - Offline Dump Formatter - BATCH * IV3A303N DFSIXSA6 A3 CNTRL - MSDB Load Cntrl Stmts - DBFSAMD1/DBFSA IV3C001T IVPC001T C0 NOTE - Introduction - System Definition * IV3C101J DFSIXSC0 C1 JOB - Alloc SYSDEF Data Sets * IV3C105J DFSIXSC6 C1 JOB - Assembly/Bind RACF Security Exits * IV3C201T DFSIXSC1 C2 TASK - Browse the STAGE1 Source Deck * IV3C202J DFSIXSC2 C2 JOB - Run SYSDEF Preprocessor * IV3C203J DFSIXSC3 C2 JOB - Run SYSDEF STAGE1 * IV3C301J DFSIXSC4 C3 JOB - Run SYSDEF STAGE2 >>> SEE DESCRIPT * IV3C401J DFSIXSC5 C4 JOB - Run SMP/E JCLIN IV3C405T IVPC405T C4 TASK - Edit IMS PROCLIB Members IV3D001T IVPD001T D0 NOTE - Introduction - z/OS and VTAM Interface * IV3D101T DFSIXSD0 D1 XMPL - Allocate Interface Data Sets * IV3D102T DFSIXSBI D1 XMPL - Allocate Sharing Control Data Sets (SHC * IV3D200T DFSIXSD1 D2 XMPL - Update JESx Procedure * IV3D201T DFSIXSD3 D2 XMPL - Update IEAAPFxx or PROGxx - Authorized * IV3D202T DFSIXSD4 D2 XMPL - Update IEALPAxx - MLPA Modules  Do not use 'Edm' from File Tailoring phase  PF3 to get out of File Tailoring
  43. 43. FT Complete Verification Panel Help _____________________________________________________________________________ FT Complete Verification - DBT Command ===> You have just ENDed the File Tailoring Phase of the IVP dialog. If you have completed your customization of the dialog jobs, you may set the File Tailoring Complete flag and proceed to the Execution Phase. You may return to File Tailoring at any time. If you have not completed your customization of the dialog jobs, you should return to the File Tailoring Phase. If File Tailoring is complete: Press ENTER If File Tailoring is NOT complete: Press END NOTE: After the phase complete flag has been set, this panel will no longer be displayed and the phase execution sequence for this phase will not be enforced. The phase complete flags are reset by re-running Table Merge. ------------------------------------------------------------- | DFSIX033: DFSIXX09 - File Tailoring Phase ended for "DBT" | -------------------------------------------------------------
  44. 44. INSTALL/IVP Phase Selection #1 Panel Help ------------------------------------------------------------------------------ IVP Phase Selection - DBT Command ===> Select the desired Phase and positioning option and press ENTER 7 1. Variable Export Utility (Export variables to a data set) VG - Variable Gathering - (Define user values for variables) 2. VG1 Start/Restart from the beginning of the phase 3. VG2 Start/Restart from the last known position within the phase FT - File Tailoring - (Create customized INSTALIB members) 4. FT1 Start/Restart from the beginning of the phase 5. FT2 Start/Restart from the last known position within the phase 6. FT3 Start/Restart from the beginning of a selected step EX - Execution - (Run the IVP jobs) 7. EX1 Start/Restart from the beginning of the phase 8. EX2 Start/Restart from the last known position within the phase 9. EX3 Start/Restart from the beginning of a selected step
  45. 45. Execution (LST Mode) Help ----------------------------------------------------------------------------------------------- Execution (LST Mode) - DBT Row 5 to 27 of 331 Command ===> Scroll ===> CSR Action Codes: Brm Doc Edm eNt eXe Ftl spR JOB/Task Step Title............................................ IV3C001T C0 NOTE - Introduction - System Definition * IV3C101J C1 JOB - Alloc SYSDEF Data Sets ! IV3C105J C1 JOB - Assembly/Bind RACF Security Exits IV3C201T C2 TASK - Browse the STAGE1 Source Deck E IV3C202J C2 JOB - Run SYSDEF Preprocessor IV3C203J C2 JOB - Run SYSDEF STAGE1 IV3C301J C3 JOB - Run SYSDEF STAGE2 >>> SEE DESCRIPTION IV3C401J C4 JOB - Run SMP/E JCLIN IV3C405T C4 TASK - Edit IMS PROCLIB Members IV3D001T D0 NOTE - Introduction - z/OS and VTAM Interface IV3D101T D1 XMPL - Allocate Interface Data Sets ! IV3D102T D1 XMPL - Allocate Sharing Control Data Sets (SHCDS) IV3D200T D2 XMPL - Update JESx Procedure IV3D201T D2 XMPL - Update IEAAPFxx or PROGxx - Authorized DSN IV3D202T D2 XMPL - Update IEALPAxx - MLPA Modules ! IV3D203T D2 XMPL - Update IFAPRDxx - DFSMStvs enablement - PRA ! IV3D204T D2 XMPL - Update IGDSMSxx - SMS initialization - PRA ! IV3D205T D2 XMPL - Update IEFSSNxx - SMS & RRS Subsystem Names IV3D206T D2 XMPL - Update IEFSSNxx - RLM Subsystem Names
  46. 46. Edit Job Panel _________________________________________________________________________________ EDIT IMS.INSTALIB(IV3C202J) - 01.00 Columns 00001 00072 Command ===> Scroll ===> PAGE ****** ***************************** Top of Data ****************************** 000001 //IV3C202J JOB ACTINFO1, 000002 // 'PGMRNAME', 000003 // CLASS=A, 000004 // MSGCLASS=H,MSGLEVEL=(1,1), 000005 // NOTIFY=JBUTTER, 000006 // REGION=512M 000007 //* 000008 //* 000009 //********************************************************************* 000010 //* IVP IMS 14.1 000011 //* 000012 //* SKELETON: DFSIXSC2 000013 //* 000014 //* FUNCTION: IMS SYSTEM DEFINITION PREPROCESSOR - FOR NAME VALIDATION 000015 //********************************************************************* 000016 //* 000017 //************************************************************@SCPYRT** 000018 //* * 000019 //* LICENSED MATERIALS - PROPERTY OF IBM *
  47. 47. EX Complete Verification Panel Help ________________________________________________________________________________ EX Complete Verification - DBT Command ===> You have just ENDed the Execution phase of the IVP dialog. This is done by setting the Execution Complete flag. You may return to Execution at any time. If Execution is complete: Press ENTER If Execution is NOT complete: Press END NOTE: After the phase complete flag has been set, this panel will no longer be displayed and the phase execution sequence for this phase will not be enforced. The phase complete flags are reset by re-running Table Merge. |------------------------------------------------------| | DFSIX046: DFSIXX10 - Execution Phase ended for "DBT" | |------------------------------------------------------|
  48. 48.  The IVP Dialog process consists of multiple steps. First item for each step describes the step.  The following lists all possible steps (ONLY APPLICABLE STEPS PRESENTED): • STEPa - IVP Preparation • STEPc - System definition • STEPd - Interface IMS to MVS and VTAM • STEPe - Prepare IVP Applications and System • STEPf - IVP Execution - DBB System (Batch) • STEPg - IVP Execution - DBC System (DBCTL) • STEPh - IVP Execution - DBT System (DB/DC) • STEPi - IVP Execution - XRF System • STEPj - IVP Execution - DCC System (DCCTL) • STEPn - Partition Data Base Sample • STEPo - Common Service Layer • STEPp - Enhanced Command Environment - No RM • STEPq - IMS Connect Sample • STEPr - Parallel Recon Access Sample (PRA) • STEPs - Callout Sample • STEPt - Open Database Sample • STEPu – IMSRSC Repository Usage for DRD • STEPz - Index of additional PDS members V14 IVP Steps
  49. 49. IVP 'A' Series The items within the 'Ax' series of steps are used to perform initialization for the IVP Dialog There are no user executable JOBs within these steps Honorable Mentions: •IV_A303N - This member contains statements used to load MSDB’s. These statements may need to be changed to point to LTERMS in the sysgen if you alter the vanilla IVP SYSGEN
  50. 50. The "IVP" is an elaborate set of examples built around several sample applications and several different types of execution environments. All of the IVP materials are designed to support the "IVP" Honorable Mentions •IV_C301J - Job to run SYSDEF STAGE2 –Contains a dummy place holder and is filled in when SYSDEF STAGE1 is run (IV_C203J) •IV_C401J - Job to run SMP/E JCLIN –Should be run after every SYSGEN IVP 'C' Series
  51. 51. The "Dx" series of EXAMPLES identify the JOBs and TASKs which the user must perform in order to establish the interfaces between IMS, z/OS and between IMS and VTAM These steps must be accounted for when upgrading releases of z/OS Honorable Mentions • IV_D209T - XMPL - Install TYPE 2 SVC –Recommend using a different number from that being used by a previous version –The TYPE 2 SVC is downward compatible. See Release Planning Guide –If in both IEANUC0x and NML - IEANUC0x will be used See OY45706 for how to remove a CSECT from IEANUC0x • IV_D210T - XMPL - Link-edit TYPE 4 SVC –Recommend using a different number from that being used by a previous version –The TYPE 4 SVC is downward compatible. See Release Planning Guide IVP 'D' Series
  52. 52. Honorable Mentions - Continued •IV_D401T - TASK - IPL MVS with MLPA or CLPA OPTION –Be sure to IPL with this CLPA to make changes effective IVP 'D' Series - Continued
  53. 53. The "Ex" series of steps identify the JOBs and TASKs which the user must perform in order to prepare the sample applications and the sample IMS system for execution Honorable Mentions • IV_E203J - Job ACBGEN • This is the first job to use the T2 SVC. A failure in this job quite often is due to a problem with this SVC • IV_E204J - Job MFS Language Utility –May need to update DEV statements in MFS source to match appropriate device type •IV3E302J – Job Add Control Statements to IMS.PROCLIB –If JAVA sub-option selected If IPL after running this or file system unmounted re-run as creates files in /tmp directory used by subsequent jobs • IV_E318J - Job Copy Staging Libraries –If SYSGEN is re-done this job must be re-ran as well. SYSGEN updates staging libraries. This job copies from staging to libraries used by online region IVP 'E' Series
  54. 54. The "Fx" series of steps identify the JOBs and TASKs which the user must perform during the execution of the "DBB" (Batch) Sample System. This sequence of items is designed to be run in the order presented and restarted only from the beginning Honorable Mentions •IV_F206J - Job FF HIDAM Update –Be sure to read the instructions (action 'n') before running this job as they will ask to cancel the job •IV_F207J - Job FF HDAM Update –Be sure to read the instructions (action 'n') before running this job as they will ask to cancel the job •IV_F401J - Job Scratch Data Sets –Done so this series of steps can be run again from the top –All following steps will contain a similar job, be sure to run if restarting a step IVP 'F' Series
  55. 55. The "Hx" series of steps identify the JOBs and TASKs which the user must perform during the execution of the "DBT" (DB/DC) Sample System Most of the utility processing in this sequence relies upon OLDS input. The JCL for these utilities has been prepared under the assumption that the execution sequence will be run from start to finish, as documented, without additional OLDS switches, IMS restarts, etc. If the OLDS usage sequence is altered, the utility JCL which relies upon OLDS input will have to be changed Contains jobs/tasks to start/stop the control region as well as test various recovery scenarios and utilities Be sure to view the documentation associated with each job/task before performing it (action 'n') IVP 'H' Series
  56. 56. IMS Migration Considerations Migration Considerations
  57. 57. 57 Verify software and hardware requisites •Program Directory Migration/Coexistence maintenance •REPORT MISSINGFIX (FIXCAT) •PSP Bucket Review IMS Release Planning guide for this release and any release being skipped Review PSP Buckets (UPGRADE: IMS1400 | IMS1300) Install new version of IMS Possible upgrade to IMS tools and related products •See http://tinyurl.com/br8y2o7 Install z/OS interface modules IMS Type 2 and Type 4 SVCs Perform any D/B recoveries that have Extended Error Queue Elements (EEQE's) •/DIS DB EEQE Migration Tasks
  58. 58. 58 Upgrade RECONs •CHANGE.RECON UPGRADE – Can use CHECKUP System definition (ALL) ACBGEN Possible changes to procedures or jobs – Ensure DRA Client address spaces (CICS,DB2 SPAS, etc.) point to correct SDFSRESL (DRA and JCL) Re-assemble any user code that accesses IMS control blocks or log records •Re-work USERMODS as necessary (don’t forget about DFSIDEF0) Ensure appropriate Dynamic Allocation members and exits are available to the new environment •Compare members in current SDFSRESL to those in new SDFSRESL  Consider changes in IMS commands Migration Tasks - 2
  59. 59. 59 Monitor changes in storage utilization (CSA/ECSA/PRIVATE/EPRIVATE) • May need to adjust IMS pool sizes • Take SVC dumps of IMS address spaces prior to migration and keep them for comparison purposes Prepare and test a fallback plan Cold start (/NRE CHKPT 0 FORMAT ALL) Migration Tasks - 3
  60. 60. 60 Recommend initial migration be done without implementing optional new functions. •Once stable in production then take advantage of new functions As of IMS V14 all distribution libraries (ADFS…) and target libraries (SDFS…) except SDFSRESL may be either a PDS or PDSE • Delivered as PDSEs • SDFSRESL must be a PDS • Other execution data sets, such as FORMAT, ACBLIB, DBDLIB, PSBLIB and MODBLKS must still be a PDS  In IMS V14 all ++SRC and ++MAC members have been re-sequenced • Will need to re-work USERMODs Migration Overview: • Similar tasks as previous IMS release-to-release migrations –Application programs continue to work without any change or recompile • Databases do not have to be changed, upgraded, reorganized, image copied, etc. • Log records have been modified and added –Products which read logs may need to be updated –User written programs may need to be modified –ILOGREC macro may be assembled to map DSECTs for most IMS log records ILOGREC RECID=ALL Migration Considerations
  61. 61. 61 SECURITY macro removed from SYSGEN (V13) •Parms in DFSPBxxx and DFSDCxxx •Exits DFSCSGN0, DFSCTRN0, DFSCTSE0 no longer in DFSVNUCx – Standalone loaded at startup In V13 and above DFSCSGN0 called at IMS initialization. The exit is able to return an address of shared storage. That address will be passed to DFSCSGN0, DFSCTRN0 and DFSCTSE0 for every call – If the exit routines cannot be linked separately or cannot use a common work area, they must be linked in the following manner: If the CSECT of DFSCTSE0 is part of DFSCTRN0 source, DFSCTSE0 must be linked as an ALIAS of DFSCTRN0. If virtual address spaces are used to exchange data between DFSCSGN0, DFSCTRN0, and DFSCTSE0, both DFSCTSE0 and DFSCSGN0 must be linked as an ALIAS of DFSCTRN0. Additional considerations: 1. Exits are loaded dynamically in V13, so use of VCONs to reference other modules or control blocks will no longer work 2. A new initialization call ( R0=4 ) has been added for DFSCSGN0. Users should verify their DFSCSGN0 exits will function correctly with this new entry vector Migration Considerations - 2
  62. 62. 62  Database Versioning • If migrating an IMS system that uses database versioning to IMS 14, you must preserve in the catalog the DBD segment instances that define the prior version of any DBD version that is still in use  DEDB Alter • To run the DEDB Alter utility, all IMS data-sharing systems must be at the IMS V13 or later. The MINVERS value in the RECON data set must be 13.1 or later. – The default value for MINVERS in IMS 14 is 12.1  HALDB Alter • HALDB alter requires the MINVERS value in the RECON data set to be set to 13.1 or later – See the IMS Release Panning Guide Migrating to IMS V14: Database for additional details  IMS Management of ACBs and IMS Catalog • In IMS 14, the IMS management of application control blocks (ACBs) introduces migration considerations for users of the IMS catalog. – See the IMS Release Panning Guide Migrating to IMS V14: Database for additional details Migration Considerations: Database
  63. 63. 63  HALDB Support for 8G OSAM • All IMS systems must be at IMS 14 or later and the MINVERS value in the RECON data set must be 14.1 before you can use 8-GB OSAM data sets in a HALDB database  IMS Catalog • The IMS catalog is a system database that can require special consideration when migrating to a new release, depending on changes to the IMS catalog itself or on changes made to other IMS functions that use the IMS catalog. • See the Release Planning Guide section Migrating to IMS 14:DB for additional details Migration Considerations Database - 2
  64. 64. 64  APPC/IMS Flood Control • In IMS 14, the new APPC/IMS flood control function is active by default and the IMS system will take action if the default flood thresholds are reached unless you change the default thresholds or disable the function  MSC • MSC Exit Routines – See the IMS Release Planning Guide Migrating to IMS 14: TM • Dynamic Definition of MSC – See the IMS Release Planning Guide Migrating to IMS 14: TM  When using MSC to connect IMS systems with different releases, consider all message types (such as ISC, APPC, and OTMA) and the prefix sizes that accompany them  Synchronous Program Switch • to use the synchronous program switch function in a shared queues environment, all of the participating systems must have a MINVERS value of at least 13.1 Migration Considerations Transaction Manager
  65. 65. 65  OTMA • Dynamic Storage for OTMA Descriptors – In IMS 14, the value that is displayed in the error messages DFS2384W and DFS3678E can be 255, 510, or another value that is specified on the DDESCMAX or MDESCMAX keywords in the DFSOTMA descriptor • Global Flood Control • In IMS V13 existing IMS error existing DFS4388W and DFS0793I messages were enhanced to be consistent with the new DFS3428W and DFS3429E • messages. Changes in automations program might be needed Migration Considerations Transaction Manager -2
  66. 66. 66 CQS (Shared Queues) •IMS V14 cannot register with a pre IMS V14 CQS •IMS V13 cannot register with a pre IMS V13 CQS •IMS V12 or IMS V13 can register with an IMS V14 CQS •User or vendor written CQS clients that want to register with IMS V14 CQS must use CQS macros from IMS V12, IMS V13 or IMS V14 •User or vendor written CQS clients that are assembled with IMS V14 CQS macros cannot register with a PRE IMS V14 CQS •A V12, V13 or V14 CQS can connect to the same coupling facility CSL •If running a mixed version IMSplex recommend CSL address spaces use the latest version of IMS (SCI, OM, RM) • ODBM version must match IMS version Data Sharing • IMS databases may be shared between supported IMS releases Coexistence
  67. 67. 67 Database Recovery Utilities • IMS V14 Database Recovery utility (DFSURDB0) and Database Change Accumulation utility (DFSUCUM0) – Accepts logs, Image Copy and Change Accumulation datasets from IMS V12 or later Utility inputs • Batch Backout, Log Archive, Log Recovery, Log Analysis –Use utility from IMS release which produced the log IMS V14 RECONs may be used by all supported IMS releases – With compatibility service Extended checkpoints • Cannot be used to restart applications across different IMS versions See Release Planning Guide Coexistence - Cont
  68. 68. 68 Fallback A system may fallback to a previous release after upgrade • Upgraded RECONs are used • Additional considerations: –Database recoveries use latest IMS version utilities –Always use ACBLIB built at the level of the running system –Cold start (/NRE CHKPT 0 FORMAT ALL) Fallback
  69. 69. 69 The following SVC's are used by IMS • T2 DFSVC200 (IGCxxx) –Downward compatible. Can use the one from the highest level of IMS with previous versions –SVC number specified in SYSGEN SVCNO keyword on IMSCTF macro DFSPBxxx member – Can be updated dynamically for life of the IPL using DFSUSVC0 • T4 DSP00MVS (IGC00xxx) –Downward compatible. Can use the one from the highest level of IMS with previous versions –SVC number specified in SYSGEN SVCNO keyword on IMSCTF macro – Can be updated dynamically for life of the IPL using DFSUSVC0 IMS SVCs
  70. 70. 70 IMS Utility DFSUSVC0 can be used to update both the IMS T2 and IMS T4 SVC dynamically • Lasts for the life of the IPL –Loads SVC in CSA/ECSA and updates z/OS SVCTABLE to point to new module –T2 SVC processing Checks IMS SVC directory table to determine if any IMS tasks/jobs currently running and if so request to update T2 SVC fails –T4 SVC processing Load a new copy in ECSA each time DFSUSVC0 run requesting T4 SVC to be updated –The following shows an example of the JCL which for executing DFSUSVC0: //STEP1 EXEC PGM=DFSUSVC0,PARM='SVCTYPE=(2,4)' //*STEP1 EXEC PGM=DFSUSVC0,PARM='SVCTYPE=(2)' //*STEP1 EXEC PGM=DFSUSVC0,PARM='SVCTYPE=(4)' //STEPLIB DD DSN=IMS.SDFSRESL,DISP=SHR //DFSRESLB DD DSN=IMS.SDFSRESL,DISP=SHR //SYSPRINT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=121) DFSUSVC0
  71. 71. 71  IMS 14 is the last version of IMS to support Remote Site Recovery (RSR).  IMS 14 systems and later do not support the IMS Classic Java APIs. If you are using these APIs, you must migrate to the IMS Universal drivers  IMS 14 is the last version of IMS to support the IMS Connect SSL function. Installations that that use this function should migrate to using IBM z/OS Communications Server Application Transparent Transport Layer Security (AT-TLS) to set up Secure Socket Layer (SSL) on TCP/IP connections to IMS Connect  Support for the IMS Control Center is discontinued. To explore, query, start, and stop IMS resources from a browser interface in a distributed environment, use the IBM Management Console for IMS and DB2 for z/OS V1.1 (5655-TAC).  XRF support for the data sharing of full-function databases is discontinued in IMS 14  IMS 14 systems and later do not support IMS MFS Web Enablement. Current users should migrate to IBM Rational Host Access Transformation Services. IMS Sunset
  72. 72. 72  IMS 14 is the last version of IMS to support the IMS Connect LOCAL option for connections between IMS Connect and IMS TM Resource Adapter. Reconfigure any connections that currently use the LOCAL option to use either TCP/IP or the WebSphere Optimized Local Adapter  IBM is withdrawing from support the Communication Controller for Linux on System z (CCL). The announced date for withdrawal is March 31, 2016. If you are using CCL for IMS XRF tracking of VTAM terminals, consider replacing XRF entirely by setting up an IMSplex with two or more IMS systems and using VTAM Generic Resources (VGR). This option requires a Parallel Sysplex environment.  IMS 14 is the last version of IMS to support the IMS Connect SSL function. If using should migrate to using IBM z/OS Communications Server Application Transparent Transport Layer Security (AT-TLS) to set up Secure Socket Layer (SSL) on TCP/IP connections to IMS Connect  IMS 14 is the last version of IMS to support the IMS Connect LOCAL option for connections between IMS Connect and IMS TM Resource Adapter. Reconfigure any connections that currently use the LOCAL option to use either TCP/IP or the WebSphere Optimized Local Adapter IMS Sunset -2
  73. 73. 73 Contact the IMS Level 2 for assistance •We are here to help and your success is our reason for being Migration/Installation Assistance
  74. 74. IMS Definition IMS Definition
  75. 75. The direction of the IMS product is the eventual removal of SYSGEN •IMS V10 introduced Dynamic Resource Definition (DRD) –First phase of implementation •IMS V12 introduced the Repository –Strategic direction in IMS Architecture  IMS uses the SYSGEN process to tailor each system •Used to determine which features/components are to be included –Eventually which features/components to be included will be determined at execution time •Defines resources that are to be made available to the system •Defines the environment in which the system is to be run •Builds the system from the IMS distribution libraries –Service in APPLY only status may be regressed  SYSGEN does not build a complete system What/Why IMS SYSGEN
  76. 76.  IMS SYSGEN consists of multiple phases which are as follows: Coding of the IMS macros which will define the system (stage 1 input) Running the preprocessor to verify the system definition (optional) Running the assembly using the IMS macros as input (stage 1) Running the job(s) built by stage 1 to actually build the system (stage 2) Running SMP/E JCLIN to update the target zones SYSGEN Phases Summary
  77. 77.  The level of SYSGEN are specified in the 'SYSTEM' keyword of the 'IMSCTRL' macro  The following illustrates the different levels of SYSGEN Level of SYSGEN
  78. 78. MODBLKS MODBLKS Level SYSGEN  Generates control blocks members for resources to be added online using online change (e.g., APPLCTN, DATABASE, TRANSACT, and RTCODE macros)
  79. 79. MODBLKS CTLBLKS Level SYSGEN CTLBLKS Generates modules for all IMS control blocks Normally done to define network definitions like TERMINAL and LINE macros
  80. 80. MODBLKS NUCLEUS Level SYSGEN CTLBLKS Generates an IMS nucleus for the control region Also used to create a new IMS nucleus NUCLEUS
  81. 81. MODBLKS ON-LINE Level SYSGEN CTLBLKS Generates all modules and procedures needed for the online environment NUCLEUS ON-LINE
  82. 82. BATCH Level SYSGEN BATCH Generates modules and procedures needed to build a complete batch system
  83. 83. MODBLKS ALL Level SYSGEN CTLBLKS NUCLEUS ON-LINE BATCH ALL Must be done during initial installation
  84. 84. MSVERIFY Level SYSGEN Builds blocks for the MSC Verification Utility •Unique in that not used to build for a running system
  85. 85.  In addition to being required for LGEN, the preprocessor can be used to verify the system definition • The following are additional functions of the preprocessor: –Check to ensure resource names are alphanumeric –Check for duplicate names WITHIN resources. The following are the resources for which this is checked:  DBD  PSB  VTAM node  MS link  Logical terminal (lterms)  Transaction codes  Routing codes  Subpool  MSLINK partner IDs  MSPLINK physical link  Remote system VTAM node • If used, can specify NAMECHK=NO on IMSCTRL macro The Preprocessor
  86. 86.  Two types of systems can be configured which will determine how stage 1 is run  Standard System  LGEN System –Strictly enforces input macro sequence –Sample JCL in Install Volume 2  The configuration is specified as a parm on the SYSTEM keyword on the IMSCTRL macro  Requires an ON-LINE or ALL Sysgen to change  Return code of '0' or '2' indicates stage 1 was successful Running the stage 1
  87. 87. The stage 2 jobs must be run in the order created Recommend using ONEJOB parm on IMSGEN macro Return code of '0' is expected from all but the MFS steps •Return code of '4' is expected from MFS steps –DFSUPAA0 •Applicable to DC systems only Running the stage 2
  88. 88.  JCLIN pointing to the target zone should be run after every Sysgen for libraries maintained by SMP/E • The SMP/E target zone will be updated to accurately represent the running system • When not done, errors may be encountered the next time service is APPLIED using SMP/E • SMP/E JCLIN JCL will vary depending on the Sysgen configuration used –IVP job IV_C401J can be used as an example JCLIN after Sysgen
  89. 89.  IMS V10 introduces Dynamic Resource Definition (DRD) • Usage is optional –Manages same resources as could be managed by a MODBLKS type SYSGEN –SYSGEN still required for CTLBLKS and above • Dynamically Update, Create, Delete certain resources definitions without having to do a system definition or online change process –Databases, Transactions, Applications (PSB) or Fastpath routing codes Definitions can be created dynamically or imported during cold start processing –Uses Resource Definition Dataset (RDDS) to manage resource definitions BSAM dataset –Managed from a Single Point of control TSO SPOC IVP provides samples Dynamic Resource Definition (DRD)
  90. 90.  Dynamic Resource Definition (DRD) •DRD and Online Change mutually exclusive •PROCLIB member specification MODBLKS=DYN to enable DRD –DFSDFxxx, DFSSQxxx(Shared Queues) or DFSCGxxx (CSL) DFSSQxxx and DFSCGxxx override DFSDFxxx DFSDF= in DFSPBxxx –DFSDFxxx - Dynamic resource section AUTOEXPORT Automatically writes to oldest RDDS at system checkpoint AUTOIMPORT Automatically imports from RDDS or MODBLKS during restart RDDSDSN – names of RDDS datasets Recommend at least 3 Same blocksize / different space allocations Dynamic Resource Definition (DRD) – Cont1
  91. 91.  Dynamic Resource Definition (DRD) –Changes made online are logged to retained across warm start –Changes can be exported to RDDS Can happen automatically (AUTOEXPORT) Imported during cold start (AUTOIMPORT) After SYSGEN and cold start can IMPORT from MODBLKS •DFSURDD0 – RDDS batch extraction utility can be used to create stage 1 macro statements or type 2 UPDATE commands for definitions in RDDS – CSLUSPOC is the batch SPOC utility Dynamic Resource Definition (DRD) – Cont2
  92. 92.  To enable your IMS to use DRD (from System Definition Guide): • Shut down IMS normally. • Change MODBLKS=OLC to MODBLKS=DYN in either the COMMON_SERVICE_LAYER section of the DFSDFxxx member or in the DFSCGxxx member in the IMS.PROCLIB data set. • Specify the following keywords in the DYNAMIC_RESOURCES section of the DFSDFxxx member of the IMS.PROCLIB data set: AUTOEXPORT=AUTO AUTOIMPORT=AUTO RDDSDSN=(rdds1,rdds2,rdds3) • Allocate RDDS datasets – Must have an EOF marker  Can use IEBGENER  See IVP for sample JCL or IMS.SDFSSLIB(DFSRDDAL) - - uses IEBGENER Enabling DRD
  93. 93. • Cold start IMS, specifying DFSDF=xxx in the control region execution parameters – xxx identifies the suffix of the DFSDFxxx member in the IMS.PROCLIB data set that IMS will use for this startup. – IMS loads the resource definitions from the IMS.MODBLKS data set because the defined RDDSs are empty. The IMS.MODBLKS data set is used only the first time you implement DRD, except for fallback purposes. IMS then uses the resource definitions to create the internal control blocks needed to manage the resources. When the initial checkpoint is taken, the resource definitions are automatically written out to one of the defined resource definition data sets (RDDS) because AUTOEXPORT=AUTO is specified. Note: After IMS starts with DRD enabled, you will no longer be able to use the online change process to add, change, or delete database, application program, route code, or transaction resources or resource definitions. Also, since AUTOIMPORT=AUTO is specified and the RDDSs are no longer empty, IMS loads its resource definitions Enabling DRD – Cont.
  94. 94.  The IMS Repository can be used to store DRD definitions instead of RDDS  Next step in the evolution of DRD  Enables multiple IMS systems in a multiple-IMS IMSplex to manage, store, share and retrieve resource definitions  Enables a single IMS system in a single-IMS IMSplex to manage, store, share and retrieve resources  Repository Function Components • Repository Server (RS) address space • Repository catalog datasets • Repository datasets • CSL requirements and RM • Centralized method for storing and retrieving resource definitions in an IMSplex Repository
  95. 95.  Focus is on improving the systems management and resource management aspects of handling IMS resource definitions • For production systems • For test systems Repository Cont.
  96. 96. • Consolidation of resource definitions in a single place • DRD definitions are the initial implementation of the IMS repository function (to replace RDDSs) • Full support for populating, managing, storing, sharing, and retrieving a consistent set of DRD stored resource definitions for multiple-IMS IMSplexes and single-IMS IMSplexes • Manual coordination of multiple RDDSs in a multiple-IMS IMSplex eliminated, replaced by basic functioning of the IMS repository • Improvements in IMSplex systems and resource management with the repository • A strategic direction for IMS architecture Repository Benefits
  97. 97. Repository Function Usage IMS 12 and above, the resource and descriptor definitions for Dynamic Resource Definition (DRD) can be stored in an IMS repository •Contains resource definitions for programs/transactions/databases/FP routing codes & descriptors •Called the IMSRSC, the IMS resource definition repository IMS 12 and above can retrieve the stored resource definitions from the IMSRSC repository to dynamically generate runtime resources for DRD
  98. 98. Repository Support for DRD Function DRD users in IMS 11 moving to IMS 12 or above •Can use existing RDDSs from IMS 11 for stored resource definitions in IMS 12 and above •Can use existing RDDSs from IMS 11 for stored resource definitions at initial migration to IMS 12 and above, then can migrate to the new IMSRSC repository •Can use the new IMSRSC repository to store definitions in IMS 12 and above
  99. 99. Repository Population Rep MODBLKS Utility Utility RDDS Direct from MODBLKS IMS Temp RDDS Export command RM Direct from RDDS
  100. 100. Repository Components - 1 A Common Service Layer (CSL) IMSplex configuration consists of: •Operations Manager (OM) –Used for new/modified type-2 commands for repository functions •Resource Manager (RM) –Used for managing the new Repository Server (RS) address space –All online access to Repository Server is through RM address space –New type-2 commands for managing the Repository Server UPDATE RM QUERY RM –RM is enabled to the repository by specifying a Repository Section in the RM initialization member (CSLRIxxx)
  101. 101. Repository Components - 2 •Structured Call Interface (SCI) –Used for communications within the CSL –Not used for communications between RM and the RS –RS is not considered a CSL manager •Optionally, a resource structure in a Coupling Facility –Used for repository name and repository type consistency if present –Managed by a Common Queue Server (CQS) address space –Multiple RMs in an IMSplex require that a resource structure exists •SPOC (single point of control) for entering type-2 commands •Can be a single-IMS IMSplex or a multiple-IMS IMSplex
  102. 102. Repository Components - 3 •Batch utilities –Batch ADMIN utility (FRPBATCH) Commands for managing IMSRSC repositories Functions such as ADD a new IMSRSC repository, LIST the characteristics of an IMSRSC repository, START or STOP an IMSRSC repository –Create RDDS from MODBLKS utility (DFSURCM0) –RDDS to / from repository utilities (Batch RM utilities) RDDS to Repository Utility (CSLURP10) For migration Repository to RDDS Utility (CSLURP20) For fallback
  103. 103. Repository Migration Overview From DRD with RDDSs to DRD with Repository •Create non-system RDDS that contains current definitions via EXPORT command or DRD utilities •Set up repository parameters in PROCLIB members FRPCONFG, BPECONFG, CSLRIxxx, DFSDFxxx •Create catalog repository data sets and IMSRSC repository data sets •Start the Repository Server address space •Use the batch ADMIN utility to define the IMSRSC data sets to the Repository Server •Run the batch RDDS to Repository utility to populate the repository –CSLURP10 •Cold start IMS with AUTOIMPORT specified From no DRD to DRD with Repository •First implement DRD with RDDSs –Set up DRD parameters in DFSDFxxx –Can use DFSURMC0 to create RDDS from MODBLKS (see IVP) •Cold start IMS using updated DFSDFxxx –AUTOIMPORT will use MODBLKS for definitions •Follow process to migrate from DRD with RDDSs to DRD with repository Changes introduced online hardened via EXPORT command • IMS V14 supports AUTOEXPORT to both REPOSITORY and/or RDDS – DFSDFxxx member  AUTOEXPORT=RDDS | REPO | AUTO
  104. 104. Repository Architecture Operations Manager (OM) IMS Control Region Repository Server (RS) SCI SCI X C F X C F RS Catalog Repository Primary/Secondary IMSRSC Repository Primary/Secondary Batch ADMIN Utility (FRPBATCH) RM utilities CSLURP10 / CSLURP20 AuditLog X C F Structured Call Interface SCI Resource Manager (RM) SCI SCI XCF
  105. 105. General IMS Maintenance Recommendation General IMS Maintenance Recommendation
  106. 106. 106 This general product maintenance recommendation provides guidelines that when implemented are intended to produce a more stable environment Risk assessment should be carefully considered. Numerous factors may be involved, some of which follow: – The quality level of the test environment – Business cycle Product Maint Recommendation Overview
  107. 107. The following are factors that cause system Integrity/Stability issues: •Yet to be discovered code defect –Simulate production as closely as possible in a test environment  Service implemented on the system that contains a code defect –PE management  Discussed later in this section Missing service that addresses a problem that can cause integrity/stability issues –HIPER APAR management  Discussed later in this section Service required for compatibility with z/OS or other products –PSP bucket - Cross Product Dependency Section  Discussed later in this section System Integrity/Stability Factors
  108. 108. 108 The general IMS maintenance recommendation for an IMS production system: Initial IMS production system base implementation service level –Latest quarterly RSU –PE resolution –A comprehensive test cycle is recommended prior to production implementation  NOTE: Because IMS maintenance will continue to be distributed during the test cycle, these recommendations along with those on the following page should be included in the initial IMS production base system implementation General IMS Maintenance Recommendation
  109. 109.  Ongoing IMS production system service level  Fully tested fixes for significant** software problems encountered  Fully tested HIPER SYSMODs that are of direct applicability to the specific IMS environment and deemed significant**  Fully tested SYSMODs which resolve PE's that are directly applicable to the specific IMS environment and deemed significant**  Fully tested SYSMODs which resolve security/integrity issues  Review the IMS PSP bucket UPGRADE for the IMS release level and SUBSET FMIDs  Important IMS product related information is continually added and may require action  NOTE: The recommendations outlined above should be followed on an ongoing basis, and should also be included as part of the initial production implementation (See prior page) ** A fix is considered "significant", when consequences which could not be tolerated may be encountered without the application of that fix General IMS Maint Recommendation – Cont
  110. 110.  PTF-in-error (PE) – Designation assigned to PTF’s that were provided to correct a problem but have either not corrected the problem or have introduced a new problem These PTF's are known as exception SYSMODs and are managed in SMP/E through ++HOLD and ++RELEASE statements (HOLDDATA) – Introduced via the SMP/E RECEIVE command PE Defined
  111. 111.  All APARs that address issues containing one or more of the following conditions are marked HIPER:  Causes an IPL or recycle of the system or subsystem - FLAG: SYSTEMOUTAGE/Y ServiceLink: RESTART/BOOT/IPL  Destruction and/or contamination of customer data - FLAG: DATALOSS/Y ServiceLink: DATALOSS  Causes major loss of function to the IMS system - FLAG: FUNCTIONLOSS/Y ServiceLink: FUNCTIONLOSS  Causes severe impact to system performance/throughput - FLAG: PERFORMANCE/Y ServiceLink: PERFORMANCE  HIPERs flagged as follows:  FLAG: HIPER/Y ServiceLink: HIPER  Has the potential to affect many customers • FLAG: PERVASIVE/Y ServiceLink: PERVASIVE NOTE: Another HIPER symptom must also be identified along with PERVASIVE to qualify for HIPER classification HIPER APAR Qualification
  112. 112.  It is recommended that Enhanced HOLDDATA be used to identify exposures to HIPER and PE PTF's • Ensure that a current copy of the Enhanced HOLDDATA has been received in SMP/E • Use SMP/E REPORT ERRSYSMODS to identify all missing PE and HIPER service  Each identified APAR should be examined to determine susceptibility to the IMS environment • Initial applicability can be determined by using the 'USERS AFFECTED' portion of the APAR text  For each APAR deemed applicable to your IMS environment, decide which are significant enough that they need to be processed • Read 'Problem Description' in APAR text for technical details – IMS Technical support can be contacted for additional information  One must weigh the decision to run without the latest PE and HIPER maintenance versus the risk of discovering a PE with that piece of maintenance PE and Hiper Exposure Identification
  113. 113.  ++HOLD statements for PE, HIPER and FIXCAT Downloadable and provided with install/service orders The ‘full.txt’ or ‘full.bin’ files are the only ones that contain FIXCAT statements Entire z/OS Platform is covered in a single set of HOLDDATA REPORT ERRSYSMODS to identify HIPER service not currently installed as well as any PE PTF installed without resolving SYSMOD SET BOUNDARY (GLOBAL) . REPORT ERRSYSMODS ZONES(tzone) . For complete descriptive information see: http://service.boulder.ibm.com/390holddata.html Enhanced Holddata
  114. 114. The following shows an example of a job that can be used to download and RECEIVE a current copy of the Enhanced Holddata: //FTPSTEP EXEC PGM=FTP, // PARM='service.boulder.ibm.com (EXIT' //SYSPRINT DD SYSOUT=* //OUTPUT DD SYSOUT=* //INPUT DD * Anonymous yourid@xxx.com cd s390/holddata locsite CY PRI=15 SEC=5 REC=FB LR=80 BLK=16000 ascii lcd 'IMS' get full.txt ENH.HOLDDATA (replace quit //RECEIVE EXEC PGM=GIMSMP,PARM='PROCESS=WAIT',DYNAMNBR=120 //SMPCSI DD DISP=SHR,DSN='IMS.GLOBAL.CSI' //SMPCNTL DD * SET BOUNDARY (GLOBAL) . RECEIVE HOLDDATA . //SMPHOLD DD DISP=SHR,DSN=IMS.ENH.HOLDDATA Enhanced Holddata - Example
  115. 115. IBM maintains a Security Portal that contains information on Security or Integrity fixes IBM treats information about Security/Integrity fixes as IBM Confidential information •The Security Portal contains Common Vulnerability Scoring System (CVSS) values*. – CVSS is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." APARs scored from 1 to 10 based on characteristics and impact of vulnerabilities Access to the Security Portal requires •An active z/OS or z/VM customer •Client management approval and agreement to keep the information confidential •An IBM ID able to access Resource Link https://www-304.ibm.com/servers/resourcelink/lib03020.nsf/pages/securityalerts?OpenDocument&start=1&count=2000 •Instructions to access the System z Security Portal can be found at: http://www.ibm.com/systems/z/advantages/security/integrity_sub.html IBM Security Portal
  116. 116.  On the Security Portal Web site IBM provides: •The current ASSIGN file to enable system programmers to install security/integrity fixes that have been SMP/E RECEIVEd – ++ ASSIGN SOURCEID(SECINT) TO(UIxxxxx). – ++ ASSIGN SOURCEID(SECINT) TO(UIyyyyy). •The current HOLDDATA file to enable system programmers to identify security/integrity fixes not currently installed on their system – ++ HOLD (JCI650D) FMID(JCI650D) REASON(AMaaaaa) ERROR DATE(11056)  COMMENT(SMRTDATA(FIX(UIxxxxx) SYMP(SECINT)  CHGDT(110225))) CLASS(SECINT). – ++ HOLD (JCI660D) FMID(JCI660D) REASON(AMbbbbb) ERROR DATE(11056)  COMMENT(SMRTDATA(FIX(UIyyyyy) SYMP(SECINT) CHGDT(110225))) CLASS(SECINT) •The current CVSS file to enable security administrators to assess their security exposure – Date APAR Bas Tmp Vector – 2011/07/27 OAnnnnn 1.9 1.7 (AV:L/AC:M/Au:N/C:P/I:N/A:N/E:ND/RL:OF/RC:C) – 2011/08/03 OAnnnnn 7.2 6.3 (AV:L/AC:L/Au:N/C:C/I:C/A:C/E:ND/RL:OF/RC:C IBM Security Portal - Cont
  117. 117. Expand Security/Integrity HOLDDATA statements ++ HOLD (HDB9910) FMID(HDB9910) REASON(AM11111) ERROR DATE(14364) COMMENT(SMRTDATA(FIX(UK22222) SYMP(7.2 6.3 (AV:L/AC:L/Au:N/C:C/I:C/A:C/E:ND/RL:OF/RC:C)) CHGDT(141230))) CLASS(SECINT). REPORT ERRSYSMODS will show CVSS data (if present) IBM Security Portal - Cont 2
  118. 118. Perform risk assessment on processed PE'd PTFs for which the system is susceptible Courses of action can include: –Remove PTF in error if not already ACCEPTed –Leave the PTF in place if the reported PE symptom is not significant –Put in place operator procedures to restrict access to reported areas of exposure –Apply corrective APAR/PTF fix if available –Request a FIXTEST for the reported problem from software service –Request a USERMOD code bypass for the reported problem from software service Perform Risk Assessment of Applicable PTFs
  119. 119.  Each UPGRADE level includes SUBSET entries for each IMS FMID within that release. The SUBSET for each installed FMID needs to be examined separately  Program Directory provides Upgrade and Subset names  Key areas for review within each SUBSET entry include the following: –Opening Text –Change Summary –Service Recommendation Summary –Installation Information - Section 1 –Documentation Changes - Section 2 –General Information - Section 3 –Service Recommendations - Section 4 –Cross Product Dependencies - Section 5  Available on WEB at: http://www14.software.ibm.com/webapp/set2/psearch/search?domain=psp PSP UPGRADE/SUBSET
  120. 120. 120 IMS release 14.1 UPGRADE name = IMS1400  The SUBSET names (IMS related FMIDs): CHG/INDEX HMK1400 JMK1401 JMK1402 JMK1403 JMK1404 JMK1405 JMK1406 HIR2230 JMK141Z/GA HMK1400/GA JMK1401/GA JMK1402/GA JMK1403/GA JMK1404/GA JMK1405/GA JMK1406/GA HIR2230/1239 IMS V14 PSP Bucket Names
  121. 121. 121 IMS release 13.1 UPGRADE name = IMS1300  The SUBSET names (IMS related FMIDs): CHG/INDEX HMK1300 JMK1301 JMK1302 JMK1303 JMK1304 JMK1305 JMK1306 HIR2230 JMK131Z/GA HMK1300/GA JMK1301/GA JMK1302/GA JMK1303/GA JMK1304/GA JMK1305/GA JMK1306/GA HIR2230/1239 HMK1300/GA1 IMS V13 PSP Bucket Names
  122. 122. 122 Goal: Enhance the way service is tested and delivered for z/OS, by providing a single coordinated service recommendation Provides cross product testing for participating products •List of products tested continually expanding This is in addition to testing that was already being performed Standardize maintenance recommendation on z/OS platform See http://www.ibm.com/servers/eserver/zseries/zos/servicetst/ for additional information Consolidated Service Test (CST)
  123. 123. 123 Consolidated Service Test - 2 All APARS included regardless of severity Testing of quarterly RSUs: Three 30-day test cycles exercised System upgraded every 30 days to include the next monthly RSU –HIPERs, PE fixes, security, integrity, pervasive and fixes to CST problems Stress and saturation testing, failure and recovery testing, and rolling IPL maintenance test of previous Quarterly RSU to current Quarterly RSU Done prior to availability of RSUyymm SOURCEID being assigned –Some products are not included in the CST testing but they still get marked RSU based on calendar rules set up for RSU Testing covers integrated workloads across all participating z/Series and S/390 products –Provides one clear consistent recommendation for the platform –Workloads continue to evolve Also available monthly 30 days of tested Hiper/PE, security/integrity and pervasive APARs between quarterly testing
  124. 124. Consolidated Service Test - 3 Quarterly CST reports available consisting of: CST hardware environment Software environment including maintenance levels Rollout recommendations Highlights for the QTR Problems encountered Excluded maintenance list  Once service has passed CST testing Marked with RSU (Recommended Service Upgrade) RSUyymm SOURCEID notation – QTRLY = RSUyy03, RSUyy06, RSUyy09, RSUyy12 – Monthly = RSUyy01, RSUyy02, RSUyy04, etc. –The following points to SOURCEID assignments for RSUyymm and PUTyymm:  ftp://public.dhe.ibm.com/s390/assigns/
  125. 125. 125 RSU Contents Quarterly RSU1512 – Available January 2016 All service through the end of September 2015 not already marked RSU. PE resolution and HIPER/Security/Integrity/Pervasive PTFs and their associated requisites and supersedes through November 2015 Monthly RSU1601 – Available February 2016 Based upon the quarter above, this addendum contains PE resolution and HIPER/Security/Integrity/Pervasive PTFs and their associated requisites and supersedes through December 2015 Monthly RSU1602 – Available March 2016 Based upon the quarter above, this addendum contains PE resolution and HIPER/Security/Integrity/Pervasive PTFs and their associated requisites and supersedes through January 2016
  126. 126. Achieving IMS Maintenance Recommendation  Current IMS Maintenance Upgrade Technique  Obtain current service using ShopzSeries  Review IMS PSP Buckets  Obtain and RECEIVE current Enhanced Holddata  SMP/E process the service –Select CST created RSUyymm SOURCEIDs –Resolve PEs –Resolve System HOLDs  Obtain and RECEIVE current Enhanced Holddata again –Run SMP/E REPORT ERRSYSMODS to identify HIPER/PE exposure Obtain applicable SYSMODS from ShopzSeries Process SYSMODs that are applicable to your environment Use IMS Support Website or PSP Buckets for APAR descriptions Contact IBM Support Center for assistance as needed  Test the new maintenance level  Repeat underscored items on an ongoing basis to remain current –As close to implementation as possible
  127. 127. Achieving IMS Maintenance Recommendation - Cont.  Caution: SYSMODs in APPLY status may be regressed by SYSGEN –Either ACCEPT all PTFs in APPLY status prior to SYSGEN –Or, After SYSGEN, reprocess APPLYed SYSMODs  Determine SYSMODs in APPLY only status SET BOUNDARY (targetzone) . LIST APAR PTF USERMOD NOACCEPT NOSUP . - This will supply the list of APPLY only SYSMODs xxxxxxx  APPLY REDO NOJCLIN every SYSMOD in APPLY status APPLY REDO NOJCLIN SELECT( xxxxxxx xxxxxxx xxxxxxx ) . **NOTE: Only specify NOJCLIN for REDO processing Special handling may be required for SYSMODs in APPLY status that have holds requiring SYSGEN or DELETE
  128. 128. IMS service can be processed using the standard SMP/E RECEIVE, APPLY, ACCEPT processing OR SMP/E RECEIVE, 'ACCEPT BYPASS(APPLYCHECK)' processing Informational APAR II13024 contains the steps required when processing using this technique •These steps are also used when: –Removing features from a Gen'd system –Anything that requires rebuilding the target environment from the distribution environment Resolves maintenance mismatch situations Maintenance Upgrade
  129. 129. 129  z/OS Release 10 and SMP/E Release 3.5 introduce FIXCAT HOLDDATA to simplify identifying required service from PSP buckets •The ‘full txt’ or ‘full.bin’ files are the only ones that contain FIXCAT statements •The following contains all FIXCAT categories and their descriptions: http://www-03.ibm.com/systems/z/os/zos/features/smpe/fix-category.html  Specify FIXCAT category on SOURCEID operand for the APPLY and ACCEPT  IMS specific categories •IBM.Coexistence.IMS.V11 Fixes that allow IMS V9 and V10 to coexist with, and fallback from, IMS V11 •IBM.Coexistence.IMS.V12 Fixes that allow IMS V10 and V11 to coexist with, and fallback from, IMS V12 IBM.Coexistence.IMS.V13 Fixes that allow IMS V11 and V12 to coexist with, and fallback from, IMS V13 IBM.Coexistence.IMS.V14 Fixes that allow IMS V12 and V13 to coexist with, and fallback from, IMS V14 Fixcat
  130. 130. 130  Fixcat -2 •IBM.TargetSystem-RequiredService.IMS.V10 Fixes required on other IBM products to allow them to run with IMS V10 •IBM.TargetSystem-RequiredService.IMS.V11 Fixes required on other IBM products to allow them to run with IMS V11 •IBM.TargetSystem-RequiredService.IMS.V12 Fixes required on other IBM products to allow them to run with IMS V12 •IBM.TargetSystem-RequiredService.IMS.V13 Fixes required on other IBM products to allow them to run with IMS V13 •IBM.TargetSystem-RequiredService.IMS.V14 Fixes required on other IBM products to allow them to run with IMS V14 Fixcat - 2
  131. 131. 131  The following are the z/OS software based FIXCAT categories supported by IMS: •Category: IBM.TargetSystem-RequiredService.z/OS.V2R2 Description: Fix required on other IBM products to allow them to run on z/OS V2R2 •Category: IBM.TargetSystem-RequiredService.z/OS.V2R1 Description: Fix required on other IBM products to allow them to run on z/OS V2R1 •Category: IBM.TargetSystem-RequiredService.z/OS.V1R13  Description: Fix required on other IBM products to allow them to run on z/OS V1R13 •Category: IBM.TargetSystem-RequiredService.z/OS.V1R12 Description: Fix required on other IBM products to allow them to run on z/OS V1R12 •Category: IBM.TargetSystem-RequiredService.z/OS.V1R11 Description: Fix required on other IBM products to allow them to run on z/OS V1R11 •Category: IBM.Function.EAV Description: Fix required to enable Extended Address Volumes support Fixcat - 3
  132. 132. 132  Examples of non IMS specific categories •IBM.ProductInstall-RequiredService –HIPER •IBM.Coexistence.z/OS.V2R2 •IBM.Function.SYSPLEXDataSharing •IBM.Device.Server.z9-EC-2094.zAAP •IBM.Device.Disk.DS8000-2107  SMP/E REPORT MISSINGFIX command used to identify service not installed Fixcat - 4
  133. 133. 133  The following is an example of the REPORT MISSINGFIX command which can be used to determine which service is needed for coexistence with IMS V14 (run this pointing to an IMS V12 or IMS V13 target zone): SET BOUNDARY (GLOBAL) . REPORT MISSINGFIX ZONES (targetzone) FIXCAT( IBM.Coexistence.IMS.V14 ) .  The following is an example of the REPORT MISSINGFIX command which can be used to determine which service is needed for coexistence with z/OS V2.R2 (run this pointing to an IMS target zone): SET BOUNDARY (GLOBAL) . REPORT MISSINGFIX ZONES (targetzone) FIXCAT( IBM.TargetSystem-RequiredService.z/OS.V2R2 ) . Fixcat - Examples
  134. 134. Hints and Tips for Successful Implementation and Maintenance of IMS Hints & Tips
  135. 135. SMP/E GENERATE command • Used to create JCL to build elements in target libraries from elements in distribution libraries –When run before ANY SMP/E JCLIN processing after sysgen, JCL created will be that to build non-sysgen elements only –When run after ANY SMP/E JCLIN processing after sysgen, JCL created will be to build both non-sysgen elements and sysgen elements  Will encounter errors indicating no DLIB for non IMS macros –Dependent on ACCJCLIN being set up in distribution zone BEFORE processing FMID's –Sample command: SET BDY(targlib) . GENERATE JOBCARD(CNTL,J) REPLACE . ** (NOTE: This sample requires DD CNTL to contain member 'J' which is a sample job card) • Used as part processing of service via ACCEPT BYPASS APPLYCHECK or when target environment needs to be rebuilt from the distribution environment –Not needed when processing using RECEIVE, APPLY, ACCEPT –See Informational APARS II13024 & II14567 (On Demand) SMP/E GENERATE
  136. 136.  User Exit Packaging • Optional user exits now in SDFSSMPL • User exits created as ++SRC type part • Allows line updates during SMP/E processing of service as opposed to complete replacement • Corresponding ++MOD parts (Object Code) NOT shipped • No MOD to LMOD relationships are created during IMS install so SMP/E will not automatically assemble and bind the parts during APPLY processing • If the user creates the MOD to LMOD relationship then SMP/E APPLY processing will automatically assemble and bind these exits • Working toward all having user exits handled the same way • There are issues when a module is part of various load modules some built by SYSGEN and some built in USERMODS as part of a USER Exit –Those using IMS Callable Services (module DFSCSI00) User Exits
  137. 137. DBRC for batch no longer specified in SYSGEN •Default for DBRC in batch and utility regions is YES •Module DFSIDEF0 can be used to set default for batch –Sample provided in IVP –Currently only used to set DBRC default in batch, may be expanded in the future for other parameters –Must be used when DBRC=FORCE is desired Batch and Utility Execution
  138. 138. The following is an for an SMP/E USERMOD for DFSIDEF0: ++ USERMOD (XYZUMOD) . ++ VER (P115) FMID(HMK1400) . ++ JCLIN. //INJCLIN JOB . . . //STEP1 EXEC PGM=IEWL, PARM=(RENT,REFR,XREF,LIST) //SYSPRINT DD SYSOUT=* //SYSLMOD DD DSN=IMS.SDFSRESL,DISP=SHR //SYSUT1 DD UNIT=(SYSDA,SEP=(SYSLMOD,SYSPUNCH)),SPACE=(CYL,(10,1)) //SYSLIN DD * INCLUDE SYSPUNCH(DFSIDEF0) NAME DFSIDEF0(R) ++SRC (DFSIDEF0) . IDEF0 TITLE 'DFSIDEF0 - IMS INSTALLATION DEFAULTS BLOCK' DFSIDEF0 CSECT DFSIDEF TYPE=BEGIN DFSIDEF TYPE=PARM,DBRC=YES ***** DFSIDEF TYPE=PARM,DBRC=NO ***** DFSIDEF TYPE=PARM,DBRC=FORCE DFSIDEF TYPE=END END DFSIDEF0 SMP/E USERMOD for DFSIDEF0
  139. 139. 139 The IMS Application Menu (DFSAPPL) can be used to invoke the growing number of IMS ISPF applications –EX 'IMS.SDFSEXEC(DFSAPPL)' 'HLQ(IMS)' IMS Application Menu Help ------------------------------------------------------------------------------ IMS Application Menu Command ===> Select an application and press Enter. 1 Single Point of Control (SPOC) 2 Manage resources 3 Reserved for future use 4 HALDB Partition Definition Utility (PDU) 5 Syntax Checker for IMS parameters (SC) 6 Installation Verification Program (IVP) 7 IVP Export Utility (IVPEX) 8 IPCS with IMS Dump Formatter (IPCS) 9 Abend Search and Notification (ASN) To exit the application, press F3. ------------------------------------- | Copyright IBM Corp. 2003. All rights reserved. | ---------------------------------------------- Help ------------------------------------------------------------------------------ IMS Application Menu Command ===> Select an application and press Enter. 1 Single Point of Control (SPOC) 2 Manage resources 3 Reserved for future use 4 HALDB Partition Definition Utility (PDU) 5 Syntax Checker for IMS parameters (SC) 6 Installation Verification Program (IVP) 7 IVP Export Utility (IVPEX) 8 IPCS with IMS Dump Formatter (IPCS) 9 Abend Search and Notification (ASN) To exit the application, press F3. Copyright IBM Corp. 2003. All rights reserved.
  140. 140. 140 The IMS Interactive Dump formatter uses IPCS to format IMS Control blocks  REXX EXEC DFSDFSRT is provided in IMS V9 and above to set up the environment •From TSO READY prompt issue: EX ‘ims.SDFSEXEC(DFSDFSRT)’ ‘HLQ(ims)’ –Where ‘ims’ is the high level qualifier for IMS datasets (ex. IMS.V14) –Will allocate SYS1.PARMLIB When used no need to add DD statements to TSO LOGON PROC for IMS dump formatting IMS Interactive Dump Formatting
  141. 141. 141 When DFSDFSRT is invoked under ISPF and the IPCS environment is not set up the following type of messages will be encountered: IMS Interactive Dump Formatter 307 *-* Address LINK "DFSIXQRY" +++ RC(-3) +++ *** .----------------------------------------------------------------------------- |IPCS is not set up correctly. Please EXIT from ISPF and issue this command -| | | | EXEC 'IMS.SDFSEXEC(DFSDFSRT)' ‘HLQ(IMS)' | '----------------------------------------------------------------------------- Solution is to exit out of ISPF back to the TSO READY prompt and the command as shown: EXEC 'IMS.SDFSEXEC(DFSDFSRT)' ‘HLQ(IMS)'
  142. 142. 142 Recommend running with at a minimum the following IMS internal traces: •DL/I •LOCK •SCHD •DISP Recommend setting up using the OPTIONS statement in DFSVSMxx parmlib member •OPTIONS,DL/I=ON,LOCK=ON,SCHD=ON,DISP=ON Can be set up with IMS TRACE command IMS DISPLAY TRACE ALL command can show what traces are in effect Support may request additional traces for specific problem diagnosis If running with RRS have RRST running all the time (i.e RRST=ON) IMS Traces
  143. 143. 143  The prefix name for APARs is now 'PI' (was ‘PM’)  UI for PTF's (was ‘UK’)  One APAR may result in multiple SYSMODS  The prefix name in the actual sysmod(s) will vary depending on the FMID as follows: IRLM IMS 12.1 IMS 13.1 IMS 14.1 --------------------- --------------------------- ------------------------ ------------------------ FMID PRE FMID PRE FMID PRE FMID PRE ------------ ----- ------------- ----- ----------- ----- ---------- ------ HIR2220 Ai HMK1200 Di HMK1300 Di HMK1400 Di JMK1201 Ai JMK1301 Ai JMK1401 Ai JMK1202 Vi JMK1302 Vi JMK1402 Vi HIR2230 Ci JMK1203 Gi JMK1303 Gi JMK1403 Gi JMK1204 Wi JMK1304 Wi JMK1404 Wi JMK1205 Xi JMK1305 Xi JMK1405 Xi JMK1206 Ji JMK1306 Ji JMK1406 Ji JMK131Z Hi JMK141Z Hi where m represents the second character of the APAR prefix • The prefix will be followed by the 5 digit APAR number APAR SYSMOD Naming Conventions
  144. 144. 144  The name of the APAR fix available on DLL/IBMLINK will vary depending on the IMS release as follows: • PIxxxxxz – PI - Prefix name for the APAR – xxxxx - The number for the APAR – z - The suffix will identify the IMS release as follows: H IRLM 2.2 J IRLM 2.3 L IMS 12.1 L IMS 13.1 L IMS 14.1 APAR Naming conventions - Part 2
  145. 145.  The naming conventions for USERMODs will vary depending on the type of USERMOD as follows:  Fixtest for an APAR –FIxxxxxz F - Identifies this as a fixtest I - Indicates the second character of the apar currently being used xxxxx - The number portion of the apar associated with this fixtest z - The version of this fixtest (A=1st, B=2nd, etc.)  Relief for an APAR –RIxxxxxz R - Identifies this as a relief I - Indicates the second character of the apar currently being used xxxxx - The number portion of the apar associated with this fixtest The version of this fixtest (A=1st, B=2nd, etc)  Trap or bypass (no APAR #) –The name will be determined via an internal CLIST USERMOD Naming Conventions on IBMLINK
  146. 146. The naming conventions of the sysmod for usermods will vary depending on the type of usermod as follows:  Fixtest and relief for an APAR –pzxxxxx p - The apar prefix depending on the fmid/compid z - The version of this fixtest/relief (A=1st, B=2nd, etc) xxxxx - The number portion of the apar associated with this fixtest  Trap or bypass (no apar #) –pzxxxxx p - The apar prefix depending on the fmid/compid z - The last character of the fix name supplied by the internal CLIST xxxxx - The number portion supplied by the internal CLIST USERMOD SYSMOD Naming Conventions
  147. 147. Always download and RECEIVE current Enhanced HOLDDATA prior to SMP/E processing •For complete descriptive information relating to Enhanced Holddata see Internet address: http://service.boulder.ibm.com/390holddata.html Be sure to resolve PE's during processing • Contact the IBM Support Center for assistance as needed SMP/E Processing
  148. 148.  Considerations  Zone setup –How to Implement Preventative Service –SYSGENS when systems contain different levels of service –How to Process Emergency Service  SMP/E processing should never be done directly to the libraries being used SMP/E Setup Considerations
  149. 149.  The simplest way to set up SMP/E is: One TLIB, DLIB and set of datasets for each IMS system – Easiest for the human to understand – Uses the most resources (time, dasd, etc) – May not be practical!  What if supporting 100+ systems SMP/E Zone Setup 1 to 1
  150. 150.  A second method is: One TLIB Zone For Each IMS - Common DLIB Zone –Service can be applied to each system selectively –Any SYSMOD in APPLY only status may be regressed via SYSGEN  Re-process any service in APPLY only status after SYSGEN –ACCEPT service once it has been applied to all systems SMP/E Zone Setup Many to 1
  151. 151.  A third method is: One DLIB and TLIB Zone for many systems –Implement to all systems at one time or manage outside of SMP/E Most complex Uses less computer resources SMP/E Zone setup 1 ZONE
  152. 152.  SMP/E APPLY encounters one of the following warning messages: GIM43401W aaaaaaaa bbbbbbbb IN SYSMOD cccccccc WAS NOT INSTALLED IN ANY TARGET LIBRARY GIM44402W aaaaaaaa WAS NOT ASSEMBLED FOR bbbbbbbb cccccccc IN FOR aaaaaaaa No Target Library
  153. 153. IMS APARs and USERMODs prior to IMS V14 only PRE SYSMODS with code dependencies. The PRE will specify the APAR as opposed to the PTF May cause regression messages to be encountered when processing IMS supplied APARs and USERMODs The following are samples of some of the messages that may be received: GIM38201 THERE IS A MODID ERROR FOR aaaaaaaa ENTRY bbbbbbbb IN SYSMOD ccccccc GIM38202 THERE IS A MODID ERROR FOR ASSEMBLY aaaaaaaa FOR bbbbbbbb ENTRY ccccccc IN SYSMOD dddddddd GIM31901 SYSMOD aaaaaaa DOES NOT SPECIFY bbbbbbb ON THE PRE OR SUP OPERAND. bbbbbbb IS THE RMID FOR ccccccc dddddddd THAT IS CURRENTLY INSTALLED GIM31902 SYSMOD aaaaaaa DOES NOT SPECIFY bbbbbbb ON THE PRE OR SUP OPERAND. bbbbbbb IS THE UMID FOR ccccccc dddddddd THAT IS CURRENTLY INSTALLED  Messages of this type are expected, but each one must be analyzed APAR/USERMOD SMP/E Regression
  154. 154.  Determine if regression will actually take place by doing the following: Look at the prereq on the sysmod, determine if the prereqs match the PTF Look at the code to see if there is any dependencies/intersections Contact the support center for assistance  If no regression will occur ignore these messages (specify BYPASS ID ) APAR/USERMOD SMP/E Regression - Cont
  155. 155. Acknowledgements and Disclaimers Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. © Copyright IBM Corporation 2015. All rights reserved. •U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM, the IBM logo, ibm.com, and IMS are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml Other company, product, or service names may be trademarks or service marks of others.
  156. 156. Thank You

×