While under CA Datacom/DB 11.0 SP02, we used a DIAGOPTION 9,32,ON which is not documented. How to handle for upgrades?

Products

• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• Datacom/AD
• CA ecoMeter Server Component FOC
• EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA On Demand Portal
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Question:

While under CA Datacom/DB 11.0 SP02, we used a Datacom Multi-user startup option DIAGOPTION 9,32,ON. I am preparing for the upgrades to a supported release and see that DIAGOPTION 9,32,ON is not documented in the current CA Datacom/DB Database and System Administration guide. What is the startup equivalent?

Answer:

Startup option DIAGOPTION 9,32,ON should be replaced by FORCE_NO_64BIT YES.

Additional Information:

FORCE_NO_64BIT is documented in the CA Datacom/DB Database and System Administration guide:

"...

(Optional) (z/OS only) In z/OS environments where support for z/OS 64-bit is available, you can force data space usage instead of 64-bit usage for Covered and Virtual areas by specifying this MUF startup option as YES. This option is allowed only when done as part of a Multi-User Facility enable.

In addition to requiring 64-bit hardware and the correct z/OS release, support for 64-bit is not available if the Multi-User Facility initiator has had a subspace used in the past. CA Datacom attempts to detect this condition and, when found, not to utilize 64-bit memory in order to prevent a system abend DC2 with a reason x'0012'. However, because detecting that a subspace has been used in the past is not always possible, we recommend that the Multi-User Facility be a started TASK or run with a class-initiator that does not allow CICS execution.

For more information on support for z/OS 64-bit in z/OS environments, see z/OS 64-Bit Support (see page 214) for the COVERED MUF startup option and z/OS 64-Bit Support (see page 306) for the VIRTUAL MUF startup option.

Specify YES to force data space usage instead of 64-bit usage in z/OS environments where support for z/OS 64-bit is available.

Valid Entries:

YES or NO

Default Value:

NO

..."

Environment

Release:
Component: DB