×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
MainView AutoOPERATOR 8.2 MainView AutoOPERATOR Customization Guide

Changing the use of CICS recoverable temporary storage

BMC Software occasionally starts a CICS transaction by using interval control services. This type of transaction must complete processing because of existing recoverable temporary storage definitions in the CICS Temporary Storage Table (TST).

If a conflict exists between the BMC Software temporary storage prefix and an existing temporary storage definition, the prefix that is used by BMC Software (CMRI) must be changed by applying the following ZAP:

NAME CMRINT2 CMRINT2
VER  00BC    C3D4D9C9
REP  00BC    xxxxxxxx (any nonrecoverable prefix)

For information about how to determine whether a conflict exists between the BMC Software temporary storage prefix and an existing temporary storage definition, refer to

  • Implementing BBI-SS PAS to CICS communication when implementing MainView AutoOPERATOR for CICS only

  • "Implementation Considerations" in the section "Standard Implementation Procedures" in the MainView for CICS Customization Guide.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Last modified by Margaret Yen on Dec 08, 2018

Comments

Log in or register to comment.

Issuing DBCTL commands
CICS transaction and program names
© Copyright 2013 - 2018 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.