© Copyright International Business Machines Corporation 2000, 2017. All rights reserved.
© HCL Technologies Ltd. 2017, 2023
Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule contract with IBM Corp.

Table of Contents

Figures

Introduction

Program Materials

Program Support

Program and Service Level Information

Installation Requirements and Considerations

Installation Instructions

Notices

Reader's Comments

Figures

Introduction

This program directory is intended for system programmers who are responsible for program installation and maintenance. It contains information about the material and procedures associated with the installation of IBM File Manager for z/OS. This publication refers to IBM File Manager for z/OS as File Manager.

The Program Directory contains the following sections:

• "Program Materials" identifies the basic program materials and documentation for File Manager.

• "Program Support" describes the IBM support available for File Manager.

• "Program and Service Level Information" lists the APARs (program level) and PTFs (service level) that have been incorporated into File Manager.

• "Installation Requirements and Considerations" identifies the resources and considerations that are required for installing and using File Manager.

• "Installation Instructions" provides detailed installation instructions for File Manager. It also describes the procedures for activating the functions of File Manager, or refers to appropriate publications.

Before installing File Manager, read the CBPDO Memo To Users and the CBPDO Memo To Users Extension that are supplied with this program in softcopy format and this program directory; after which, keep the documents for your reference. Section "Preventive Service Planning" tells you how to find any updates to the information and procedures in this program directory.

File Manager is supplied in a Custom-Built Product Delivery Offering (CBPDO, 5751-CS3). The program directory that is provided in softcopy format on the CBPDO is identical to the hardcopy format if one was included with your order. All service and HOLDDATA for File Manager are included on the CBPDO.

Do not use this program directory if you install File Manager with a ServerPac. When you use one of those offerings, use the jobs and documentation supplied with the offering. The offering will point you to specific sections of this program directory as needed.

File Manager Description

File Manager (5755-A03) provides the following:

• Improved productivity of ISPF users

  • The indexed search provides a way to perform a fast search across one or more partitioned data sets. The results are displayed in the index search report containing the list of matching words, the number of lines where the word occurs, the number of data sets containing occurrences of the word, and the number of members.

• CICS install: Improved the usability and task orientation of the requirements for accessing CICS resources from File Manager. Depending on how you invoke File Manager, the customization steps required might differ. The File Manager installation and customization documentation has been reworked and reorganized and includes a checklist to facilitate users in the process.

• A new Internal COBOL compiler at the V6.4 level

• A new Internal PL/I compiler at the V6.1 level

• DB2 Version 13 support

• Two new options added to the Db2 CSV Export Options panels and the DBX (Export) batch command: LEADING=YES and TRAILING=YES.

• FM/CICS changed the default from START=BATCH to START=TASK

• Support of the latest z/OS subsystem environments

• For more information refer to the File Manager documentation website: https://help.blueproddoc.com/filemanager/15.1.0/en/whatsnew/whatsnew.html

File Manager FMIDs

File Manager consists of the following FMIDs:

HADLF10 File Manager

JADLF12 File Manager/Db2

JADLF14 File Manager/IMS

JADLF16 File Manager/CICS

Japanese components:

JADLF11 File Manager

JADLF13 File Manager/Db2

JADLF15 File Manager/IMS

JADLF17 File Manager/CICS

Program Materials

An IBM program is identified by a program number. The program number for File Manager is 5755-A03.

Basic Machine-Readable Materials are materials that are supplied under the base license and are required for the use of the product.

The program announcement material describes the features supported by File Manager. Ask your IBM representative for this information if you have not already received a copy.

Basic Machine-Readable Material

The distribution medium for this program is physical media or downloadable files. This program is in SMP/E RELFILE format and is installed by using SMP/E. See "Installation Instructions" for more information about how to install the program.

You can find information about the physical media for the basic machine-readable materials for File Manager in the CBPDO Memo To Users Extension.

Table 1 describes the program file content for File Manager English components.
Table 2 describes the program file content for File Manager Japanese components.

You can refer to the CBPDO Memo To Users Extension to see where the files reside on the image.

Notes:

1. The data set attributes in this table must be used in the JCL of jobs that read the data sets. However, because the data sets are in IEBCOPY unloaded format, their actual attributes might be different.

2. If any RELFILEs are identified as PDSEs, ensure that SMPTLIB data sets are allocated as PDSEs.

Table 1. Program File Content for File Manager

Table 2. Program File Content for File Manager - Japanese

Program Publications

The following sections identify the basic publications for File Manager.

Table 3 identifies the basic unlicensed publications for File Manager.

Table 3. Basic Material: Unlicensed Publications

Optional Program Publications

