IBM Support

Updates to IMS Tools Base for z/OS V1.6 Policy Services User's Guide and Reference (SC19-4374-03)

Product Documentation


Abstract

Updates to IMS Tools Base for z/OS V1.6 Policy Services User's Guide and Reference (SC19-4374-03)

Content

The most recent updates appear at the top of the list.


Update 2

Date of change: July, 2019

Change description:  Documentation update to add data element information under the 'Data elements' section.

Topics: Changes apply to multiple topics.

 

============================

Topic: Reference: Policy Services > Data elements > Data elements related to database data set space

A new entry has been added to the following table.

 

Table. Data elements related to database data set space (Table 14 in PDF)

 Data element name   HDAM   HIDAM   HISAM   SHISAM   PINDEX   SINDEX   PHDAM   PHIDAM   PSINDEX   Type   Description 
... ...
DB_NUM_DBDS_BLOCKS Y Y Y Y - - Y Y - DS The number of blocks or CIs that are used for the data set. High Used RBA is on the highest block or CI.
Start of changeDB_NUM_ALLOCATED_BLOCKS Y Y Y Y - - Y Y - DS The number of blocks or CIs that are allocated for the data set.End of change
DB_BLOCK_SIZE Y Y Y Y - - Y Y - DS The CI size of VSAM or the block size of OSAM.
... ...

============================

Topic: Reference: Policy Services > Data elements > Data elements related to overflow in an area

A new entry has been added to the following table.

 

Table. Data elements related to overflow in an area (Table 20 in PDF)

 Data element name   DEDB   Sensor data record type   Description 
... ...
DB_AVG_NUM_IOVFCI_BY_UOW Y AREA The average number of IOVF CIs that are used by a UOW in the data set. UOWs that do not use IOVF CIs are excluded.
Start of changeDB_MAX_NUM_IOVFCI_BY_UOW Y AREA The maximum number of IOVF CIs that are used by a UOW in the data set.End of change
DB_MIN_NUM_IOVFCI_BY_UOW Y AREA The minimum number of IOVF CIs that are used by a UOW in the data set.
... ...
 

Update 1

Date of change: June, 2019

Change description: Documentation change by PH11800. This APAR provides a new batch utility that imports sensor data.

Topics: Changes apply to multiple topics.

 

============================

Topic: Using Policy Services utilities > Sensor Data Extractor > Control statements for the Sensor Data Extractor

This topic has been changed as follows:

 

The control statement for the Sensor Data Extractor controls the functions of the Sensor Data Extractor.

The control statement must be specified in the BSNSYSIN data set. This control statement data set generally resides in the input stream. However, it can also be defined as a sequential data set or as a member of a partitioned data set. It must contain 80-byte, fixed-length records. The block size, if coded, must be a multiple of 80.

Start of changeThe control statement must be coded in columns 1 - 72.  Columns 73 - 80 are regarded as comments and ignored. End of change

...

============================

Topic: Using Policy Services utilities > Statistics Data Import Utility (new)

The following topics have been added.

Statistics Data Import Utility
  Statistics Data Import Utility overview
  Running the Statistics Data Import Utility
  EXEC and DD statements for the Statistics Data Import Utility
  Control statements for the Statistics Data Import Utility
  Input CSV-formatted data sets for the Statistics Data Import Utility
  Output from the Statistics Data Import Utility
  JCL examples for the Statistics Data Import Utility

The following PDF contains the updated contents:

Start of change

PDF icon

aiipsa62_for_APAR_PH11800.pdf

End of change

Note: Page, figure, table, and cross-reference numbers in this PDF extract might not match your current user guide version. Use this documentation extract for content update purposes only. Change bar markings on the left side of the page indicate the new or changed information. This information will be included in any future refreshes of the entire user guide.

============================

Topic: Troubleshooting > Runtime error messages (BSN)


The following messages have been modified or added.

 

BSN8016E UNSUPPORTED DOMAIN. DOMAIN=domain_name.
or
UNSUPPORTED DATABASE TYPE. DBTYPE=database_type.
Start of change or
UNSUPPORTED DATABASE TYPE PREACCES=X'nn'.

or
UNSUPPORTED INPUT FORMAT.
End of change

Explanation: Start of changeThe Policy Services utility does not support the requested domain, database, or input sensor data format. End of change
System action: Processing ends with a return code of 8.
User response: This error might be an internal system error. Contact IBM Software Support.

 

