IBM Support

Upgrade ODMP710, Subset H272711

  Preventive Service Planning

Upgrade ODMP710, Subset H272711


Upgrade ODMP710, Subset H272711:

This subset contains installation information for ODMPBASE390
Version 7, Release 1, Modification 0.


Change Summary

DATE LAST CHANGED SECTION 1. 03/12/18 INSTALLATION INFORMATION 2. 02/01/29 DOCUMENTATION CHANGES 3. 07/12/18 GENERAL INFORMATION 4. 10/07/21 SERVICE RECOMMENDATIONS 5. 07/07/02 CROSS PRODUCT DEPENDENCIES


Service Recommendation Summary

DATE APAR PTF VOLID COMMENTS 13 10/07/21 PM07633 UK55884 1004 HIPER ARSDB -VI IMPORT COMMAND 12 10/02/15 PM05593 UK54280 1002 HIPER ARSZIMIG REPORT DELETES 11. 09/02/27 PK52978 UK30870 0711 SECONDARY SPACE ALLOCATION ON 10 07/10/29 PK52840 UK30677 0710 HIPER ARSEXOAM/ARSEXPIR MAY 9 05/07/04 PK06182 UK05071 0507 HIPER ANNOTATIONS MAY BE 8 05/05/19 PK05639 UK03540 0505 HIPER BAG RECORD LOST WHEN 7 05/04/25 PK04109 UK02718 0504 HIPER AFP WITH OS/390 INDEXER 6 04/12/06 PQ93485 UQ93052 0409 HIPER OAM ERROR DURING UNLOAD 5. 04/12/02 PQ95156 UQ95494 0411 ARSZIMIG FAILS WITH SQLCODE -803 4 04/12/01 PQ89802 UQ90658 0407 HIPER HAVE ARSLOAD RESTRICT 3 04/01/12 PQ80768 UQ83879 0401 HIPER In a z/OS, 64 bit 2 02/03/06 PQ58254 UQ63718 0203 HIPER ARSDOC -X GETS "THE SERVER 1 01/10/15 PQ52842 UQ58458 0110 HIPER DEVELOPMENT APAR


Installation Information

This section contains changes to the product's Program Directory. 1. 03/12/18 The ++HOLD information for PTF UQ83223 discusses the need to define a new DDDEF for library SEZARNT1. This library must be added to the list of libraries identified in section 6.1.3 SMP/E CALLLIBS Processing in the 'Program Directory for IBM CM OnDemand For z/OS and OS/390, Version 7.1.1'. Please refer to the ++HOLD information for instructions on defining the SEZARNT1 library.


Documentation Changes