No optional publications are provided for File Manager.

Program Source Materials

No program source materials or viewable program listings are provided for File Manager.

Publications Useful During Installation

You might want to use the publications listed in Table 4 during the installation of File Manager.

Table 4. Publications Useful During Installation

Note: These publications can be found in IBM Documentation. Use a web browser with internet access to refer to: https://www.ibm.com/docs/en/zos/2.5.0?topic=zos-smpe

Program Support

This section describes the IBM support available for File Manager.

Program Services

Contact your IBM representative for specific information about available program services.

Preventive Service Planning

Before you install File Manager, make sure that you have reviewed the current Preventive Service Planning (PSP) information. Review the PSP Bucket for General Information, Installation Documentation, and the Cross Product Dependencies sections. For the Recommended Service section, instead of reviewing the PSP Bucket, it is recommended you use the IBM.PRODUCTINSTALL-REQUIREDSERVICE fix category in SMP/E to ensure you have all the recommended service installed. Use the FIXCAT(IBM.PRODUCTINSTALL-REQUIREDSERVICE) operand on the APPLY CHECK command. See "Perform SMP/E APPLY" for a sample APPLY command.

If you obtained File Manager as part of a CBPDO, HOLDDATA is included.

If the CBPDO for File Manager is older than two weeks by the time you install the product materials, you can obtain the latest PSP Bucket information by going to the following website:

https://esupport.ibm.com/customercare/psearch/search?domain=psp

You can also use S/390 SoftwareXcel or contact the IBM Support Center to obtain the latest PSP Bucket information.

For program support, access the Software Support Website at https://www.ibm.com/mysupport/.

PSP Buckets are identified by UPGRADEs, which specify product levels; and SUBSETs, which specify the FMIDs for a product level. The UPGRADE and SUBSET values for File Manager are included in Table 5.

Table 5. PSP Upgrade and Subset ID

Statement of Support Procedures

Report any problems which you feel might be an error in the product materials to your IBM Support Center. You may be asked to gather and submit additional diagnostics to assist the IBM Support Center in their analysis.

Table 6 identifies the component IDs (COMPID) for File Manager.

Table 6. Component IDs

Program and Service Level Information

This section identifies the program and relevant service levels of File Manager. The program level refers to the APAR fixes that have been incorporated into the program. The service level refers to the PTFs that have been incorporated into the program.

Program Level Information

The following APAR fixes against the previous release of File Manager have been incorporated into this release.

• All FMIDs
  PH00352 PH00894 PH01136 PH01305 PH01306 PH01678 PH01882 PH02069 PH02219 PH03103 PH03105 PH03766 PH04063 PH04065 PH04066 PH04067 PH04068 PH04350 PH04889 PH04903 PH04934 PH04939 PH05137 PH05390 PH06753 PH07777 PH08587 PH08641 PH08656 PH08657 PH08658 PH08659 PH08660 PH08661 PH08775 PH09010 PH09660 PH09716 PH09851 PH10084 PH10085 PH10311 PH10322 PH10532 PH10581 PH11137 PH11570 PH11639 PH11854 PH12208 PH12618 PH12853 PH12855 PH12856 PH12881 PH13394 PH14008 PH14070 PH14204 PH14384 PH14684 PH14704 PH14750 PH15054 PH16000 PH16179 PH16188 PH16358 PH16620 PH16670 PH16702 PH16703 PH16765 PH16846 PH17027 PH17035 PH17110 PH17111 PH17112 PH17282 PH17289 PH17923 PH17975 PH18177 PH18200 PH18413 PH18510 PH18637 PH18726 PH18803 PH18865 PH19642 PH19643 PH19644 PH19645 PH19646 PH19647 PH19823 PH20000 PH20110 PH20203 PH20232 PH20322 PH20323 PH20381 PH21174 PH21387 PH21718 PH21912 PH22283 PH22410 PH22424 PH22539 PH23558 PH23620 PH23708 PH23852 PH24283 PH24303 PH24525 PH24631 PH24924 PH25106 PH25107 PH25110 PH25290 PH41734 PH41741 PH41771 PH41869 PH42461 PH42671 PH42912 PH42987 PH43040 PH43298 PH43304 PH44334 PH44387 PH44461 PH44735 PH44739 PH44806 PH44988 PH45142 PH45163 PH45387 PH45676 PH45708 PH45990 PH46076 PH46614 PH46784 PH46812 PI89463 PI89464 PI90402 PI91686 PI93217 PI93729 PI94064 PI94927 PI95564 PI95707 PI96763 PI97117 PI97118 PI97379 PI98330 PI99053 PI99252 PI99483 PI99530 PH42670 PH45885 PH47451 PH47481 PH47835 PH48298 PH49301
  

   

