Getting started

This section is intended for users who are familiar with File-AID/MVS and the IBM Interactive System Productivity Facility/Program Development Facility (ISPF/PDF), hereafter referred to as ISPF. The basic components of ISPF are not defined here.

At BMC we strive to make our products and documentation the best in the industry. Feedback from our customers helps us to maintain our quality standards.

If problems arise, consult your manual or the File-AID/Data Solutions technical representative at your site for assistance. If problems persist, please obtain the following information before calling BMC. This information helps us to efficiently determine the cause of the problem.

  1. If possible, access the File-AID/Data Solutions System Parameters screen (option 0.1) to determine your client number, File-AID/Data Solutions release number and release date.
  2. Identify the operating system being used to help determine operating system dependencies.
  3. If an abend occurs, note the displacement and the module in which it occurs. If possible, obtain a copy of the system dump (see Creating a Dump).
  4. Note the sequence of issued commands that resulted in the problem, and the data type involved.

Creating a Dump

Data Solutions processing normally traps abends and summarizes the abend information. In most cases, this provides the information necessary to analyze the problem. When it is not sufficient, a BMC support representative may ask you to shut off the Data Solutions abend-trapping and create a full (regular) dump.

Batch

To get a full dump from a Data Solutions batch function:

  1. Add the following JCL to the job step in question:
    //SYSUDUMP DD SYSOUT=*                         DUMP OUTPU
    //ABNLDUMP DD DUMMY         UNDER ABEND-AID, GET FULL DUMP, TOO
    The system forces the DCB parameters that it needs. You can point SYSUDUMP to a data set
    instead of a SYSOUT class.
  2. Change the EXEC statement from PGM=UDASOLUT to PGM=UDASOLUT,PARM=’DEBUG’ in the JCL of the job step in question. This sets up Data Solutions to get a dump.
  3. Add the following CEEOPTS DD statement to turn off LE (Language Environment) trapping:

//CEEOPTS DD *
TRAP(OFF,NOSPIE) 

Recreate the problem, print the dump or copy it to a dataset, and ship it and other supporting materials to BMC for analysis.

SYSMDUMP

In case the SYSUDUMP doesn’t provide enough information, a BMC Support representative may ask for a SYSMDUMP.

To get a full SYSMDUMP from a Data Solutions batch function:

  1. Add the following JCL to the job step in question:
    //CEEOPTS DD *

    TRAP(OFF,NOSPIE)
    //SYSMDUMP DD DSN=your dataset name,
    // DCB=(RECFM=FBS,LRECL=4160,BLKSIZE=4160),
    // UNIT=SYSDA,DISP=(NEW,CATLG,CATLG),
    // SPACE=(CYL,(300,100),RLSE)
  2. Change the EXEC statement from PGM=UDASOLUT to PGM=UDASOLUT,PARM=’DEBUG’ in the JCL of the job step in question. This sets up Data Solutions to get a dump.

Recreate the problem and ship the dump and other supporting materials to BMC for analysis.

Online

To get a full dump from a Data Solutions online function:

  1. Allocate a CEEOPTS file with RECFM=FB, LRECL=80, BLKSIZE=80, and space units= 1 block.
  2. Edit the CEEOPTS file and set positions 1 - 16 to: TRAP(OFF,NOSPIE).
  3. To set up TSO allocation to get a dump, enter these TSO commands:
    ALLOC     FI(SYSUDUMP) DA(SYSUDUMP) MOD CYL SPACE(5 5) REUSE /*DUMP OUTPUT*/ ALLOC FI(ABNLDUMP) DUMMY REUSE     /*UNDER ABEND-AID, GET FULL DUMP,TOO*/
    The system forces the DCB parameters that it needs.
  4. Then online do ALLOC FI(CEEOPTS) DA(ceeopts DSN) OLD
  5. To put Data Solutions in TEST mode and set up to get a dump, select Data Solutions option Z.4 (Data Solutions Primary Option Menu, hidden Diagnostics option Z, Variables option 4). Set the TEST mode to Y.
  6. Without backing out of  Data Solutions recreate the problem. When needed for problem diagnosis, create screen prints. When the abend occurs, immediately, press Enter.
    Now you wait for the system to write the dump. Be     prepared to wait, this normally takes a while. There may be several cascading dumps to process.
  7. When the system comes back, ship the dump and other supporting materials to BMC for analysis.