This section outlines major errors in the product's published documentation. 5. 02/01/29 Indexing Reference SC27-1375-00 In the "About this publication" section, under the "How this publication is organized" heading, add an additional bullet: - "Part 5. OS/390 Indexer reference" describes how to use the OS/390 Indexer to specify index data for line print data A new Part 5 is added (the existing "Part 5. Appendixes" becomes "Part 6. Appendixes"). Part 5. OS/390 Indexer reference This part of the book provides information about the OS/390 Indexer process. You can use the OS/390 Indexer to extract index data from and generate index data about data sets which contain line data. Chapter 26. Overview Note: Statements in this chapter about the OS/390 Indexer in OS/390 apply equally to the OS/390 Indexer in the z/OS environment. The OS/390 Indexer extracts indexes and stores documents all in one pass of reading the input line print data. The OS/390 Indexer indexes reports based on the organization of the data in the report. The OS/390 Indexer processes two input sources: - Indexing parameters that specify how the data should be indexed. You can create the indexing parameters when you define an OnDemand application. The parameters are of the same form as used by ACIF. - The print data stream. The OS/390 Indexer indexes input data based on the organization of the data: - Document organization. For reports made up of logical items, such as statements, policies, and invoices. The OS/390 Indexer can generate index data for each logical item in the report. - Report organization. For reports that contain line data with sorted values on each page, such as a transaction log or general ledger. The OS/390 Indexer can divide the report into groups of pages and generate index data for each group of pages. Before you can index a report with the OS/390 Indexer, you need to create a set of indexing parameters. The indexing parameters describe the physical characteristics of the input data, identify where in the data stream that the OS/390 Indexer can locate index data, and provide other directives to the OS/390 Indexer. Collecting the information needed to develop the indexing parameters requires a few steps. For example: 1. Examine the input data to determine how users use the report, including what information they need to retrieve a report from the system (indexing requirements). 2. Create parameters for indexing. You run the OS/390 Indexer as part of the OnDemand load process with the ARSLOAD program. The OnDemand application retrieves the indexing parameters from the OnDemand database and uses the parameters to process the input data. The OS/390 Indexer can logically divide reports into individual items, such as statements, policies, and bills. You can define up to 32 index fields for each item in a report. Indexing Concepts Indexing parameters include information that allow the OS/390 Indexer to identify key items in the print data stream so they can be extracted from the report and stored in the OnDemand database. OnDemand uses these index values for efficient, structured search and retrieval. You specify the index information that allows the OS/390 Indexer to segment the data stream into individual items called groups. A group is a collection of one or more pages. You define the bounds of the collection, for example, a bank statement, insurance policy, phone bill, or other logical segment of a report file. A group can also represent a specific number of pages in a report. For example, you might decide to segment a 10,000 page report into groups of 100 pages. The OS/390 Indexer creates indexes for each group. Groups are determined when the value of an index changes (for example, account number) or when the maximum number of pages for a group is reached. An indexing parameter is made up of an attribute name (for example, Customer Name) and an attribute value (for example, Earl Hawkins). The parameters include pointers that tell ACIF where to locate the attribute information in the data stream. For example, the tag Account Number with the pointer 1,21,16 means the OS/390 Indexer can expect to find Account Number values starting in column 21 of specific input records. The OS/390 Indexer collects 16 bytes of information starting at column 21 and adds it to a list of attribute values found in the input. For each group identified by the OS/390 Indexer, its set of index values are stored by the OnDemand load process into the OnDemand database. The OS/390 Indexer Parameters The OS/390 Indexer process uses standard ACIF parameters, as described in Part 1 of this document, to provide the segmentation and indexing instructions. This allows for the use of the Indexing Wizard, which is part of the Administration Client, for defining the parameters. The following subset of ACIF parameters are recognized by the OS/390 Indexer process. Refer to Chapter 3 of this document for detailed descriptions of these parameters. - TRIGGER - Identifies locations and string values required to uniquely identify the beginning of a group and the locations and string values of fields used to define indexes. You must define at least one trigger and can define up to eight triggers. - INDEX - Identifies the index name and the field on which the index is based. You must define at least one index parameter. You can define up to 32 index parameters. Notes for index usage: Only one field can be specified for each index. Only group and grouprange indexes are supported. Grouprange indexes can only be used with indexes one or two. Group indexes can be used with all 32 indexes. - FIELD - Identifies the location of index data. You must define at least one field. You can define up to 32 fields. Neither default nor constant field values are supported. - GROUPMAXPAGES - Determines the maximum number of pages to be put into a group. This allows the OS/390 Indexer to logically segment a large report into groups of pages and create indexes for each group. You can specify a number from 1 and 9999. Use this parameter when specifying a grouprange index. - FILEFORMAT - Used by the OS/390 Indexer to identify the logical record length of the input file. Only the record format of this parameter is supported: FILEFORMAT=RECORD,n where n is the logical record length value. Other ACIF parameters can be specified, but they are ignored by the OS/390 Indexer. Indicate When to Use the OS/390 Indexer In the Administration Client, when defining the Application, on the Indexer Information tab, the field labeled Indexer should be set to the value of OS/390 to indicate to the ARSLOAD application that the OS/390 Indexer process is to be used to capture this report. When using JCL to execute the ARSLOAD program to capture reports, use the DD:ddname parameter in the parameter list for ARSLOAD to indicate which ddname points to the input report file being captured. 4. 01/11/05 Migration Guide LY37-3746 SUMMARY OF CHANGES -- Changes associated with APAR PQ53865 / PTF UQ59395 - At the beginning of "Chapter 2. Migration Steps" is an expanded list of prerequisites - In "Step 3 -- Identifying Reports Used in Multiple Folders" the V2.1 PTF providing the IODMG07A utility is referenced - In "Step 12 -- Preparing to Capture Production Reports in OD z/OS" the program ARSMIGRT is introduced - The new section "Compatibility Mode Between V7.1 and V2.1" is added CHAPTER 2. MIGRATION STEPS Before you can begin migrating your data from V2.1 to V7.1, you must have the following in place: - PTFs UQ58213 and UQ58214 installed as part of OnDemand for OS/390 V2.1 - OnDemand for z/OS and OS/390 V7.1 installed, including all available PTFs - The V7.1 Administration Client installed on a Windows workstation, with the host server defined - In addition, the OD/390 V2.1 Server Feature J07L211 is a prerequisite for using the V7.1 compatability mode. STEP 3 -- IDENTIFYING REPORTS USED IN MULTIPLE FOLDERS If a folder being migrated contains a report which is used in another folder(s), you should also migrate this (these) other folder(s) at the same time. Program IODMG07A, available via OD/390 V2.1 PTF UQ58213, can assist in identifying these conditions. Run this program with the list of folders you want to migrate. It will return to you a list of all additional folders which should be migrated at the same time due to the same report(s) being used in these other folders. STEP 12 -- PREPARING TO CAPTURE PRODUCTION REPORTS IN OD Z/OS When you are satisfied that the application, application group, folder, etc. data meets your needs, then you can prepare for capturing production reports in OD z/OS. If you have OD/390 capture steps in your production JCL, this will need to be modified to use the OD z/OS capture process. If you are using the OD/390 Dynamic Capture Subsystem, you will need to modify the SPOOL parameters used, to direct the SPOOL files to the OD z/OS capture process. In addition, you must run the ARSZFLDM and ARSMIGRT programs. The ARSZFLDM program will 1. Set a flag in the OD/390 CDFDT table to identify which migrated folders are now being captured in OD z/OS (that is, the reports being mapped to this folder are being captured in OD z/OS.) 2. Create an output file to be used as input to the ARSMIGRT program to set the Application Group last_doc_date and migr_srvr fields. The OD/390 CDFDT flag does two things: - When an OD z/OS client builds a list of folders to present to the user, it tells the OD/390 system to exclude flagged folders from the list returned to the client. Otherwise, duplicate folder definitions will appear. - The OD/390 Batch Capture program (IODBSTOR) will not allow a report assigned to a migrated folder to be captured. This ensures you don't accidentally capture reports into the wrong system. The ARSMIGRT program reads as input the output file generated by the ARSZFLDM program. This information, along with input parameters, provides for updating the ARSAG table values of last_doc_date and migr_srvr. These values identify the last posting date stored for that application in the V2.1 region identified by the migr_srvr value. Refer to the usage notes in the JCL of this job for further instructions. COMPATIBILITY MODE BETWEEN V7.1 AND V2.1 A V7.1 client can be used to access folders defined on a V7.1 server and on a V2.1 server. For this to work, an entry must be provided in the ARS.CFG file within the V7.1 server. The format of this entry is: ARS_MIGR_SERVERS=migr_srvr host_name protocol port_number unified_login v2_server where - "migr_srvr" is a label used to identify the V2.1 server (a suggestion is to use the V2.1 CICS region name). This value MUST match that used in the ARSMIGRT program. - "host_name" is either the DNS Host Name or the IP Address of the V2.1 Server - "protocol" should be set to the value 2, which denotes TCP/IP - "port_number" is the port associated with the V2.1 Listener - "unified_login" identifies whether the server accepts a unified login. Set this to 0, signifying NO. - "v2_server" identifies whether this server is a V2.1 server or not. Set this to 1, signifying YES. A typical entry in the ARS.CFG file might be: ARS_MIGR_SERVERS=OD210PRD 9.91.121.31 2 3015 0 1 3. 01/11/01 Text Below ###################################################################### # (C) COPYRIGHT 2000-2001 IBM Corporation. All rights reserved. # # ================================================================== # # # This file contains the initial configuration properties for the # WebSphere Application Server for OS/390 version 3.02. # # This properties file is used during installation verification # of the Application Server. # # For a description of the individual properties, see the # WebSphere Application Server Planning, Installing, Using Guide. # # ================================================================== # # # # appserver.version # # Version number used to verify this is the correct version # of configuration file. This property is required. # # appserver.version=3.02.0 # #--------------------------------------------------------------------# # # appserver.usesystemclasspath=true|false # # appserver.usesystemclasspath=false # #--------------------------------------------------------------------# # # appserver.libpath # # appserver.libpath=/p3odwek/html/cgi-bin # #--------------------------------------------------------------------# # # appserver.classpath # # # appserver.classpath= first line for java 118 appserver.classpath=/usr/lpp/db2/db2610/classes/db2jdbcclasses.zip:/usr/ pp/java # #--------------------------------------------------------------------# # # appserver.name # # appserver.name=defaultServletEngine # #--------------------------------------------------------------------# # # appserver.jvmpropertiesfile # # appserver.jvmpropertiesfile=/p3odwek/default_global.properties # #--------------------------------------------------------------------# # # appserver.loglevel INFO|ERROR|WARNING # # appserver.loglevel=INFO # #--------------------------------------------------------------------# # # appserver.logdirectory=directory_name | STDOUT # # appserver.logdirectory=/p3odwek/logs appserver.tracelevel=*=all=enabled service.plugin.tracelevel=MOST # #--------------------------------------------------------------------# # # appserver.workingdirectory # # appserver.workingdirectory=/p3odwek/html/tmp # #--------------------------------------------------------------------# # # appserver.configviewer # # appserver.configviewer= #--------------------------------------------------------------------# # # appserver.jspbasehrefadd=true|false # # If set to true, a base HREF tag will be included in the # java code generated from a jsp. The default is true. # appserver.jspbasehrefadd=true # #--------------------------------------------------------------------# # # objectleveltrace.enabled=true|false # # objectleveltrace.enabled=false # # # ================================================================== # # # Session Settings # # ================================================================== # # # session.enable=true|false # # session.enable=true # #--------------------------------------------------------------------# # # session.urlrewriting.enable=true|false # # session.urlrewriting.enable=false # #--------------------------------------------------------------------# # # session.cookies.enable=true|false # # session.cookies.enable=true # #--------------------------------------------------------------------# # # session.protocolswitchrewriting.enable=true|false # # session.protocolswitchrewriting.enable=false # #--------------------------------------------------------------------# # # session.cookie.name # # session.cookie.name=sesessionid # #--------------------------------------------------------------------# # # session.cookie.comment # # session.cookie.comment=servlet Session Support # #--------------------------------------------------------------------# # # session.cookie.maxage # # session.cookie.maxage=-1 # #--------------------------------------------------------------------# # # session.cookie.path # # session.cookie.path= # #--------------------------------------------------------------------# # # session.cookie.secure=true|false # # session.cookie.secure=false # #--------------------------------------------------------------------# # # session.invalidationtime # # session.invalidationtime=1800000 # #--------------------------------------------------------------------# # # session.tablesize # # session.tablesize=1000 # #--------------------------------------------------------------------# # # session.tableoverflowenable=true|false # # session.tableoverflowenable=false # #--------------------------------------------------------------------# # # session.dbenable=true|false # # session.dbenable=false # #--------------------------------------------------------------------# # # session.dbjdbcpoolname # # session.dbjdbcpoolname=SessionJDBCConnectionPool # #--------------------------------------------------------------------# # # session.dbtablename # # session.dbtablename= # #--------------------------------------------------------------------# # # session.domain # # session.domain= # # # ================================================================== # # # Connection Pool Definitions # # ================================================================== # # # jdbcconnpool.default_jdbcpool.waitforconnectiontimeoutmilliseconds=30000 jdbcconnpool.default_jdbcpool.idleconnectiontimeoutmilliseconds=120000 jdbcconnpool.default_jdbcpool.inuseconnectiontimeoutmilliseconds=120000 jdbcconnpool.default_jdbcpool.jdbcdriver=ibm.sql.DB2Driver jdbcconnpool.default_jdbcpool.databaseurl= jdbcconnpool.default_jdbcpool.datasourcename=default_pool_datasource # #--------------------------------------------------------------------# # # jdbcconnpool.SessionJDBCConnectionPool.minconnections=10 jdbcconnpool.SessionJDBCConnectionPool.maxconnections=40 jdbcconnpool.SessionJDBCConnectionPool. waitforconnectiontimeoutmilliseconds=3000 jdbcconnpool.SessionJDBCConnectionPool. idleconnectiontimeoutmilliseconds=120000 jdbcconnpool.SessionJDBCConnectionPool. inuseconnectiontimeoutmilliseconds=-1 jdbcconnpool.SessionJDBCConnectionPool.jdbcdriver=ibm.sql.DB2Driver jdbcconnpool.SessionJDBCConnectionPool.databaseurl= jdbcconnpool.SessionJDBCConnectionPool.connectionidentity=server # # ================================================================== # # # Virtual Host settings # # ================================================================== # # # host.<virtual_hostname>.alias=<hostname>|localhost # # host.default_host.alias=localhost # #--------------------------------------------------------------------# # # host.<virtual_hostname>.mimetypefile # # host.default_host.mimetypefile= # # # ================================================================== # # # Deployed Web Application Settings # # ================================================================== # # # # deployedwebapp.<appname>.host= # deployedwebapp.<appname>.rooturi= # deployedwebapp.<appname>.classpath= # deployedwebapp.<appname>.documentroot= # deployedwebapp.<appname>.autoreloadinterval= # deployedwebapp.<appname>.authresource= # deployedwebapp.<appname>.filter.<MIME_type>=<servletname> # # ================================================================== # # # Web Application Settings # # ================================================================== # # # # # webapp.<appname>.description= # webapp.<appname>.servletmapping= # webapp.<appname>.jspmapping= # webapp.<appname>.jsplevel= # webapp.<appname>.filemapping= # webapp.<appname>.attributes= # webapp.<appname>.errorpagemapping= # # # ================================================================== # # # Servlet Settings # # ================================================================== # # # # # webapp.<appname>.servlet.<servletname>.autostart= # webapp.<appname>.servlet.<servletname>.code= # webapp.<appname>.servlet.<servletname>.initargs= # webapp.<appname>.servlet.<servletname>.servletmapping= # # # # # # ================================================================== # # # The following defines the examples web application used for # OD WEK. # # ================================================================== # deployedwebapp.ODwek.host=default_host deployedwebapp.ODwek.rooturi=/ deployedwebapp.ODwek.classpath=/p3odwek/html/servlets deployedwebapp.ODwek.documentroot=/p3odwek/html/scripts # deployedwebapp.ODwek.dispatchthreadchecking=disabled webapp.ODwek.jsplevel=1.0 webapp.ODwek.jspmapping=*.jsp webapp.ODwek.filemapping=/ #webapp.ODwek.servletmapping=/servlet webapp.ODwek.errorpagemapping=ODerror.jsp #webapp.ODwek.servlet.errorReport.code=com.ibm.servlet.engine. webapp.DefaultErro #webapp.ODwek.servlet.errorReport.servletmapping=/ErrorReporter/ webapp.ODwek.servlet.ArsWWWServlet.autostart=false webapp.ODwek.servlet.ArsWWWServlet.code=com.ibm.edms.od.ArsWWWServlet webapp.ODwek.servlet.ArsWWWServlet.initargs=ConfigDir=/p3odwek/html/ cgi-bin webapp.ODwek.servlet.ArsWWWServlet.servletmapping=/ArsWWWServlet # ================================================================== # # # The following defines the examples web application used for # installation verification. # # ================================================================ # deployedwebapp.examples.host=default_host deployedwebapp.examples.rooturi=/webapp/examples deployedwebapp.examples.classpath=$was_install_root$ /AppServer/hosts/default_hos deployedwebapp.examples.documentroot=$was_install_root$ /AppServer/hosts/default webapp.examples.jspmapping=*.jsp webapp.examples.filemapping=/ webapp.examples.servlet.simpleJSP.code=SimpleJSPServlet webapp.examples.servlet.simpleJSP.servletmapping=/simpleJSP webapp.examples.servlet.simpleJSP.servletmapping=/simpleJSP.servlet webapp.examples.servlet.showCfg.code=com.ibm.servlet. .engine.config.ServletEngine webapp.examples.servlet.showCfg.servletmapping=/showCfg 2. 01/10/31 OSA/SF parts sent to Boe. in support of the 1998-08-06 PQ16071 ESP build ---------------------------------------------------------------------- New part notifications ---------------------------------- IOAKMCHK TC3$JEFC is new to OSA/SF IOAQKMCH TPS$JEFC is new to OSA/SF IOAKOAT TC3$JEFC is new to OSA/SF IOAQKOAT TPS$JEFC is new to OSA/SF IOASWTOW TPS$JEFC is new to OSA/SF IOAQSWTW TPS$JEFC is new to OSA/SF * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * THE FILES YOU SHOULD RECEIVE ARE: The APAR text file ------------------------------------------------------- PQ16071 APAR The following are updated LNKSKEL files (used to build various phases) ------------------------------------------------------- <As sent to you as> <shipped as> IOAMAIN CMD$JEFC Not shipped; used as LNKSKEL IOAMAIN to build IOAMAIN phase in Boe. The following are updated text decks (used to build the IOAEREXX phase) ------------------------------------------------------- <As sent to you as> <shipped as> IOAEAPPC TC3$JEFC not shipped, used to build IOAEREXX phase IOAEC TC3$JEFC " " IOAEPROC TC3$JEFC " " IOAEREXX TC3$JEFC " " The following are updated text decks (used to build the IOAMAIN phase) ------------------------------------------------------- <As sent to you as> <shipped as> IOAAIRPT TC3$JEFC not shipped, used to build IOAMAIN phase IOACAPPC TC3$JEFC " " IOACLIST TC3$JEFC " " IOACLOGR TC3$JEFC " " IOACMAIN TC3$JEFC " " IOACMISC TC3$JEFC " " IOACONSL TC3$JEFC " " IOACTRAC TC3$JEFC " " IOACTRVU TC3$JEFC " " IOADASST TC3$JEFC " " IOADCHSC TC3$JEFC " " IOADCMDS TC3$JEFC " " IOADFILE TC3$JEFC " " IOADQURY TC3$JEFC " " IOADSETF TC3$JEFC " " IOADUTIL TC3$JEFC " " IOAINST TC3$JEFC " " IOAIPORT TC3$JEFC " " IOAKCFG TC3$JEFC " " IOAKCMDE TC3$JEFC " " IOAKDMGR TC3$JEFC " " IOAKDVT TC3$JEFC " " IOAKEXM TC3$JEFC " " IOAKEXOP TC3$JEFC " " IOAKFCT TC3$JEFC " " IOAKFILE TC3$JEFC " " IOAKICHN TC3$JEFC " " IOAKIML TC3$JEFC " " IOAKMCHK TC3$JEFC " " IOAKMISC TC3$JEFC " " IOAKMODS TC3$JEFC " " IOAKOAT TC3$JEFC " " IOAKPDAT TC3$JEFC " " IOAKQRY TC3$JEFC " " IOAKROAT TC3$JEFC " " IOAKSNAS TC3$JEFC " " IOAKSPRM TC3$JEFC " " IOAKSTOP TC3$JEFC " " IOAKSTRT TC3$JEFC " " IOAKSYNC TC3$JEFC " " IOAKUTIL TC3$JEFC " " IOANNVA TC3$JEFC " " IOASOPF TC3$JEFC " " IOASREGN TC3$JEFC " " IOASTOP TC3$JEFC " " IOAZSCCM TC3$JEFC " " IOAACME TPS$JEFC " " IOAACOMM TPS$JEFC " " IOADPLX TPS$JEFC " " IOAQACME TPS$JEFC " " IOAQACOM TPS$JEFC " " IOAQAIRT TPS$JEFC " " IOAQCAPP TPS$JEFC " " IOAQCLIS TPS$JEFC " " IOAQCLOG TPS$JEFC " " IOAQCMAI TPS$JEFC " " IOAQCMIS TPS$JEFC " " IOAQCONS TPS$JEFC " " IOAQCTRA TPS$JEFC " " IOAQCTRV TPS$JEFC " " IOAQDASS TPS$JEFC " " IOAQDCHS TPS$JEFC " " IOAQDCMD TPS$JEFC " " IOAQDFIL TPS$JEFC " " IOAQDPLX TPS$JEFC " " IOAQDQUR TPS$JEFC " " IOAQDSET TPS$JEFC " " IOAQDUTI TPS$JEFC " " IOAQINST TPS$JEFC " " IOAQIPOR TPS$JEFC " " IOAQKCFG TPS$JEFC " " IOAQKCMD TPS$JEFC " " IOAQKDMG TPS$JEFC " " IOAQKDVT TPS$JEFC " " IOAQKEXM TPS$JEFC " " IOAQKEXO TPS$JEFC " " IOAQKFCT TPS$JEFC " " IOAQKFIL TPS$JEFC " " IOAQKICH TPS$JEFC " " IOAQKIML TPS$JEFC " " IOAQKMCH TPS$JEFC " " IOAQKMIS TPS$JEFC " " IOAQKMOD TPS$JEFC " " IOAQKOAT TPS$JEFC " " IOAQKPDA TPS$JEFC " " IOAQKQRY TPS$JEFC " " IOAQKROA TPS$JEFC " " IOAQKSNA TPS$JEFC " " IOAQKSPR TPS$JEFC " " IOAQKSTO TPS$JEFC " " IOAQKSTR TPS$JEFC " " IOAQKSYN TPS$JEFC " " IOAQKUTI TPS$JEFC " " IOAQNNVA TPS$JEFC " " IOAQSOPF TPS$JEFC " " IOAQSREG TPS$JEFC " " IOAQSTOP TPS$JEFC " " IOAQSUKB TPS$JEFC " " IOAQSWTW TPS$JEFC " " IOAQSYSS TPS$JEFC " " IOAQZSCC TPS$JEFC " " IOASUKBD TPS$JEFC " " IOASWTOW TPS$JEFC " " IOASYSS TPS$JEFC " " I-book parts that should be put into ICCF library 59 ------------------------------------------------------------------ <As sent to you as> <shipped as> <note> IOAATM2 MAK$JEFC IOAATM2.I put into ICCF library 59 IOACMD MAK$JEFC IOACMD.I " " " IOAINX MAK$JEFC IOAINX.I " " " IOAMAIN MAK$JEFC IOAMAIN.I " " " IOAOSHRA MAK$JEFC IOAOSHRA.I " " " IOAOSHRT MAK$JEFC IOAOSHRT.I " " " Z-book parts --------------------------------------- <As sent to you as> <shipped as> IOAATM2 SMP$JEFC IOAATM2.Z IOAINX SMP$JEFC IOAINX.Z IOAMAIN SMP$JEFC IOAMAIN.Z IOAOSHRA SMP$JEFC IOAOSHRA.Z IOAOSHRT SMP$JEFC IOAOSHRT.Z REXX procs ------------------------------------------------------- <As sent to you as> <shipped as> <note> IOACMD REX$JEFC IOACMD.O renamed to IOACMD.PROC IOAINATM REX$JEFC IOAINATM.O renamed to IOAINATM.PROC IOASNAVS REX$JEFC IOASNAVS.O renamed to IOASNAVS.PROC Images ------------------------------------------------------- <As sent to you as> <shipped as> - - NONE - - ATM image and configuration files ------------------------------------------------------- <As sent to you as> <shipped as> IOAACDSF BIN$JEFC - ATM LE default config file IOAACDSF O IOAATMLE BIN$JEFC - ATM image IOAATMLE O Files shipped on the host, used by OS/2 and Software Installer -------------------------------------------------------------- <As sent to you as> <shipped as> IOABPKGB BIN$JEFC - ASCII SI/2 package file IOABPKGB W IOABPKGJ BIN$JEFC - ASCII SI/2 package file(Japanese support) IOABPKGJ W IOAGDLL BIN$JEFC - SI/2 packed file (contains OS/2 GUI DLLs) IOAGDLL W IOAGEXE BIN$JEFC - SI/2 packed file (contains OS/2 GUI EXEs) IOAGEXE W IOAGHLP BIN$JEFC - SI/2 packed file (contains OS/2 GUI HLPs) IOAGHLP W IOAGRECV BIN$JEFC - ASCII OS/2 REXX install/update front-end IOAGRECV W IOAIEXTS BIN$JEFC - SI/2 file used for install IOAIEXTS W IOAIHPLB BIN$JEFC - SI/2 file used for install IOAIHPLB W IOAIMSG BIN$JEFC - SI/2 file used for install IOAIMSG W IOAINSTS BIN$JEFC - SI/2 file used for install IOAINSTS W IOAIPII BIN$JEFC - SI/2 file used for install IOAIPII W IOAIPRCS BIN$JEFC - SI/2 file used for install IOAIPRCS W IOAIUPCK BIN$JEFC - SI/2 file used for install IOAIUPCK W 1. 01/10/02 Configuration Guide GC27-1373 page 6 - The host printing feature works only with Infoprint. page 7 - In figure 1 "Optional Object Server with Database Manager" should just be "Optional Object Server". page 17 - arsprt is not a file and should be removed from table 7. page 18 - on all of the path statments "/user/" should be "/usr/". page 21 - the 3rd paragraph should read: " To change the ARS.CFG file, log on as the root user or other user with apropriate permissions. Change the /usr/lpp/ars/confi directory. Make a backup copy of the file provided by IBM. Edi the ARS.CFG file with a standard editor. page 21 - ARSTSPAC is not a program, is is a JCL member used to define a DB2 tablespace. The name of the tablespace as defined by this JCL must agree with the tablespace name in file ARS.CFG, in field ARS_DB_TABLESPACE. page 25 - For listed files /arscache/cache1/ through .../cache5/, each of these files is its own mount point. Replace the last 2 sentences on this page with: " JCL member ARSTSPAC sets up tablespaces; member ARSDB2 sets up the tables." Page 29 and all applicable pages - Note that program ARSSOCKD is the server program for a library server; ARSOBJD is the server program for an object server. Introduction and Planning Guide GC27-1438 No changes. Administrator's Guide SC27-1374 No changes. Indexing Reference SC27-1375 No changes IBM Content Manager OnDemand for z/OS Web Enablement Kit Installation and Configuration Guide SC27-1376 No changes. Distribution Facility SC27-1377 For changes to this related documentation refer to: IBM OnDemand Distribution Facility Version 7 (CM OnDemand ODF) Release 1, Modification Level 0, Program Number 5655-H39 for the following: FMID : J272712 5852 IBM OnDemand Distribution Facility Message Reference SC27-1379 No changes. Migration Guide LY37-3746 Customers migrating from OD/390 v2.1 to OD z/OS 7.1 should apply PTF UQ58213 for Step 3 of the migration process, as documented on page 5 of the OnDemand for z/OS and OS/390 Migration Guide, form number "LY37-3746-00." The Migration Guide LY37-3746 can be obtained from the OD/390 Secure FTP Site at: ftp://od390cst@service2.boulder.ibm.com/ To obtain access to this site, send an email requesting access to: od390@us.ibm.com