Service Level Information

No PTFs against this release of File Manager have been incorporated into the product package.

Frequently check the File Manager PSP Bucket for HIPER and SPECIAL attention PTFs against all FMIDs that you must install. You can also receive the latest HOLDDATA, then add the FIXCAT(IBM.PRODUCTINSTALL-REQUIREDSERVICE) operand on your APPLY CHECK command. This will allow you to review the recommended and critical service that should be installed with your FMIDs.

Installation Requirements and Considerations

The following sections identify the system requirements for installing and activating File Manager. The following terminology is used:

• Driving system: the system on which SMP/E is executed to install the program.

  The program might have specific operating system or product level requirements for using processes, such as binder or assembly utilities during the installation.

• Target system: the system on which the program is configured and run.

  The program might have specific product level requirements, such as needing access to the library of another product for link-edits. These requirements, either mandatory or optional, might directly affect the element during the installation or in its basic or enhanced operation.

In many cases, you can use a system as both a driving system and a target system. However, you can make a separate IPL-able clone of the running system to use as a target system. The clone must include copies of all system libraries that SMP/E updates, copies of the SMP/E CSI data sets that describe the system libraries, and your PARMLIB and PROCLIB.

Use separate driving and target systems in the following situations:

• When you install a new level of a product that is already installed, the new level of the product will replace the old one. By installing the new level onto a separate target system, you can test the new level and keep the old one in production at the same time.

• When you install a product that shares libraries or load modules with other products, the installation can disrupt the other products. By installing the product onto a separate target system, you can assess these impacts without disrupting your production system.

Driving System Requirements

This section describes the environment of the driving system required to install File Manager.

Machine Requirements

The driving system can run in any hardware environment that supports the required software.

Programming Requirements

Table 7. Driving System Software Requirements

Note: SMP/E is a requirement for Installation and is an element of z/OS.

Note: Installation might require migration to new z/OS releases to be service supported. See https://www.ibm.com/support/lifecycle/

Target System Requirements

This section describes the environment of the target system required to install and use File Manager.

File Manager installs in the z/OS (Z038) SREL.

Machine Requirements

The target system can run in any hardware environment that supports the required software.

Programming Requirements

Installation Requisites

Installation requisites identify products that are required and must be present on the system or products that are not required but should be present on the system for the successful installation of this product.

Mandatory installation requisites identify products that are required on the system for the successful installation of this product.

File Manager has no mandatory installation requisites.

Conditional installation requisites identify products that are not required for successful installation of this product but can resolve such things as certain warning messages at installation time.

File Manager has no conditional installation requisites.

Operational Requisites

Operational requisites are products that are required and must be present on the system or products that are not required but should be present on the system for this product to operate all or part of its functions.

Mandatory operational requisites identify products that are required for this product to operate its basic functions.

Table 8, Table 9, Table 10, and Table 11 list the mandatory operational requisites for File Manager, File Manager/Db2, File Manager/IMS and File Manager/CICS.

Table 8. Target System Mandatory Operational Requisites

Note: Installation might require migration to new releases to obtain support. See https://www.ibm.com/support/lifecycle/

Table 9. Target System Mandatory Operational Requisites for File Manager/Db2

Note: Installation might require migration to new releases to obtain support. See https://www.ibm.com/support/lifecycle/

Table 10. Target System Mandatory Operational Requisites for File Manager/IMS

Table 11. Target System Mandatory Operational Requisites for File Manager/CICS

Conditional operational requisites identify products that are not required for this product to operate its basic functions but are required at run time for this product to operate specific functions.

Conditional operational requisites for File Manager base function are listed below. There are no conditional operational requisites for File Manager/Db2, File Manager/IMS, or File Manager/CICS.

Table 12. Target System Conditional Operational Requisites

Note: Installation might require migration to new releases to obtain support. See https://www.ibm.com/support/lifecycle/

Note:

For template functions using High Level Assembler, ensure that the SASMMOD1 HLASM library is available to File Manager.

Toleration/Coexistence Requisites

Toleration/coexistence requisites identify products that must be present on sharing systems. These systems can be other systems in a multisystem environment (not necessarily sysplex), a shared DASD environment (such as test and production), or systems that reuse the same DASD environment at different time intervals.

File Manager has no toleration/coexistence requisites.

Incompatibility (Negative) Requisites

Negative requisites identify products that must not be installed on the same system as this product.

File Manager has no negative requisites.

DASD Storage Requirements

File Manager libraries can reside on all supported DASD types.

Table 13 and Table 14 list the total space that is required for each type of library.

