Writer instructions

Purpose

Use this page to display a banner announcement on each page of the space. Create the Space announcements page in the master space, outside of the Home branch.

You can version the Space announcements page to enable different banners to be published into different target spaces, however, the banner that is displayed in the versioned (master) space itself only displays the most recently-published banner.  If you find errors in the banner area of your versioned space and you are sure the Space announcements page is set up correctly, try publishing the page to the same space.

For more information, see Space-announcements-banners.

Removing

When an announcement is no longer needed, remove the BMC Space Banner macro.

Translation

Localized spaces using the L10n Viewport theme must change the name of this page to Space announcements l10n.  See Configuring-the-Scroll-ViewPort-theme-for-translated-spaces.

Usage

Choose one or none of the following BMC Space Banner macros.

If your space requires another kind of announcement, you can use this page in coordination with your team lead and editors.

When should I use a space announcement banner?

Use the space organization announcement after you change the content from a book-like organization (such as User Manual, Configuration Manual, and Administration Guide) to the product model.

Use the latest version announcement to push traffic to later versions. You do not need to add this to every previous version, but if you have a specific reason that you want users to be aware—for example, Google searches show content for an obsolete version—use the banner to help users find a relevant version.

When an announcement is no longer needed, remove the BMC Space Banner macro.

Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

File-AID for IMS/ISPF

A short test using File-AID for IMS/ISPF and the training files (see Installing-Training-Files) completes the installation process. Running the test verifies that all components of File-AID for IMS/ISPF are loaded properly and that executing File-AID for IMS/ISPF produces the expected results.

This section provides step-by-step procedures along with screen illustrations and explanations of common variances to assist you with the verification of the installation of File-AID for IMS/ISPF.

Important

If you previously used a version of File-AID for IMS/ISPF, the default field values on the screens shown in this section may differ from your screen displays. The default field values presented in this section will match your default field values only if your ISPF Profile member (IXPPROF) does not exist.

Task 13.25 Verify Primary Options

  1. Invoke File-AID for IMS/ISPF through the method chosen during customization of your environment.
  2. From the File-AID for IMS/ISPF Primary Option Menu, verify that you can invoke each of the primary options by entering the appropriate number or letter and pressing Enter.
  3. As you confirm that you can invoke an option, invoke the next one by either returning to the Primary Option Menu using the END command or pressing PF3 and then selecting the next option or by going directly to the option using a jump command (for example, =3 to go to option 3, Utilities).

Task 13.26 Verify XIXCOPY CLIST

The XIXCOPY CLIST must be available to you in order to continue the verification process (see Installing-Training-Files).

  1. Type TSO %XIXCOPY on the COMMAND line to execute the XIXCOPY CLIST.

    File-AID displays progress messages as the sample files are created.

  2. Answer the question OK TO DELETE? with Y (Yes) to delete old training files and create new copies.

Task 13.27 Verify Option 7

Perform the following:

  1. Enter 7 from the File-AID for IMS/ISPF Primary Option Menu. The Segment/Layout XREF - Dataset Specification screen (see the following figure) is displayed.

    EDIT Segment/Layout XREF - Dataset Specification Screen

    image2021-7-19_22-11-39.png

  2. Verify that the data set names on the screen have the same high level qualifier you specified in Create CLISTs for Individual Products. Typically, the high level qualifier is your TSO UserID. If not, change them to the new training file names.

  3. Type PORDR in the Member field and press Enter. The EDIT Segment/Layout XREF - Segment List screen is displayed (see the following figure).

    EDIT Segment/Layout XREF - Segment List Screen

    image2021-7-19_22-12-16.png

Task 13.28 Verify Option 2

  1. Enter =2 on the COMMAND line. Either the EDIT - Data Base Specification (Dynamic PSB) screen (EDIT - Data Base Specification Screen (Dynamic PSB)) or the EDIT - Data Base Specification (Static PSB) screen (EDIT - Data Base Specification Screen (Static PSB)) is displayed.
  2. If the Static PSB screen is displayed, enter the XPSB command on the COMMAND line to switch to the Dynamic PSB screen.