General Information

This section contains general information, i.e. SYSGEN hints/tips. 9. 07/12/18 INTERDEPENDENT PRODUCT- TSM 5.4 PROBLEM- (PK55924) ARS0020E ARSSOCKD SM ERROR: RC = 610 USERS AFFECTED- All users of TSM 5.4 as an OnDemand storage manager RECOMMENDATION- Use local fix described in PK55924 8. 07/05/15 Installation Considerations for OD MP 7.1.2.9 Rollup. Description: PTFs UK24971 (Base product) and UK24972 (ODF) include the fixpacks for OD MP 7.1.2.8 and 7.1.2.9. - These fixes require upgrades to OnDemand database tables, and once the data base tables upgrade process has begun the PTFs may not be RESTORED. - Before PTFs UK24971 and UK24972 are APPLIED, table ARSAPP must be analyzed to verify the table upgrades may be successfully performed. The SQL to perform this verification is included in Recommendation: below. - Users Affected: All OnDemand for z/OS and OS/390 customers installing PTFs UK24971 and UK24972 (APAR PK39482). - Recommendation: Upgrading DB2 Content Manager OnDemand to Version 7.1.2.9 or higher requires changes to the ARSUSER, ARSAG, ARSAPP, ARSLOAD, ARSSEG, and ARSSYS tables before the OnDemand Server can be used. Additional tables and tablespaces must be created for exploitation in possible future enhancements. - If the changes to the tables are not made, the following message will be issued, and the server will terminate: - ARS0013E ARSSOCKD DB ERROR: DB2 FOR OS/390 ODBC DRIVER SQLSTATE=HY002 ERRLOC=2:210:8 -- SQLSTATE=HY002, SQLCODE=-99999, FILE=ARSAG.C, LINE=4563 - The SQL below MUST be used to verify the ARSAPP table may be successfully upgraded. Prior to APPLYing this APAR, run the following SQL to determine if any of the ARSAPP columns are currently too big to fit in the updated tables: - SELECT NAME, AGID FROM ARSUSER.ARSAPP WHERE LENGTH(FIXED_VIEW) > 10698 OR LENGTH(INDEXER) > 10698 OR LENGTH(PREPROCESSOR) > 10698; - If any rows are returned, DO NOT APPLY PTF UK24971. The columns will need to be reduced in size before PTF UK24971 is applied. Contact IBM Support for assistance. - Upgrading customers will need to perform the following after APPLYing PTF UK24971. Customers will need to make sure they have a valid database backup and recovery plan prior to performing this procedure: - 1. Customize and execute the ARSTSPCC member of SARSINST to create the additional tablespaces. 2. Stop the OnDemand Server. 3. Backup the OnDemand Database or make sure they have a current backup. 5. Run "arsdb <-I instance_name> -vx ARSAPP" 6. Run "arsdb <-I instance_name> -vd ARSSYS" 7. Run "arsdb <-I instance_name> -vd ARSAPP" 8. Run "arsdb <-I instance_name> -vc ARSSYS" 9. Run "arsdb <-I instance_name> -vc ARSAPP" 10. Run "arsdb <-I instance_name> -vi ARSSYS" 11. Run "arsdb <-I instance_name> -vi ARSAPP" 12. Run "arsdb <-I instance_name> -vu" 13. Start the OnDemand Server - Customers installing a new instance of the libraries and databases for OnDemand for z/OS and OS/390 V7 should install PTF UK24971 before running the database creation job ARSTSPAC. This will eliminate the need to execute the ARSTSPCC job and "arsdb" commands to update the customized tablespaces and tables. 7. 05/11/22 Customers migrating from OnDemand Version 2 should APPLY UK09169. This prevents storage node nodeids from going negative, which occurs when too many storages nodes are created. 6. 04/05/04 SMP/E APPLY Considerations for PTF UQ87838 (APAR PQ84533) Description: Before installing PTF UQ87838 for APAR PQ84533, all prior maintenance to OnDemand for z/OS and OS/390 V7 should be ACCEPTed. If PTF UQ81830 has been applied, it must be ACCEPTed. If PTF UQ87838 is applied with PTF UQ81830 in applied status and not ACCEPTed, PTF UQ87838 will fail with an unresolved external reference for module ARSZSTOB in the link edit for load module ARSZFLDG. If PTF UQ85534 is in the group of PTFs being applied, it will receive the link edit failure. Users Affected: All with OnDemand for z/OS and OS/390 installing PTF UQ87838 for APAR PQ84533. Recommendation: The general recommendation for OnDemand for z/OS and OS/390 V7 is to ACCEPT prior maintenance before beginning the next maintenance installation. This process is required if PTF UQ81830 was installed in the prior maintenance. PTF UQ81830 introduced a new module (ARSZSTOB) that was added to the ARSZFLDG load module in UQ87838. If UQ81830 has not been ACCEPTed, the link edit for ARSZFLDG in either PTF UQ85534 or UQ87838 will fail with an unresolved external reference for module ARSZSTOB. Circumvention: If the link edit failure for load module ARSZFLDG is encountered during the APPLY of UQ85534 or UQ87838, the following actions must be taken 1. ACCEPT prior maintenance through at least UQ81830. 2. Manually delete load module ARSZFLDG from the SMPLTS library for the installing SMP/E system. (This step will be omitted if the SMP/E level is V3.2 or above and the SMPLTS dataset is not being used.) 3. Re-execute the APPLY job, adding the SMP/E option "REDO" to the SMP/E APPLY control statement. 5. 04/05/04 ODWEK browser problems with OnDemand Client 7.1.1.0 Description- After installing PTF UQ87838 for APAR PQ84533 and upgrading workstations to use the OnDemand Client 7.1.1.0, ODWEK users may get the error "page expired" when going back in the browser history. Users Affected- All customers using ODWEK for OnDemand for z/OS and OS/390 installing PTF UQ87838 for APAR PQ84533 and upgrading to the OnDemand Client 7.1.1.0. Recommendation- Customers using HTTP 5.3 should install PTF UQ85573. Customers using WebSphere Application Server (WAS) 3.50 should install PTF UQ79590. 4. 03/12/18 PTF UQ83223 distributes components that may run in CICS, if required. The components are prepared to run in CICS by post-SMP/E installation jobs that are also shipped with the PTF. Program ARSAPIIC requires that library CBC.SCLBDLL be included to the CICS DFHRPL in order for it to execute. Failure to include this library may result in a U4083 ABEND during a request for Structured APIs services. Documentation for the new function provided in PTF UQ83223 will be incorporated in future OnDemand documentation. As an interim measure, until the update is released, a PDF document is being provided. This can be located by going to: http://www.ibm.com/support and doing a search for PQ81183. 3. 03/11/18 There are inaccuracies in the UQ81830 ++HOLD information. The following updates are provided to correct any errors in the UQ81830 installation instructions: 1) The Migration Guide manual number that corresponds with the migration enhancements provided in PTF UQ81830 is LY37-3746-02. The Migration Guide is only intended to be used by OnDemand V2.1 and/or IAFC V1.3 customers that are migrating to OnDemand V7.1. 2) All references to the ARSPBKG1 job in the USERJCL library should be ignored. The ARSBPKG1 job should not be run after UQ81830 is installed. With UQ81830, job ARSZMIG1 replaces job ARSBPKG1. The ARSZMIG1 job should be run to bind the ARSZFLDG and ARSZFLDM programs. 3) Access to the //service2.boulder.ibm.com ftp site is secured. Contact the IBM Support Center on queue ARS,146 to receive the authorized userid and password to the site. Do not send ftp site userid and password requests to od390@us.ibm.com. 4) The ftp://service2.boulder.ibm.com/ODzOS/V7.1Documentation/ directory contains two sub-directories. Select sub-directory LY37-3746-02 to retrieve the latest Migration Guide. Ignore the ++Hold entries in PTF UQ81830 that instruct you to download the following documents: LY37-3746-00-C.pdf or LY37-3746-00-B.pdf. 2. 02/01/29 When using the Administration Client to maintain Application table entries, on the Indexer Information tab, for the Indexer type, the value of "OS/390" is now supported, with APAR PQ54254 / PTF UQ62184. 1. 01/10/02 Customers can get technical documentation from the web at: www.ibm.com/software/data/ondemand/390/library.html. All English language and translated publications can be obtained from this web site. With the initial release of this product, the host print function is available only with the use of Infoprint. When using the Administration Client to maintain Application table entries, on the Indexer Information tab, for the Indexer type, the value of "OS/390" is currently not supported.