Table 13. Total DASD Space Required by File Manager

Table 14. Total DASD Space Required by File Manager Japanese components

Notes:

1. For non-RECFM U data sets, IBM recommends using system-determined block sizes for efficient DASD utilization. For RECFM U data sets, IBM recommends using a block size of 32760, which is most efficient from the performance and DASD utilization perspective.

2. Abbreviations used for data set types are shown as follows.

   U	Unique data set, allocated by this product and used by only this product. This table provides all the required information to determine the correct storage for this data set. You do not need to refer to other tables or program directories for the data set size.
   S	Shared data set, allocated by this product and used by this product and other products. To determine the correct storage needed for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the data set already exists, it must have enough free space to accommodate the storage size given in this table.
   E	Existing shared data set, used by this product and other products. This data set is not allocated by this product. To determine the correct storage for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the data set already exists, it must have enough free space to accommodate the storage size given in this table.

   If you currently have a previous release of this product installed in these libraries, the installation of this release will delete the old release and reclaim the space that was used by the old release and any service that had been installed. You can determine whether these libraries have enough space by deleting the old release with a dummy function, compressing the libraries, and comparing the space requirements with the free space in the libraries.

   For more information about the names and sizes of the required data sets, see "Allocate SMP/E Target and Distribution Libraries".

3. All target and distribution libraries listed have the following attributes:
   • The default name of the data set can be changed.
   • The default block size of the data set can be changed.
   • The data set can be merged with another data set that has equivalent characteristics.
   • The data set can be either a PDS or a PDSE, with the exception of SFMNMODA, AFMNMODA, SFMNMOD1, AFMNMOD1, SFMNMOD2, AFMNMOD2, SFMNMODJ, AFMNMODJ, which must be PDSEs.

4. All target libraries listed have the following attributes:
   • These data sets can be SMS-managed, but they are not required to be SMS-managed.
   • These data sets are not required to reside on the IPL volume.
   • The values in the "Member Type" column are not necessarily the actual SMP/E element types that are identified in the SMPMCS.

5. All target libraries that are listed and contain load modules have the following attributes:
   • These data sets can not be in the LPA, with some exceptions. If the value in the "Member Type" column specifies "LPA", it is advised to place the data set in the LPA.
   • These data sets can be in the LNKLST.
   • These data sets are not required to be APF-authorized, except for SFMNMODA, which must be APF authorized. Certain functions will not be available to all users if the File Manager load library, SFMNMOD1, is not APF-authorized. For more information see the File Manager Customization Guide.
   • File Manager requires that the SMPLTS data set must be a PDSE. If your existing SMPLTS is a PDS, you will need to allocate a new PDSE and copy your existing SMPLTS into it and then change the SMPLTS DDDEF entry to indicate the new PDSE data set.

The following figures describe the target and distribution libraries required to install File Manager. The storage requirements of File Manager must be added to the storage required by other programs that have data in the same library.

Note: Use the data in these tables to determine which libraries can be merged into common data sets. In addition, since some ALIAS names may not be unique, ensure that no naming conflicts will be introduced before merging libraries.

Table 15. Storage Requirements for File Manager Target Libraries

Table 16. Storage Requirements for File Manager Target Libraries - Japanese

Table 17. Storage Requirements for File Manager

Table 18. Storage Requirements for File Manager Distribution Libraries - Japanse

FMIDs Deleted

Installing File Manager might result in the deletion of other FMIDs. To see which FMIDs will be deleted, examine the ++VER statement in the SMPMCS of the product.

If you do not want to delete these FMIDs at this time, install File Manager into separate SMP/E target and distribution zones.

Note: These FMIDs are not automatically deleted from the Global Zone. If you want to delete these FMIDs from the Global Zone, use the SMP/E REJECT NOFMID DELETEFMID command. See the SMP/E Commands book for details.

Special Considerations

PDSE Considerations:

File Manager uses the "partitioned data set extended" or PDSE format for its LMOD target libraries. There are some operational differences between PDS and PDSE data sets. The PDS format may be shared by more than one z/OS system and no special precautions are necessary. However the PDSE format may only be shared by z/OS systems which are part of a sysplex or which are connected using Global Resource Serialization (are in a GRS complex). If z/OS systems share use of a PDSE data set outside of a sysplex or GRS environment, you may experience severe problems when the data set is updated. This is due to the fact that PDSE directory information is cached in storage, and when the data set is updated from one system the other system(s) have no knowledge of the update, and their cached directory information will be incorrect.

You must take care not to share these data sets between z/OS systems unless they are in a sysplex or are connected in a GRS complex. If you need to share the content of these libraries, a separate copy must be created for each z/OS system.