Start of changeBSN8017E DBD dbd_name NOT FOUND IN DBDLIB.
Explanation: The Policy Services utility could not find the DBD member dbd_name in the DBD library.
System action: Processing ends with a return code of 8.
User response: Check if the correct DBD library is specified in the IMS DD statement. End of change

 

BSN8023E DATA DICTIONARY SERVICE FAILED FOR FUNC=function, RC=overall_return_code, RSN=overall_reason_code.
- DATA ELEMENT: data_element_name, RC=return_code, RSN=reason_code.
Start of change- DATA VALUE: data_element_value End of change

Explanation: Start of changeAn error was detected when the indicated function function of the Data Dictionary Service was running.  If the error was detected in specific data elements, the second line of the BSN8023E message is issued. If the error was detected in a data value of a specific data element, the third line of the BSN8023E message is issued.

In the message text,

overall_return_code
overall_reason_code

These hexadecimal values indicate the return and reason codes from the Data Dictionary Service.

data_element_name

The name of the data element that caused the error.

return_code
reason_code

These hexadecimal values indicate the return and reason codes associated with the data element.

data_element_value

The value of the data element that caused the error. End of change

System action: Processing ends with a return code of 8.
User response: Correct the error, and rerun the job.

 

Start of changeBSN8028I UTILITY HISTORY DATA WAS ADDED TO SENSOR DATA REPOSITORY.
Explanation: The Statistics Data Import Utility stored catalog information about the imported sensor data (utility history data) in the IMS Tools KB Sensor Data repository.
System action: Processing continues.
User response: None. This message is informational.

 

BSN8029I HISTORICAL SENSOR DATA SET WAS GENERATED.
Explanation: The Statistics Data Import Utility generated the historical sensor data set from input CSV-formatted sensor data sets.
System action: Processing continues.
User response: None. This message is informational.

 

BSN8042E DATE FORMAT IS INCORRECT FOR REQUEST TYPE=request_type.
 - CSV DATA SET NAME=data_set_name LINE=line_number

Explanation: The date format of the Run Date column was yyyy/mm, while the value in the Request Type column was D. Or, the date format of the Run Date column was yyyy/mm/dd, while the value in the Request Type column was M.
data_set_name is the name of the input CSV-formatted data set. line_number is the line number in the CSV file that caused the error.

System action: Processing ends with a return code of 8.
User response: Check if the value in the Run Date column and the value in the Request Type column are correct.

 

BSN8043E AT LEAST 1 INPUT FILE MUST BE SPECIFIED.
Explanation: No input sensor data set was specified for the Statistics Data Import Utility.
System action: Processing ends with a return code of 8.
User response: Specify at least one of the following keywords: CSV_DB, CSV_AREA, or CSV_DSG.

 

BSN8044E INCORRECT COLUMN NAME IS SPECIFIED.
 - CSV DATA SET NAME=data_set_name
 - COLUMN NAME=column_name

Explanation: The column name column_name in the input CSV-formatted data set is not supported.
data_set_name is the name of the input CSV-formatted data set.

System action: Processing ends with a return code of 8.
User response: Remove the unsupported column from the CSV-formatted data set.

 

BSN8045E MANDATORY COLUMN column_name IS NOT FOUND.
 - CSV DATA SET NAME=data_set_name

Explanation: The mandatory column name column_name was not specified in the input CSV-formatted data set.
data_set_name is the name of the input CSV-formatted data set.

System action: Processing ends with a return code of 8.
User response: Add the mandatory column column_name into the CSV-formatted data set.

 

BSN8046E INCORRECT VALUE IS SPECIFIED FOR column_name COLUMN.
 - CSV DATA SET NAME=data_set_name
 - LINE=line_number VALUE=data_value [, RC=return_code].
Explanation: The mandatory column name column_name was not specified in the input CSV-formatted data set.
data_set_name is the name of the input CSV-formatted data set.

System action: Processing ends with a return code of 8.
User response: Add the mandatory column column_name into the CSV-formatted data set.

 

BSN8047I EXISTING UTILITY HISTORY DATA DID NOT CONTAIN INFORMATION OF HISTORICAL SENSOR DATA.
 - RECONID=recon_id, DBD=dbd_name [, PARTITION=partition_name | , AREA=area_name].

Explanation: The Statistics Data Import Utility obtained existing utility history data for the database to be imported, but the utility history data did not contain catalog information about the historical sensor data.

In the message text,
recon_id

Shows the RECON ID associated with the IMS Tools Knowledge Base that contains the utility history data.

