Deploying File-AID product libraries

Task 12.1 Add the File-AID Load Libraries to Your System

Below are documented methods that could be used.

LIBDEF Method:

The File-AID load libraries can be dynamically assigned when File-AID is accessed by using ISPF LIBDEF services. Copy CLIST XVJALLOC from hlq.SXVJCLIB to hlq.CXVJCLIB and modify it to your site’s requirements following the instructions in the member (see also Member XVJALLOC in Overview-of-File-AID-product-configuration). To use LIBDEF, verify that XVJLBDEF (Y) is set in the XVJALLOC CLIST and point to File-AID Libraries.

See the discussion of LIBDEF and ALTLIB allocations in Make Remaining File-AID Libraries Available.

ALTLIB Facility Method:

Copy CLIST XVJRUN from hlq.SXVJCLIB to hlq.CXVJCLIB and modify it to your site’s requirements following the instructions in the member (see also Member XVJRUN in Overview-of-File-AID-product-configuration). XVJRUN is an ALTLIB CLIST.

See the discussion of LIBDEF and ALTLIB allocations in Make Remaining File-AID Libraries Available.

Link Pack Area Method:

Refer to “Add the File-AID Load Libraries to Your System” in the File-AID Installation and Configuration Guide.

Link List Method:

The File-AID load library, hlq.SXVJLOAD, and the customized load library, hlq.CXVJLOAD, can be added to your Link List concatenation.

Logon Proc or Allocation CLIST method:

The File-AID load library, hlq.SXVJLOAD, and the customized load library, hlq.CXVJLOAD, can be concatenated to a DD statement in your logon PROC or Allocation CLIST. If you use this method, your load modules will be executed specifically from this allocation.

Place the File-AID load library in the concatenation of either of the following DD statements:

• ISPLLIB
• STEPLIB.

See the examples of LOGON PROC, allocation CLIST, and the discussion of CLISTs XVJALLOC and others in Make Remaining File-AID Libraries Available.

Task 12.2 Make Remaining File-AID Libraries Available

Choose one of the following methods to make the File-AID libraries available:

LIBDEF Method:

The File-AID libraries can be dynamically assigned when File-AID is accessed by using ISPF LIBDEF services. Copy CLIST XVJALLOC from hlq.SXVJCLIB to hlq.CXVJCLIB and modify it to your site’s requirements following the instructions in the member (see also Member XVJALLOC in Overview-of-File-AID-product-configuration). To use LIBDEF, verify that XVJLBDEF (Y) is set in the XVJALLOC CLIST and point to File-AID Libraries.

All of the classic File-AID product CLISTs (e.g., FAMENU, FIMENU, F1, F2, etc.) have been updated to use XVJALLOC. The CLIST library containing XVJALLOC and the classic File-AID family of CLISTs must be allocated to SYSPROC (via some method) to use the XVJALLOC LIBDEF.

ALTLIB Facility Method:

Copy CLIST XVJRUN from hlq.SXVJCLIB to hlq.CXVJCLIB and modify it to your site’s requirements following the instructions in the member. For more information, see Task 1.1 Update CLIST Members for hlq.CXVJCLIB in the Overview-of-File-AID-product-configuration. XVJRUN is an ALTLIB CLIST.

XVJRUN launches File-AID 23.1 products using the ALTLIB facility to allocate the CLIST library or libraries, which in turn calls XVJALLOC to allocate the remaining libraries. It can be executed from the user’s SYSPROC concatenation or directly from the data set it is in (usually hlq.SXVJCLIB or hlq.CXVJCLIB, if XVJRUN was modified).

When a valid PRODID() parameter is specified (for example, XVJRUN PRODID(XFA)), the specified product will be launched. Without a valid PRODID() parameter, it posts a menu of all products. The following table lists valid PRODID() parameters.

Prodids for File-AID products

Change the LOGON PROC:

All the other File-AID libraries must be made available to ISPF. When running File-AID under TSO, concatenate the new File-AID libraries to the ISPF libraries in the ISPF logon PROC as follows:

Set up Allocation CLIST Method:

In addition to the load library (hlq.SXVJLOAD) and the CLIST library (hlq.SXVJCLIB), all other File-AID libraries must be made available to ISPF.

You can create a CLIST to be executed from the TSO “READY” prompt, or as an initial logon command. This CLIST must be placed in a CLIST library allocated to SYSPROC in your logon proc. You may call the CLIST anything you like - for example: ALLOCFA.

This technique requires that individuals wishing to use File-AID must know the name of your allocation CLIST and how to execute it (READY prompt or initial command).