Coexistence with previous versions of File Manager

File Manager Version 14:

There are no actions required.

File Manager and COBOL and PL/I Compilers

A version of the COBOL compiler specifically for File Manager is included. These COBOL compiler modules are installed into SFMNMOD1 by the APPLY step for File Manager base component.

This is a reduced-function COBOL compiler and cannot be used to generate executable COBOL programs.

A version of the PL/I compiler specifically for File Manager is included. These PL/I compiler modules are installed into SFMNMOD1 by the APPLY step for File Manager base component.

This is a reduced-function PL/I compiler and cannot be used to generate executable PL/I programs.

The purpose of these compilers is to compile copybooks that File Manager can use to create templates which map the data.

Both these compilers require Language Environment library SCEERUN to be available for execution.

Please note that COBOL users have the choice of either using an already installed licensed COBOL compiler or the File Manager supplied compiler. PL/I users must use the compiler supplied with File Manager .

For more information on the compilers see File Manager Customization Guide.

File Manager Base Function

To process High Level Assembler copybooks, ensure that the HLASM load library, ASM.SASMMOD1, is available to File Manager.

You can optionally enable File Manager to use the DFSORT COPY function to improve the performance of the File Manager Data Set Copy and Data Set Print functions.
For information on how to enable File Manager to use DFSORT, see the File Manager Customization Guide.

For function access control and authorization verification, RACF® Security Server 02.04.00 or higher, or a functionally equivalent security package is required.

If you plan to use File Manager base function with functions making use of the object access method objects, DB2 UDB for z/OS 12.01.00 or subsequent versions or releases, or DB2 VUE for z/OS 12.01.00 or subsequent versions or releases, are required.

File Manager/Db2

File Manager/Db2 has no special considerations for the target system.

File Manager/IMS

File Manager/IMS has no special considerations for the target system.

File Manager/CICS

File Manager/CICS has no special considerations for the target system.

IBM Application Delivery Foundation for z/OS Common Components (ADFz Common Components)

ADFz Common Components is required if you plan to use the File Manager CICS component and/or the ADFz Common Components Common Server component.

If you have previously received ADFz Common Components (FMID HVWR190) and installed it into the target and distribution zones where you intend to install File Manager, there is no need to install the newly received ADFz Common Components again.

Installation Instructions

This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of File Manager.

Please note the following points:

• If you want to install File Manager into its own SMP/E environment, consult the SMP/E manuals for instructions on creating and initializing the SMPCSI and the SMP/E control data sets.

• You can use the sample jobs that are provided to perform part or all of the installation tasks. The SMP/E jobs assume that all DDDEF entries that are required for SMP/E execution have been defined in appropriate zones.

• You can use the SMP/E dialogs instead of the sample jobs to accomplish the SMP/E installation steps.

Installing File Manager

SMP/E Considerations for Installing File Manager

Use the SMP/E RECEIVE, APPLY, and ACCEPT commands to install this release of File Manager.

SMP/E Options Subentry Values

The recommended values for certain SMP/E CSI subentries are shown in Table 19. Using values lower than the recommended values can result in failures in the installation. DSSPACE is a subentry in the GLOBAL options entry. PEMAX is a subentry of the GENERAL entry in the GLOBAL options entry. See the SMP/E manuals for instructions on updating the global zone.

Table 19. SMP/E Options Subentry Values

Sample Jobs

The following sample installation jobs are provided as part of the product to help you install File Manager:

Table 20. Sample Installation Jobs

Table 21. Sample Installation Jobs for File Manager Japanese components

You can access the sample installation jobs by performing an SMP/E RECEIVE (refer to "Perform SMP/E RECEIVE") then copy the jobs from the SMPTLIB data sets to a work data set for editing and submission. See Table 20 to find the appropriate relfile data set.

You can also copy the sample installation jobs from the product files by submitting the following job. Before you submit the job, add a job card and change the lowercase parameters to uppercase values to meet the requirements of your site.

//STEP1    EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//IN       DD DSN=IBM.HADLF10.F2,UNIT=SYSALLDA,DISP=SHR,
//         VOL=SER=filevol
//OUT      DD DSNAME=jcl-library-name,
//         DISP=(NEW,CATLG,DELETE),
//         VOL=SER=dasdvol,UNIT=SYSALLDA,
//         SPACE=(TRK,(20,10,5))
//SYSUT3   DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
//SYSIN    DD *
    COPY INDD=IN,OUTDD=OUT
    SELECT MEMBER=(FMNALSMP,FMNRECEV,FMNALLOC,FMNDDDEF)
    SELECT MEMBER=(FMNAPPLY,FMNVERIF,FMNACCEP)