dbd_name

Shows the name of the database to be imported.

partition_name

Shows the name of the HALDB partition to be imported.

area_name

Shows the name of the DEDB area to be imported.

The Statistics Data Import Utility will replace the utility history data with the new one.
System action: Processing continues.
User response: None. This message is informational.

 

BSN8048E INPUT SENSOR DATA IS OLDER THAN HISTORICAL SENSOR DATA.
 - THE LATEST RUN DATE OF INPUT SENSOR DATA: yyyy-mm-dd1
 - THE OLDEST RUN DATE OF HISTORICAL SENSOR DATA: yyyy-mm-dd2

Explanation: The set of sensor data to be imported is older than the oldest sensor data that was imported in the past.
yyyy-mm-dd1 is the latest date in the Run Date column of the CSV-formatted data set.
yyyy-mm-dd2 is the oldest date in the historical sensor data set.

System action: Processing ends with a return code of 8.
User response: Import sensor data whose Run Date value is newer than yyyy-mm-dd2.

 

BSN8049E DIFFERENT column_name IS SPECIFIED IN THE INPUT FILE.
 - CSV DATA SET NAME=data_set_name
 - LINE=line_number column_name=data_value.
Explanation: In a CSV-formatted data set, certain column values must be the same for all generations. The Statistics Data Import Utility detected a difference in the value data_value in the column column_name.
data_set_name is the name of the input CSV-formatted data set. line_number is the line number in the CSV file that caused the error.

System action: Processing ends with a return code of 8.
User response: Correct the error in the CSV-formatted data set.

 

BSN8050I COULD NOT ALLOCATE HISTORICAL DATA SET, WILL TRY TO ALLOCATE NEW DATA SET. RC=return_code, RSN=reason_code.
Explanation: The Statistics Data Import Utility failed to allocate a historical sensor data set dynamically with DISP=SHR.
The Statistics Data Import Utility will try to allocate a historical sensor data set dynamically with DISP=NEW.
The hexadecimal value return_code is the return code from SVC99. The hexadecimal value reason_code represents the S99ERROR and S99INFO contents.

System action: Processing continues.
User response: None. This message is informational.

 

BSN8051E DATE VALUES IN RUN DATE COLUMN MUST BE IN DESCENDING SEQUENCE.
 - CSV DATA SET NAME=data_set_name
Explanation: The sensor data in the CSV-formatted data set is not sorted in descending order.

System action: Processing ends with a return code of 8.
User response: Sort the data by the Run Date column in descending order.

 

BSN8052E DSG ID dsg_id IS SPECIFIED IN MULTIPLE INPUT FILES.
Explanation: Data set group ID dsg_id is specified in the DSG ID column of more than one input CSV-formatted data set.
System action: Processing ends with a return code of 8.
User response: Specify a unique data set group ID for each input CSV-formatted data set.

 

BSN8053E DATABASE TYPE IS NOT APPROPRIATE FOR THE INPUT FILE SPECIFIED BY keyword KEYWORD.
Explanation: The Statistics Data Import Utility detected one of the following conditions:
 - The input file specified by the CSV_DB or CSV_DSG keyword was sensor data for a DEDB area.
 - The input file specified by the CSV_AREA keyword was sensor data for a full-function database.
System action: Processing ends with a return code of 8.
User response: Correct the keyword specification for the input data set.
End of change

============================

Topic: Troubleshooting > Return and reason codes 

The following topic has been added:

Start of changeReturn codes: Statistics Data Import Utility

The Statistics Data Import Utility ends with one of the following return codes:

Table. Return codes reported by Statistics Data Import Utility

Return code Description User response
0 Job successfully ended. None.
4 Job ended with a warning message. Check the messages whose message numbers are suffixed by ’W’. If this is not the expected result, correct the error, and rerun the job.
8 Job ended with an error message. Check the messages whose message numbers are suffixed by ’E’. Correct the error, and rerun the job.
12 Job abnormally ended and recovered by ESTAE routine. This might be an internal system error. Contact IBM Software Support.
16 Job failed to initialize the BPE environment. Correct any errors, and rerun the job. If this situation persists, contact IBM Software Support.

End of change



Publication Number

SC19-4374-03

Copyright Date

2010, 2019

Document information

More support for: IMS Tools

Component: IBM Tools Base

Software version: 1.6.0

Operating system(s): z/OS

Software edition: SC19-4374-03

Reference #: 0886525

Modified date: 01 July 2019