Concatenate the new File-AID libraries to the ISPF libraries in the allocation CLIST as follows:

Allocation CLIST Example 1 - When TSO STEPLIB command is available

Allocation CLIST Example 2 - When TSO STEPLIB command is not available

Starting File-AID from ISPF/PDF Primary Panel (Optional)

If you were a customer of a File-AID product (or products) prior to Release 10, ISR@PRIM Panel shows a partial sample of how you might have connected one or more products to your ISR@PRIM panel in the past.

These same CLISTs are still supported as long as the current release CLIST libraries (hlq.SXVJCLIB/hlq.CXVJCLIB) are allocated to SYSPROC. The LIBDEF rules apply the same in the current release as they did in prior releases when configured with XVJLBDEF (Y) (see Member XVJALLOC in Overview-of-File-AID-product-configuration), or you provide allocation of the additional File-AID libraries (load, panels, messages, etc.) with DD CARDs in your PROC or other techniques of your own design. Some prior File-AID products provided ALTLIB techniques. Some customers built their own ALTLIBs. When modified to point to the correct current release CLIST libraries, these should continue to function properly.

ISR@PRIM Panel

New Connection Techniques

Refer to “Starting File-AID from ISPF/PDF Primary Panel (Optional) ” in the Installing section.

CA Librarian and/or CA Panvalet Libraries

The CA Librarian or CA Panvalet load libraries must be accessible for a File-AID non-directed load. Use your site preferred method to make them accessible.

Modifications for VSAM Space Manager Pool Names or Volume Allocation

If your installation has VSAM Space Manager or Sterling Software’s Volume Allocation Manager (VAM) and wants to allow allocation of VSAM clusters by pool name, modify File-AID/Data Solutions panels UDAMU35A, UDAMU35G, UDAMU35H, and UDAMU35X and File-AID/MVS panels XFAMU35A, XFAMU35G, XFAMU35H, and XFAMU35X in panel library hlq.SXVJPENU by following the instructions in the PROC section of the panels. Uncomment the necessary statements and add the specified pool names.

Japanese and English interface in one install

When your site wants to deploy an English as well as a Japanese language instance for File-AID using the same SMP/E libraries (or a copy thereof), follow this procedure:

During the SMP/E installation specify Japanese language support:

1. Enter "Y" to the “Install Japanese components?” prompt (refer to Step 10. Specify Target and Distribution Zone Information or Step 7. Specify Target and Distribution Zone Information in BMC Installer Mainframe Products SMP/E Installation).
   This will include the Japanese Language SMP/E data sets for MESSAGES, PANELS and SKELETONS when you complete the SMP/E installation.

   Warning

   Important

   You can optionally copy a complete and unique set of SMP/E target libraries for your two language environments and configure them independently.

2. During product configuration, create two sets of CMSC DDSNnnnn members and configuration PARMLIB members (for English with suffix ENG and one for Japanese with suffix JPN):

English Configuration

1. Allocate Customized Libraries for your English Configuration (refer to “Allocate Customized Libraries” in the File-AID Installing section):

   1. Load Library Configuration Module Data set, for English for example:hlq.CXVJLENG

   2. CLIST Configuration Module Data set, for English for example:hlq.CXVJCENG

   3. Skeleton Configuration Module Data set, for English for example:hlq.CXVJSENG

2. Create a CMSC PARMLIB member DDSNENG and update it with the names of the English File-AID run-time libraries you allocated in Step 1.
3. Set DDSNSFX () to DDSNSFX (ENG) for English run-time libraries in the following 3 places:
   1. XVJRUN (Member XVJRUN in Overview-of-File-AID-product-configuration)
   2. XVJALLOC (Member XVJALLOC in Overview-of-File-AID-product-configuration)

   3. XVJDSN (Update XVJDSN with File-AID Run-Time Libraries in Overview-of-File-AID-product-configuration)

      For File-AID for Db2 only, set DDSNSFX () to DDSNSFX (ENG) for English run-time libraries in these additional 2 places:

   4. XPSTART (Set Interface for Code Debug Db2)

   5. F2XNSAMP (File-AID for Db2 Interface )

4. Create a set of File-AID PARMLIB members with suffix ENG (refer to “Table 2. File-AID Product PARMLIB Members” in Planning).
5. Set DBCSSUP to N for English in the following 3 places:
   1. PARMLIB member FACMENG (USE_JAPANESE_MESSAGES_AND_PANELS)
   2. XVJALLOC (Member XVJALLOC in Overview-of-File-AID-product-configuration)

   3. XVJDSN (Update XVJDSN with File-AID Run-Time Libraries in Overview-of-File-AID-product-configuration)

      This causes the allocation CLISTs to be created using the English Language Data sets.