SYSMDUMP

In case the SYSUDUMP doesn’t provide enough information, a customer service representative may ask for a SYSMDUMP.

To get a full SYSMDUMP from a File-AID online function:

  1. Allocate a CEEOPTS file with RECFM=FB, LRECL=80, BLKSIZE=80 and space units= 1 block.
  2. Edit the CEEOPTS file and set positions 1 - 16 to TRAP(OFF,NOSPIE).
  3. Allocate a SYSMDUMP file with RECFM=FBS, LRECL=4160, BLKSIZE=24960 and units= 500 cylinders.
  4. Then online do ALLOC FI(SYSMDUMP) DA(sysmdump DSN) OLD
  5. Then online do ALLOC FI(CEEOPTS) DA(ceeopts DSN) OLD

Recreate the problem and ship the dump and other supporting materials to BMC for analysis.

This section provides information about the following topics:

  • Overview-of-BMC-AMI-DevX-File-AID-Data-Solutions: Product feature and function descriptions.
  • Conventions-in-BMC-AMI-DevX-File-AID-Data-Solutions: Instructions for accessing File-AID/Data Solutions and descriptions of the conventions and procedures that can be used with more than one function, such as tutorials.
  • Parameters-function: Display and modify a variety of parameter settings at any time during your File-AID/Data Solutions session. This section describes the Parameters function, options, and screens.
  • Date-Aging-function: Options and screens used with Date Aging, Date Calculator, and Business Rules.
  • Euro-Tools-function: Options and screens associated with Euro Conversion and Euro Triangulation.
  • Data Analyzer (3): Options and screens used with the Date Analysis, Data Validation, and Data Analysis functions.
  • Translator-function: Options and screens associated with the Translator function.
  • Generation-function: Options and screens associated with the Generator function.
  • Field Exits (6): Options and screens associated with field exits.
  • Data Encryption (7): Options and screens associated with the Data Encryption function.
  • Data Replace (8): Options and screens associated with the Data Replace function.

  • Data Privacy (D): The File-AID/Data Solutions Data Privacy function executes any Dynamic Privacy Rules you defined using the File-AID Data Privacy plugin of the Topaz Workbench1.

    Important

    1: The Compuware Workbench has been replaced by the Topaz Workbench. The Topaz Workbench provides all of the functionality of the previous Compuware Workbench as well as any additional chargeable functionality.

  • Utilities-function: Print the contents of an existing change criteria member, and generate and update a File Override data set for any file in the change criteria member. This section describes the Print options and screens, and the File Override options and screens.
  • Criteria-function: Create and maintain sets of criteria that File-AID/Data Solutions uses to modify the data file. This section describes the change criteria function, options, and screens. It also describes the optional selection criteria feature which you can elect to use with the aging criteria to select specific records in a data file for change processing.
  • Record Layout Cross Reference (R): Create and maintain XREFs (record layout cross references) that File-AID/MVS and Data Solutions use to format files containing more than one record type. This section describes the Record Layout Cross Reference function, options, and screens.
  • Batch Aging Criteria Creation: Batch procedure to facilitate the creation of aging criteria without using Data Solutions’s online interface. This can be used to employ the output of a variety of Y2K analysis tools. This section describes the sample files and procedure to create aging criteria.
  • UDACOPY Sample Files: Describes the sample training files provided with File-AID/Data Solutions.
  • File-AID/Data Solutions-Supplied Date Pattern Exits: Describes the characteristics of the sample formatted date pattern exits provided with File-AID/Data Solutions.

 

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