Dynamic PSB

EDIT - Data Base Specification Screen (Dynamic PSB)

image2021-7-19_22-14-20.png

  1. Verify that the DBDLIB data set, Segment/Layout XREF dataset, and layout data set names match the training file data set names that were created for you by the XIXCOPY process. Enter DBDLIB member name PORDR and XREF member name PORDR.

  2. Enter Y in the Create audit trail field to verify that the Cataloged Unit and Cataloged Volume parameters are properly set.

    After you complete the screen, press Enter. The EDIT - Data Base Dataset Specification screen shown in the following figure is displayed.

    EDIT – Data Base Dataset Specification Screen

    image2021-7-19_22-15-0.png

  3. Enter the data set names for the training ORDER and CUSTOMER databases (both created with XIXCOPY) on lines one and two, respectively. Press Enter.

    File-AID for IMS is invoked and the EDIT - Data Base Location screen shown in the following figure is displayed.

    EDIT – Data Base Location Screen

    image2021-7-19_22-15-40.png

  4. Type S on the first data line on the screen and press Enter. The Formatted screen shown in the following figure is displayed.

    Formatted Screen

    image2021-7-19_22-16-19.png

  5. Press PF3 twice to return to the EDIT - Data Base Specification (Dynamic PSB) screen (EDIT - Data Base Specification Screen (Dynamic PSB)).
  6. Enter XPSB on the COMMAND line. The EDIT - Data Base Specification (Static PSB) screen is displayed (see the following figure).

Static PSB

EDIT - Data Base Specification Screen (Static PSB)

image2021-7-19_22-17-3.png

  1. Verify that the PSBLIB dataset 1 entry has the same high level qualifier as your installed target data sets (see File-AID Target Libraries table in Overview-of-File-AID-product-configuration). The DBDLIB dataset 1, COBOL layout dataset, and XREF entries should already be set from the prior edit session.
  2. Type XIXPSBSA as the PSB Member name, erase the DBDLIB Member name, and press Enter. The DBD Selection List for Static PSB screen is displayed (DBD Selection List for Static PSB Screen).
  3. Type S in the first line command to edit the PORDR database, and press Enter. The EDIT - Data Base Dataset Specification screen is displayed. The dataset names should be set from the prior edit session.
  4. Press Enter. File-AID is invoked again, and the EDIT - Data Base Location screen is displayed.
  5. Type S on the first data line on the screen and press Enter. The Formatted screen is displayed.
  6. Type =X in the command field, and press Enter. If your TSO user profile option is set to WTMSG, the message DFS627I RESOURCE CLEANUP COMPLETE is shown, followed by a display of the Primary Option Menu.
    DBD Selection List for Static PSB Screen
    image2021-7-19_22-17-44.png

Task 13.29 Verify CA Panvalet and CA Librarian Support

Important

If your installation uses CA Panvalet or CA Librarian, perform this task. Otherwise, proceed directly to Verify Batch Extract Job Submission .

  1. Get the name of a CA Panvalet or CA Librarian COBOL or PL/I member that contains a segment layout.
  2. Enter 7 from the File-AID Primary Option Menu.
  3. Type member name LIBRTST, and press Enter. The EDIT Segment/Layout XREF - Segment List screen is displayed.
  4. Change the YYYYYYYYYY value under the COBOL Member heading to the name of the member you obtained in Step 1 of Task 13.29.
  5. Enter the END command twice. The File-AID Primary Option Menu is displayed.
  6. Select Option 2 and press Enter. Add the name of your CA Panvalet or CA Librarian data set as the second COBOL or PL/I layout data set on the EDIT - Data Base Specification screen.
  7. Press Enter. The EDIT - Data Base Dataset Specification screen (EDIT - Data Base Specification Screen (Static PSB)) is displayed. The data set names should have been retained from Step 2 of Task 13.27.
  8. Press Enter. The EDIT - Data Base Location screen is displayed.
  9. Type S on the first data line and press Enter. The Formatted screen is displayed using the COBOL or PL/I layout from CA Panvalet or CA Librarian.
    This screen probably does not match the segment contents. However, the purpose of this task is simply to verify that the layout itself was successfully retrieved.