Service Recommendations

13 10/07/21 PROBLEM: (PM07633) ARSDB -VI IMPORT COMMAND PERFORMANCE DEGRADATION DUE TO FREQUENCY OF COMMITS USERS AFFECTED: All Content Manager OnDemand for z/OS users using arsdb -i RECOMMENDATION: INSTALL UK55884 ON VOLID 1004 (H272711) 12 10/02/15 PROBLEM: (PM05593) ARSZIMIG REPORT DELETES ARSOD ROWS FOR ALREADY MIGRATED DATA USERS AFFECTED: All users migrating indexes from OnDemand V2.1 to OnDemand V7.1, V8.4 or V8.4.1 RECOMMENDATION: INSTALL UK54280 ON VOLID 1002 (H272711) 11. 09/02/27 PROBLEM: (PK52978) SECONDARY SPACE ALLOCATION ON TABLE SPACE MAY BE INCORRECTLY SET TO 0. USERS AFFECTED: All users of Content Manager OnDemand for z/OS and OS/390 using DB2 V8 or higher. RECOMMENDATION: INSTALL UK30870 ON VOLID 0711 (H272711) 10 07/10/29 PROBLEM: (PK52840) ARSEXOAM/ARSEXPIR MAY DELETE MORE THAN THEY SHOULD IN A CERTAIN UNIQUE SITUATION. USERS AFFECTED: All users of Content Manager OnDemand for z/OS and OS/390 using ARSEXOAM or ARSEXPIR and storing AFP or Global DJDE documents. RECOMMENDATION: INSTALL UK30677 ON VOLID 0710 (H272711) 9 05/07/04 PROBLEM: (PK06182) ANNOTATIONS MAY BE INCORRECT FOLLOWING MIGRATION. OnDemand Version 2 annotations created by the OnDemand GUI Client may have missing or invalid data when migrated to OnDemand Version 7. When annotations were added to Version 2 documents using the OnDemand GUI Client, the annotations would contain the carriage return and line feed control characters '0D25'. During the migration process for annotations, the line feed symbol '25' was removed by the FTP process, resulting in missing or invalid data in the Version 7 annotations. The carriage return displays as a vertical bar when viewing migrated annotations. USERS AFFECTED: All customers migrating indexes from either CM OnDemand V2.1 or IAFC to CM OnDemand V7.1. SUMMARY: After installing PTF UK05071, customers migrating from Version 2 should run the following SQL against the Version 2 Annotation table (CDNCT) to determine if there are any annotations containing the carriage return and line feed values. SELECT * FROM CDNCT WHERE NCT_TEXT LIKE X'6C0D256C' If the SQL results in no rows selected, there are no annotations containing carriage control and line feed, and no further analysis or corrective action is required. If rows are returned, the following analysis and corrective actions are required. Review the documents for the annotation rows returned. - For documents already migrated, the documents and annotations identified will need to be migrated again. - For documents not yet migrated, no corrective action is required. RECOMMENDATION: INSTALL UK05071 ON VOLID 0507 (H272711) 8 05/05/19 PROBLEM: (PK05639) BAG RECORD LOST WHEN LOADING AFP DOCUMENT USING OS/390 INDEXER. USERS AFFECTED: All users of the OS/390 Indexer with AFP datastreams. RECOMMENDATION: INSTALL UK03540 ON VOLID 0505 (H272711) 7 05/04/25 PROBLEM: (PK04109) AFP WITH OS/390 INDEXER CAN CAUSE UNUSUAL PAGE RESULTS WHEN VIEWED OR PRINTED. USERS AFFECTED: All users of the OS/390 Indexer with AFP datastreams. RECOMMENDATION: INSTALL UK02718 ON VOLID 0504 (H272711) 6 04/12/06 PROBLEM: (PQ93485) OAM ERROR DURING UNLOAD CAN DELETE ALL APPLGRP DATA IN OD CACHE. (ROLLUP OF MP APAR PQ94176) USERS AFFECTED: All users of OnDemand for z/OS and OS/390. RECOMMENDATION: INSTALL UQ93052 ON VOLID 0409 (H272711) 5. 04/12/02 PROBLEM: (PQ95156) ARSZIMIG FAILS WITH SQLCODE -803 (DUPLICATE INSERT). THIS IS A FAILURE AGAINST ARSOD. THIS IS ALSO A PROBLEM WITH ARSZIAIM. USERS AFFECTED: All with OnDemand for z/OS V7R1M0 migrating from version 2. RECOMMENDATION: INSTALL UQ95494 ON VOLID 0411 (H272711) 4 04/12/01 PROBLEM: (PQ89802) HAVE ARSLOAD RESTRICT APPLICATION QUERY TO A SINGLE APPLICATION. ARSLOAD CAN DELETE SPOOL FILES IF LOAD FAILS. USERS AFFECTED: All with OnDemand for z/OS V7R1M0. RECOMMENDATION: INSTALL UQ90658 ON VOLID 0407 (H272711) 3 04/01/12 PROBLEM: (PQ80768) In a z/OS, 64 bit environment adding an annotation to a document may cause fields in the app group table to be removed. USERS AFFECTED: All with OnDemand for z/OS and OS/390 running in z/Architecture mode that use annotations. RECOMMENDATION: INSTALL UQ83879 ON VOLID 0401 (H272711) 2 02/03/06 PROBLEM: (PQ58254) ARSDOC -X GETS "THE SERVER FAILED WHILE RETRIEVING A DOCUMENT" USERS AFFECTED: All with OnDemand for z/OS V7R1M0 using ODF. RECOMMENDATION: INSTALL UQ63718 ON VOLID 0203 (H272711) 1 01/10/15 PROBLEM: (PQ52842) DEVELOPMENT APAR USERS AFFECTED: All with OnDemand for Z/OS and OS/390 V7R1. RECOMMENDATION: INSTALL UQ58458 ON VOLID 0110 (H272711)