6. Update CMSC to recognize PARMLIB members with suffix ENG (refer to Update CMSC with PARMLIB Information).

7. Create XVJSFX Load Module (refer to Changing PARMLIB Member Suffixes (Optional)).

   Warning

   Important

   You can optionally copy a complete and unique set of SMP/E target libraries for your English language environment and configure it independently.

Japanese Configuration

1. Allocate Customized Libraries for your Japanese Configuration (refer to “Task 3.1 Allocate Customized Libraries” in the Task-3-Preparing-for-configuration-after-installation:
   1. Load Library Configuration Module Data set, for Japanese for example:
      hlq.CXVJLJPN
   2. CLIST Configuration Module Data set, for Japanese for example:
      ​hlq.CXVJLJPN​
   3. Skeleton Configuration module data set, for Japanese for example:
      hlq.CXVJSJPN

   4. Enter/confirm the optional Japanese Language SMP/E data sets for MESSAGES, PANELS and SKELETONS:
      hlq.SXVJMJPN
      hlq.SXVJPJPN
      hlq.SXVJSJPN

2. Create a CMSC PARMLIB member DDSNJPN and update it with the names of the Japanese File-AID run-time libraries you allocated in Step a.
3. Set DDSNSFX () to DDSNSFX (JPN) for Japanese run-time libraries in the following 3 places:
   1. XVJRUN (Member XVJRUN in Overview-of-File-AID-product-configuration)
   2. XVJALLOC (Member XVJALLOC in Overview-of-File-AID-product-configuration)
   3. XVJDSN (Update XVJDSN with File-AID Run-Time Libraries in Overview-of-File-AID-product-configuration)
      For File-AID for Db2 only, set DDSNSFX () to DDSNSFX (JPN) for Japanese run-time libraries in these additional 2 places:
   4. XPSTART (Set Interface for Xpediter for DB2)

   5. F2XNSAMP (File-AID for DB2 Interface)

4. Create a set of File-AID PARMLIB members with suffix JPN (For more information, see “Table 2. File-AID Product PARMLIB Members” ).
5. Set DBCSSUP to Y for Japanese in the following 3 places:
   1. PARMLIB member FACMJPN (USE_JAPANESE_MESSAGES_AND_PANELS)
   2. XVJALLOC (Member XVJALLOC in Overview-of-File-AID-product-configuration)
   3. XVJDSN (Update XVJDSN with File-AID Run-Time Libraries in Overview-of-File-AID-product-configuration)
      This causes the allocation CLISTs to be created using the Japanese Language Data sets.
6. Update CMSC to recognize PARMLIB members with suffix JPN (For more information, see Update CMSC with PARMLIB Information).
7. Create XVJSFX Load Module (For more information, see Changing PARMLIB Member Suffixes (Optional) in PARMLIB-members).
8. To run English, execute XVJRUN from your English CLIST library (hlq.CXVJCENG).
9. To run Japanese, execute XVJRUN from your Japanese CLIST library (hlq.CXVJCJPN).

Creating uppercased File-AID panel, message, and skeleton libaries

If your site requires uppercased panels, messages, and skeletons, follow these steps to create uppercased libraries:

1. Modify the sample JCL (member XVJXUPPR in hlq.SXVJSAMP) according to your site’s requirements by following the instructions in the member.
2. Submit the job.
3. Save the used JCL whenever maintenance is performed to panels, messages, and/or skeletons.
4. If your File-AID run-time libraries are included in the default DDSNnnnn member as specified in your site’s CMSC startup (Simple Deploy method), edit the DDSNnnnn member in the CMSC library to replace hlq.SXVJPENU, SXVJMENU, and SXVJSENU with the uppercase libraries.
5. Otherwise, edit the following members:
   1. Edit the members XVJALLOC and XPSTART (File-AID for Db2 only) in your customized CLIST library hlq.CXVJCLIB to replace hlq.SXVJPENU, SXVJMENU, and SXVJSENU with the uppercase libraries.
   2. Edit the member XVJDSN in your customized skeleton library hlq.CXVJSENU to replace hlq.SXVJPENU, SXVJMENU, and SXVJSENU with the uppercase libraries.

Maintenance consideration

After performing maintenance to lowercase panels, messages, and skeletons, submit XVJXUPPR to update the uppercase libraries.