Task 13.30 Verify Batch Extract Job Submission

Invoke Option 4.1, Data Base Extract. The following sequence of screens is displayed to submit a DL/I job. The DL/I job extracts segments from the sample databases specified in the Training files screen in the Install option of the File-AID – INSTALL MENU to a new data set named hlq.FISAMP.UNLOAD.

Data Base Extract - Data Base Specification Screen

image2021-7-19_22-20-49.png

  1. Enter the DBDLIB training data set name created during installation, and press Enter. The Data Base Extract - Option Specification screen is displayed (Data Base Extract - Option Specification Screen).
  2. Verify that the fields match the preceding figure, and press Enter. The EXTRACT - Data Base Dataset Specification screen is displayed (EXTRACT - Data Base Dataset Specification Screen).
    The data set names should be retained from Step 2 of Task 13.27. Press Enter. The Data Base Extract - JCL Specification screen is displayed (Data Base Extract - JCL Specification Screen).
  3. Verify that the fields match the above figure.
  4. Modify the JOB statement information to conform to your installation standards, and press Enter to submit the job.
  5. Review the Data Base Extract Report when the job finishes executing.

Data Base Extract - Option Specification Screen

image2021-7-19_22-22-11.png

EXTRACT - Data Base Dataset Specification Screen

image2021-7-19_22-22-41.png

Data Base Extract - JCL Specification Screen

image2021-7-19_22-23-17.png

Task 13.31 Exit

Enter =X in the Command field and press Enter to exit File-AID for IMS/ISPF.

Task 13.32 Update Default Profile Table (Optional)

The default File-AID for IMS ISPF profile member is in the hlq.SXVJTENU data set in member IXPPROF. If you wish to update the default profile for new users, update member IXPPROF in the hlq.SXVJTENU data set with the desired default profile.

Generating Diagnostics

If you contact BMC’s Customer Support for assistance, the Customer Support Analyst may ask you to generate a dump and/or a File-AID trace.

Before attempting to generate dump output, consult your system programming staff to determine what is required to generate complete SYSUDUMP output. Sometimes key portions of a system dump are not written in order to maximize system performance, particularly in production environments.

You may use the FIDUMP CLIST found in the File-AID CLIST library (hlq.SXVJCLIB) to generate SYSUDUMP and IXPTRACE output. An example of this CLIST is shown in FIDUMP CLIST.

The FIDUMP CLIST creates and allocates a SYSUDUMP data set and an IXPTRACE data set. By default, these data sets are named &sysuid.FILEAID.IMS.DUMP and &sysuid.FILEAID.IMS.TRACE1 where &sysuid is your user ID. If necessary, you may change the names of these data sets by modifying the CLIST. The CLIST also invokes File-AID in TEST mode. This causes the product to bypass ESTAE/ESPIE processing at the time of an ABEND. Executing this CLIST will always create the File-AID trace data set. This permits diagnostic information to be generated even when no ABEND occurs.

Important

1: When using the File-AID/Eclipse of the Topaz Workbench, the trace data set name is &sysuid.FAIMS.TRACE.Dnnnnnnn.Tnnnnnnn.

FIDUMP CLIST

image2021-7-19_22-24-36.png

In most cases the following steps will allow you to create SYSUDUMP output and/or a trace output:

  1. Access ISPF 7.1 (Dialog Test).
  2. Enter EX 'hlq.SXVJCLIB(FIDUMP)' in the CMD field, where hlq is the high level qualifier used to install File-AID for IMS/ISPF. This starts File-AID for IMS/ISPF in test mode.
  3. Perform the steps in File-AID for IMS/ISPF that produced the problem’
  4. If necessary, free the SYSUDUMP and IXPTRACE data sets.
  5. Download these data sets using a BINARY transfer protocol and transmit them to BMC.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*