Cross Product Dependencies

This section contains information that is dependent upon another product other than this subset ID. It also contains information dealing with migration and product coexistance. 3. 07/07/02 INTERDEPENDENT PRODUCT: OAM on z/OS 1.8 PROBLEM: ABEND878 after many OAM OSREQ STOREs an z/OS 1.8 R180. USERS AFFECTED: All using OAM to store OnDemand objects RECOMMENDATION: INSTALL UA34353 ON VOLID F705 2. 06/03/29 INTERDEPENDENT PRODUCT: DFSMS OAM on z/OS 1.7 PROBLEM:(OA14602) RC8 RSN24000101 WHEN OSREQ INVOKED WITH PRE R1K0 MACRO USERS AFFECTED: OAM users that use a pre z/OS 1.7 OSREQ macro. RECOMMENDATION: INSTALL UA23747 ON VOLID F601 (HDZ11K0) 1. 06/01/19 INTERDEPENDENT PRODUCT: LE for MVS and VM PROBLEM: (PK04353) ABEND0C4 WHEN DISPLAYING ERROR MESSAGE CEE3567I USERS AFFECTED: All users of z/OS Language Environment running DLL applications. RECOMMENDATION: INSTALL UK06009 ON VOLID 0508 (HLE7709) INSTALL UK06010 ON VOLID 0508 (HLE7720)


Informational / Documentation


PTF / APAR Reference Lists

PTF Include List
UK54280 UK55884
PTF Exclude List
PE APAR List


End of Upgrade ODMP710 , Subset H272711 , as of 2018/09/17.



Document information

More support for: z/OS family

Modified date: 21 July 2010