/*

To copy the sample jobs for the File Manager Japanese components, use this JCL.

//STEP1    EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//IN       DD DSN=IBM.HADLF10.F2,UNIT=SYSALLDA,DISP=SHR,
//         VOL=SER=filevol
//OUT      DD DSNAME=jcl-library-name,
//         DISP=(NEW,CATLG,DELETE),
//         VOL=SER=dasdvol,UNIT=SYSALLDA,
//         SPACE=(8800,(5,2,5))
//SYSUT3   DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
//SYSIN    DD *
    COPY INDD=IN,OUTDD=OUT
    SELECT MEMBER=(FMNRECVJ,FMNALLOJ,FMNDDDFJ,FMNAPLYJ,FMNACPTJ)
/*

IN:

filevol is the volume serial of the DASD device where the downloaded files reside.

OUT:

jcl-library-name is the name of the output data set where the sample jobs are stored.

dasdvol is the volume serial of the DASD device where the output data set resides. Uncomment the statment if a volume serial must be provided.

Allocate SMP/E CSI (Optional)

If you are using an existing CSI, do not execute this job.

If you are allocating a new SMP/E data set for this install, edit and submit sample job FMNALSMP to allocate the SMP/E data set for File Manager. Consult the instructions in the sample job for more information.

Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.

Perform SMP/E RECEIVE

If you have obtained File Manager as part of a CBPDO, use the RCVPDO job in the CBPDO RIMLIB data set to receive the File Manager FMIDs, service, and HOLDDATA that are included on the CBPDO package. For more information, see the documentation that is included in the CBPDO.

You can also choose to edit and submit sample job FMNRECEV to perform the SMP/E RECEIVE for File Manager base function, and the DB2, IMS and CICS components. If you do not want to RECEIVE File Manager/Db2, File Manager/IMS or File Manager/CICS at this time, remove the FMID for that component from the sample job. Consult the instructions in the sample job for more information.

If you want to receive the File Manager Japanese components, edit and submit the sample job FMNRECVJ to perform the SMP/E RECEIVE for these components. Consult the instructions in the sample job for more information.

Expected Return Codes and Messages: You will receive a return code of 0 if these jobs run correctly.

Allocate SMP/E Target and Distribution Libraries

Edit and submit sample job FMNALLOC to allocate the SMP/E target and distribution libraries for File Manager. Consult the instructions in the sample job for more information.

If you have received any File Manager Japanese components, edit and submit the sample job FMNALLOJ to allocate SMP/E target and distribution libraries for these components. Consult the instructions in the sample job for more informatio

Expected Return Codes and Messages: You will receive a return code of 0 if these jobs run correctly.

Create DDDEF Entries

Edit and submit sample job FMNDDDEF to create DDDEF entries for the SMP/E target and distribution libraries for File Manager, and the DB2, IMS, and CICS components.

If you are not installing any component, remove or comment out the step for that component from the sample job.

Consult the instructions in the sample job for more information.

If you have received any File Manager Japanese components, edit and submit the sample job FMNDDDFJ to create DDDEF entries for the SMP/E target and distribution libraries for these components. Consult the instructions in the sample job for more information.

Expected Return Codes and Messages: You will receive a return code of 0 if these jobs run correctly.

Perform SMP/E APPLY

1. Ensure that you have the latest HOLDDATA; then edit and submit sample job FMNAPPLY to perform an SMP/E APPLY CHECK for File Manager and the DB2, IMS and CICS components. If you do not want to APPLY any component, remove the FMID for that component from the sample job. Consult the instructions in the sample job for more information.

   You cannot perform an SMP/E APPLY for File Manager/Db2, File Manager/IMS or File Manager/CICS unless you are also APPLYing, or have already APPLIED, File Manager base function. However, you can apply File Manager/Db2, File Manager/IMS, and File Manager/CICS together.

   If you have received any File Manager Japanese components, edit and submit the sample job FMNAPLYJ to perform an SMP/E APPLY CHECK for these components. Consult the instructions in the sample job for more information.

   The latest HOLDDATA is available through several different portals, including https://service.software.ibm.com/holdata/390holddata.html. The latest HOLDDATA may identify HIPER and FIXCAT APARs for the FMIDs you will be installing. An APPLY CHECK will help you determine if any HIPER or FIXCAT APARs are applicable to the FMIDs you are installing. If there are any applicable HIPER or FIXCAT APARs, the APPLY CHECK will also identify fixing PTFs that will resolve the APARs, if a fixing PTF is available.

   You should install the FMIDs regardless of the status of unresolved HIPER or FIXCAT APARs. However, do not deploy the software until the unresolved HIPER and FIXCAT APARs have been analyzed to determine their applicability. That is, before deploying the software either ensure fixing PTFs are applied to resolve all HIPER or FIXCAT APARs, or ensure the problems reported by all HIPER or FIXCAT APARs are not applicable to your environment.

   To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the PRE, ID, REQ, and IFREQ on the APPLY CHECK. The SMP/E root cause analysis identifies the cause only of errors and not of warnings (SMP/E treats bypassed PRE, ID, REQ, and IFREQ conditions as warnings, instead of errors).

   Here are sample APPLY commands:

   1. To ensure that all recommended and critical service is installed with the FMIDs, receive the latest HOLDDATA and use the APPLY CHECK command as follows

      APPLY S(fmid,fmid,...) CHECK
      FORFMID(fmid,fmid,...)
      SOURCEID(RSU*)
      FIXCAT(IBM.PRODUCTINSTALL-REQUIREDSERVICE)
      GROUPEXTEND .
      

      
      

      Some HIPER APARs might not have fixing PTFs available yet. You should analyze the symptom flags for the unresolved HIPER APARs to determine if the reported problem is applicable to your environment and if you should bypass the specific ERROR HOLDs in order to continue the installation of the FMIDs.

      This method requires more initial research, but can provide resolution for all HIPERs that have fixing PTFs available and are not in a PE chain. Unresolved PEs or HIPERs might still exist and require the use of BYPASS.

   2. To install the FMIDs without regard for unresolved HIPER APARs, you can add the BYPASS(HOLDCLASS(HIPER)) operand to the APPLY CHECK command. This will allow you to install FMIDs even though one or more unresolved HIPER APARs exist. After the FMIDs are installed, use the SMP/E REPORT ERRSYSMODS command to identify unresolved HIPER APARs and any fixing PTFs.

      APPLY S(fmid,fmid,...) CHECK
      FORFMID(fmid,fmid,...)
      SOURCEID(RSU*)
      FIXCAT(IBM.PRODUCTINSTALL-REQUIREDSERVICE)
      GROUPEXTEND
      BYPASS(HOLDCLASS(HIPER),HOLDFIXCAT) .
       ..any other parameters documented in the program directory
      

      This method is quicker, but requires subsequent review of the Exception SYSMOD report produced by the REPORT ERRSYSMODS command to investigate any unresolved HIPERs. If you have received the latest HOLDDATA, you can also choose to use the REPORT MISSINGFIX command and specify Fix Category IBM.PRODUCTINSTALL-REQUIREDSERVICE to investigate missing recommended service.

      If you bypass HOLDs during the installation of the FMIDs because fixing PTFs are not yet available, you can be notified when the fixing PTFs are available by using the APAR Status Tracking (AST) function of ServiceLink or the APAR Tracking function of ResourceLink.

2. After you take actions that are indicated by the APPLY CHECK, remove the CHECK operand and run the job again to perform the APPLY.

   Note: The GROUPEXTEND operand indicates that SMP/E applies all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions.

   Expected Return Codes and Messages from APPLY CHECK: You will receive a return code of 0 if these jobs run correctly.

   Expected Return Codes and Messages from APPLY: You will receive a return code of 0 if these jobs run correctly.

Define PARMLIB members

If you do not intend to use SAF-rule controlled auditing for any File Manager component, you can skip the rest of this section.

When SAF-rule controlled auditing and PARMLIB processing is required for a File Manager component, a specific member needs to be added to SYS1.PARMLIB (or any other library in the system parmlib concatenation). Default parmlib members are provided in hlq.SFMNSAM1.

If you intend to use SAF-rule controlled auditing for File Manager base, copy member FMN0PARM to the appropriate system parmlib library.

If you are installing File Manager/IMS and intend to use SAF-rule controlled auditing for File Manager/IMS, copy member FMN1PARM to the appropriate system parmlib library.

If you are installing File Manager/Db2 and intend to use SAF-rule controlled auditing for File Manager/Db2, copy member FMN2PARM to the appropriate system parmlib library.

If you are installing File Manager/CICS and intend to use SAF-rule controlled auditing for File Manager/CICS, copy member FMN3PARM to the appropriate system parmlib library.

The IBM File Manager for z/OS Customization Guide, contains more information on customizing these members, and methods to include them in the system parmlib concatenation.

Note: File Manager will not start when SAF-rule controlled auditing is active and the required parmlib member does not exist in the system parmlib concatenation.

Verify the Installation of File Manager

To verify the successful installation of File Manager base function, edit and submit the sample batch job FMNVERIF. Consult the instructions in the sample job for more information. This job will produce a listing showing the product level of File Manager, and sample data file outputs. The job uses the DSP function and produces output in both hex and tabular form. There are three steps: using a sample COBOL template and copybook, using a sample HLASM copybook and using a PL/I INCLUDE book. FMNVERIF is distributed in hlq.SFMNSAM1.

Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.

To verify the successful installation and customization of File Manager/Db2, you need to create a small sample database, run a batch job and perform some tasks using File Manager/Db2. This process is described in the File Manager Customization Guide.

To verify the successful installation and customization of File Manager/IMS, you need to run a number of batch jobs to set up IMS databases, and then use File Manager/IMS to work with these databases. This process is described in the File Manager Customization Guide.

To verify the successful installation and customization of File Manager/CICS, follow the verification process described in the File Manager Customization Guide.

Perform SMP/E ACCEPT

Edit and submit sample job FMNACCEP to perform an SMP/E ACCEPT CHECK for File Manager and the DB2, IMS and CICS components. If you do not want to ACCEPT any component, remove the FMID for that component from the sample job. Consult the instructions in the sample job for more information.

If you have applied any File Manager Japanese components, edit and submit the sample job FMNACPTJ to perform an SMP/E ACCEPT CHECK for the these components. Consult the instructions in the sample job for more information.

To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the PRE, ID, REQ, and IFREQ on the ACCEPT CHECK. The SMP/E root cause analysis identifies the cause of errors but not warnings (SMP/E treats bypassed PRE, ID, REQ, and IFREQ conditions as warnings rather than errors).

Before you use SMP/E to load new distribution libraries, it is recommended that you set the ACCJCLIN indicator in the distribution zone. In this way, you can save the entries that are produced from JCLIN in the distribution zone whenever a SYSMOD that contains inline JCLIN is accepted. For more information about the ACCJCLIN indicator, see the description of inline JCLIN in the SMP/E Commands book for details.

After you take actions that are indicated by the ACCEPT CHECK, remove the CHECK operand and run the job again to perform the ACCEPT.

Note: The GROUPEXTEND operand indicates that SMP/E accepts all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions.

Expected Return Codes and Messages from ACCEPT CHECK: You will receive a return code of 0 if these jobs run correctly.

If PTFs that contain replacement modules are accepted, SMP/E ACCEPT processing will link-edit or bind the modules into the distribution libraries. During this processing, the Linkage Editor or Binder might issue messages that indicate unresolved external references, which will result in a return code of 4 during the ACCEPT phase. You can ignore these messages, because the distribution libraries are not executable and the unresolved external references do not affect the executable system libraries.

Expected Return Codes and Messages from ACCEPT: You will receive a return code of 0 if these jobs run correctly.

Run REPORT CROSSZONE

The SMP/E REPORT CROSSZONE command identifies requisites for products that are installed in separate zones. This command also creates APPLY and ACCEPT commands in the SMPPUNCH data set. You can use the APPLY and ACCEPT commands to install those cross-zone requisites that the SMP/E REPORT CROSSZONE command identifies.

After you install File Manager, it is recommended that you run REPORT CROSSZONE against the new or updated target and distribution zones. REPORT CROSSZONE requires a global zone with ZONEINDEX entries that describe all the target and distribution libraries to be reported on.

For more information about REPORT CROSSZONE, see the SMP/E manuals.

Activating File Manager

Product Customization

The publications IBM File Manager for z/OS Customization Guide, , contains the necessary information to register, customize and use File Manager

Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

APAR numbers are provided in this document to assist in locating PTFs that may be required. Ongoing problem reporting may result in additional APARs being created. Therefore, the APAR lists in this document may not be complete. To obtain current service recommendations and to identify current product service requirements, always contact the IBM Customer Support Center or use S/390 SoftwareXcel to obtain the current "PSP Bucket".

IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Trademarks

IBM, the IBM logo, and other IBM trademark listed on the IBM Trademarks List are trademarks or registered trademarks of International Business Machines Corporation, in the United States and/or other countries. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on ibm.com/trademark.

Reader's Comments

Program Directory for IBM File Manager for z/OS, March 2023

We appreciate your input on this publication. Feel free to comment on the clarity, accuracy, and completeness of the information or give us any other feedback that you might have.

Send your comments by emailing us at ibmdocs@us.ibm.com, and include the following information:

1. Your name and address

2. Your email address

3. Your telephone or fax number

4. The publication title and order number

5. The topic and page number related to your comment

6. The text of your comment

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

IBM or any other organizations will only use the personal information that you supply to contact you about the issues that you submit.

Thank you for your participation. above.