MBC21

MacKinney Batch to CICStm
Installation and User Guide

Release 2.1
(c) Copyright 2006, 2021
tm
CICS is a trademark of IBM Corporation
Revised 06/25/2021
Confidentiality Notice
The information contained in this manual is a proprietary product of MacKinney Systems. The
use of this manual is authorized through a License Agreement for the exclusive use of the
Buyer. This manual or any part thereof may not be reproduced, copied, or in any manner
altered without the express written consent of MacKinney Systems. However, this manual may
be reproduced or copied by the Buyer for exclusive internal use only without written consent.
The use of the information contained in this manual by a third party without the express written
consent of MacKinney Systems is strictly forbidden.
Copyright 2006,2021 - All Rights Reserved

MacKinney Systems, Inc.
(417) 882-8012
e-mail sales@mackinney.com
WWW.MACKINNEY.COM
Removal of this confidentiality notice from this manual is contrary to the terms of the License Agreement.
MacKinney Systems
MacKinney Batch to CICS

Table of Contents
Installation Information
0.1 Introduction ............................................................................................................................................. 9

0.2 Environments Supported ....................................................................................................................... 10
0.3 Summary of Changes from Prior Releases ........................................................................................... 11
0.4 Related Products ................................................................................................................................... 13
0.4.1 CICS/Message .............................................................................................................................. 13
0.4.2 CEMT from Batch ........................................................................................................................ 13
0.5 Installation File Contents ...................................................................................................................... 14
Section I
Installation Guide
1.1 Steps for Installing MacKinney Batch to CICS .................................................................................... 16
1.1.1 New z/OS Installation Instructions [ZNew] ................................................................................. 17
1.1.2 Converting from CMT z/OS Installation Instructions [ZCnv] ..................................................... 18
1.1.3 New VSE Installation Instructions [VNew] ................................................................................. 19
1.1.4 Converting from CMT VSE Installation Instructions [VCnv]...................................................... 20
1.1.5 Upgrading from a Previous Release of MBC [Upgd] ................................................................... 21
1.1.6 Upgrading Current Release to a new PTF Level .......................................................................... 28
1.2 MBC VSAM Files [ZNew] [ZCnv] [VNew] [VCnv] ........................................................................... 29
1.2.1 Defining and Loading the BATCNTL File [ZNew] [ZCnv] [VNew] [VCnv] ............................. 29
1.2.1.1 Loading Help Screens in the BATCNTL File [ZNew] [ZCnv] [VNew] [VCnv]................. 29
1.2.2 Defining and Loading the BATSTAT File [ZNew] [ZCnv] [VNew] [VCnv] ............................. 29
1.2.3 Defining and Loading the BATCSTS File [ZNew] [ZCnv] [VNew] [VCnv] .............................. 29
1.3 Defining MBC CICS Resource Definition Entries [ZNew] [ZCnv] [VNew] [VCnv].......................... 30
1.3.1 Defining MBC Programs and Transactions [ZNew] [ZCnv] [VNew] [VCnv] ............................ 30
1.3.2 Defining SHUT Terminal Definition [ZNew] [ZCnv] [VNew] [VCnv] ...................................... 30
1.3.3 Defining SIT Entries [ZNew] [ZCnv] [VNew] [VCnv] ............................................................... 30
1.3.4 Defining MBC CICS File Definitions [ZNew] [ZCnv] [VNew] [VCnv]..................................... 31
1.4 Preparing for EXCI Use [ZNew] [ZCnv] ............................................................................................. 32
1.4.1 Verifying EXCI Options (DFHXCOPT) [ZNew] [ZCnv] ............................................................ 32
1.4.2 Defining Connection and Sessions Entries [ZNew] [ZCnv]......................................................... 32
1.5 Preparing for TCP/IP Use [VNew] [VCnv] .......................................................................................... 33
1.5.1 IP Stack Considerations [VNew] [VCnv] ..................................................................................... 33
1.5.2 Verifying Standard Listener Support [VNew] [VCnv] ................................................................. 33
1.5.3 Defining Domain Applid Records [VNew] [VCnv] ..................................................................... 33
1.6 Customization Steps [ZNew] [ZCnv] [VNew] [VCnv] ........................................................................ 34
1.6.1 GRS Considerations [ZNew] [ZCnv] ........................................................................................... 34
1.6.2 Running MBC across Multiple Systems (Images) [ZNew] [VNew] ............................................ 34
1.6.3 CA-Datacom/DB Users [ZNew] [ZCnv] [VNew] [VCnv] ........................................................... 34
1.6.4 VSE DL/I Users [VNew] [VCnv] ................................................................................................. 34
1.6.5 Converting CEMT from Batch MTPFLIST [ZCnv] [VCnv]........................................................ 34
1.7 Pre-Testing [ZNew] [ZCnv] [VNew] [VCnv] ...................................................................................... 35
1.7.1 Making Programs Available for CICS Access [ZNew] [ZCnv] [VNew] [VCnv] ........................ 35
1.7.2 Converting CEMT from Batch BATCNTL File [ZCnv] [VCnv] ................................................. 35
1.7.3 Making Files Available for CICS Access [ZNew] [ZCnv] [VNew] [VCnv] ............................... 35
1.7.4 Updating the Product Password [ZNew] [VNew] ........................................................................ 36
1.7.5 Customizing Installation Options [ZNew] [VNew]...................................................................... 36
1.7.6 Removing MTPSTATR from PLTPI [ZCnv] [VCnv].................................................................. 36
1.7.7 Copying EXCI modules from SDFHEXCI [ZNew] [ZCnv] ........................................................ 36
1.7.8 Reviewing Security Considerations [ZNew] [ZCnv] [VNew] [VCnv] ........................................ 36
1.7.9 Operational Differences Compared to CEMT from Batch [ZCnv] [VCnv] ................................. 36
1.8 Testing [ZNew] [ZCnv] [VNew] [VCnv] ............................................................................................. 37
1.8.1 Sample JCL for Executing MBCBATCH [ZNew] [ZCnv] [VNew] [VCnv] ............................... 37
1.9 Preparing for Production [ZNew] [ZCnv] [VNew] [VCnv] ................................................................. 39
1.9.1 Converting CEMT from Batch BATSTAT File [ZCnv] [VCnv] .................................................. 39
1.9.2 Renaming Files for Cutover [ZCnv] [VCnv] ................................................................................ 39
1.9.3 Swapping out Files in CICS [ZCnv] [VCnv]................................................................................ 39
1.9.4 Sharing BATCNTL and BATSTAT Files [ZNew] [VNew] ........................................................ 39
1.9.5 Reviewing Installation Options [ZCnv] [VCnv]........................................................................... 39
1.9.6 Making MBC Modules available for Batch Access [ZCnv] [VCnv]............................................ 40
1.9.7 Defining PLT Entries [ZNew] [ZCnv] [VNew] [VCnv] .............................................................. 40
1.9.8 Defining Domain Applid Records [VNew] [VCnv] ..................................................................... 40
1.9.9 Security Differences between Test and Production [ZNew] [ZCnv] [VNew] [VCnv] ................ 41
Section II
Special Considerations
2.1 General Considerations [ZNew] [ZCnv] [VNew] [VCnv] ................................................................... 42
2.1.1 MBC Timeout Considerations [ZNew] [ZCnv] [VNew] [VCnv] ................................................ 42
2.1.2 Consideration if Autoinstalling programs [ZNew] [ZCnv] [VNew] [VCnv] ............................... 42
2.1.3 CICS Down / Applid Status Tracking [ZNew] [ZCnv] [VNew] [VCnv] ..................................... 42
2.1.4 TCP/IP Debugging [VNew] [VCnv] ............................................................................................ 43
2.1.5 Handling Extended Data [ZNew] [ZCnv] [VNew] [VCnv] ......................................................... 43
2.1.5.1 Sample Extended Data Log [ZNew] [ZCnv] [VNew] [VCnv]............................................. 44
2.1.6 Running with EXCI Session Userid [ZNew] [ZCnv] ................................................................... 44
2.1.7 Transient Data Queue Handling ................................................................................................... 45
2.1.8 DL/I File Handling for z/OS ......................................................................................................... 45
2.2 Conversion Considerations [ZCnv] [VCnv] ......................................................................................... 46
2.2.1 Installation Option Changes [ZCnv] [VCnv]................................................................................ 46
2.2.2 Message and Logging Changes [ZCnv] [VCnv] .......................................................................... 46
2.2.3 New, Modified and Removed Commands [ZCnv] [VCnv] .......................................................... 47
2.2.4 Changes in Dynamic Allocation [ZCnv] [VCnv] ......................................................................... 48
2.2.5 Source Code Modifications [ZCnv] [VCnv] ................................................................................ 48
2.2.6 File Status Tracking Changes [ZCnv] [VCnv] ............................................................................. 48
2.2.7 Using BATCNTL Domain Applid Records to Limit Access [ZCnv] [VCnv] ............................. 48
2.2.8 Security Conversion Considerations [ZCnv] [VCnv] ................................................................... 49
2.2.9 Tips to avoid Production JCL Changes [ZCnv] [VCnv] .............................................................. 49
2.3 Security Considerations [ZNew] [ZCnv] [VNew] [VCnv] ................................................................... 50
2.3.1 Security Overview [ZNew] [ZCnv] [VNew] [VCnv] ................................................................... 50
2.3.1.1 Securing access to the MBC CICS server ............................................................................ 50
2.3.1.2 Securing your CICS resources (files and transactions) ........................................................ 50
2.3.2 Securing MBC CICS Transactions [ZNew] [ZCnv] [VNew] [VCnv] ......................................... 51
2.3.3 Securing MBC Files [ZNew] [ZCnv] [VNew] [VCnv] ................................................................ 53
Section III
Administration
3.1 Administration Overview...................................................................................................................... 54
3.2 The Administration Menu ..................................................................................................................... 55
3.3 Password Maintenance.......................................................................................................................... 56
3.3.1 Installation Passwords via Batch .................................................................................................. 56
3.4 Installation Options ............................................................................................................................... 57
3.4.1 Installation Options via Batch....................................................................................................... 60
3.4.2 Online APPLID Number/Name Screen ........................................................................................ 61
3.5 Display PTFs and Level Set .................................................................................................................. 62
3.5.1 Level Set via Batch ....................................................................................................................... 62
3.6 Applid Groups (ApplGrps) ................................................................................................................... 63
3.6.1 Defining ApplGrps to Use With Shared Resources ...................................................................... 63
3.6.2 ApplGrp Directory Screen – MBCL............................................................................................. 63
3.6.3 ApplGrp Update Screen ................................................................................................................ 64
3.6.4 ApplGrp Copy Screen................................................................................................................... 66
3.6.5 ApplGrp Via Batch (MBCBAGRP) ............................................................................................. 67
3.7 Resource Items ...................................................................................................................................... 68
3.7.1 Shared and Non-Shared Resource Items....................................................................................... 68
3.7.2 Resource Item Directory Screen – MBCI ..................................................................................... 68
3.7.3 Resource Item Update Screen ....................................................................................................... 70
3.7.3.1 Resource Items (FI) .............................................................................................................. 71
3.7.3.2 Resource Items (PG)............................................................................................................. 72
3.7.3.3 Resource Items (TR)............................................................................................................. 73
3.7.3.4 Resource Items (IP) .............................................................................................................. 74
3.7.3.5 Resource Items (TD) ............................................................................................................ 75
3.7.3.6 Resource Items (TX) ............................................................................................................ 76
3.7.4 Resource Item Update via Batch (MBCBRITM) ......................................................................... 77
3.7.5 Resource/Group XREF Screen ..................................................................................................... 79
3.8 Resource Groups ................................................................................................................................... 80
3.8.1 Shared and Non-Shared Resource Groups.................................................................................... 80
3.8.1.1 Using Shared Resource Groups ............................................................................................ 81
3.8.2 Group Directory Screen – MBCG ................................................................................................ 84
3.8.3 Group Define Screen .................................................................................................................... 86
3.8.4 Group Maintenance Screen........................................................................................................... 87
3.8.4.1 Group Item Selection Screen ................................................................................................ 88
3.8.5 Group Copy Screen....................................................................................................................... 90
3.8.6 Group Operation Screen – MBCO................................................................................................ 92
3.8.7 Group Status Screen – MBCS ...................................................................................................... 93
3.8.8 Resource Groups via Batch (MBCBRGRP) ................................................................................. 94
3.9 Status Tracking Maintenance ................................................................................................................ 96
3.9.1 Status Tracking Maintenance Screen – MBC1 ............................................................................. 96
3.9.2 Status Tracking Detail Screen....................................................................................................... 97
3.9.3 Status Tracking Batch Maintenance ............................................................................................. 98
3.9.3.1 MBCBCSTS ......................................................................................................................... 98
3.9.3.2 MBCBSTAT......................................................................................................................... 99
3.10 Domain Applids ................................................................................................................................ 100
3.10.1 Domain Directory Screen – MBCD.......................................................................................... 100
3.10.2 Domain Update Screen ............................................................................................................. 101
3.10.3 Domain Applids via Batch (MBCBDOM) ............................................................................... 102
Section IV
Batch Programs and Procedures
4.1 Batch Client (MBCBATCH) Overview.............................................................................................. 103
4.1.1 Linking to MBCBATCH from your Application ....................................................................... 104
4.1.2 MBCBATCH Return Codes ....................................................................................................... 104
4.1.3 Sample Batch Job Log ................................................................................................................ 105
4.2 Batch Utilities ..................................................................................................................................... 107
4.2.1 MBCBCUTL .............................................................................................................................. 107
4.2.2 MBCBCNV ................................................................................................................................ 109
4.2.3 MBCBCNVS .............................................................................................................................. 109
4.2.4 MBCBCNVR.............................................................................................................................. 110
4.2.5 MBCBCNV2 .............................................................................................................................. 110
4.2.6 MBCBCPRT ............................................................................................................................... 111
4.3 Batch User Exits ................................................................................................................................. 112
4.3.1 Header Exit MBCBHDRX ......................................................................................................... 112
4.3.2 Command Exit MBCBCMDX.................................................................................................... 112
4.3.3 Pre-Execution Exit MBCBPREX ............................................................................................... 112
4.3.4 Job Log Exit MBCBLOGX ........................................................................................................ 112
4.3.5 Extended Data Log Exit MBCBLXGX ...................................................................................... 112
4.3.6 Command Return-code Exit MBCBCRCX ................................................................................ 113
4.3.7 Open BATSTAT Exit MBCBOPSX (z/OS only)....................................................................... 113
4.3.8 WTO Exit MBCBWTOX ........................................................................................................... 113
Section V
Command Descriptions and Syntax
5.1 Command Summary ........................................................................................................................... 114
5.1.1 Related Commands ..................................................................................................................... 115
5.2 Command Syntax ................................................................................................................................ 116
* (Comment) ........................................................................................................................................ 116
ALOC / ALOQ .................................................................................................................................... 117
ALOG / ALSG..................................................................................................................................... 117
ALOR / ALSR ..................................................................................................................................... 118
APPL ................................................................................................................................................... 118
CDAL .................................................................................................................................................. 119
CEDA .................................................................................................................................................. 120
CEMT PERFORM............................................................................................................................... 121
CEMT SET / DISCARD / INQUIRE .................................................................................................. 121
CICS / CSCQ ....................................................................................................................................... 122
CLOS / CLOG / CLOD / CLDG / CLOV / CLVG ............................................................................. 123
CSDA................................................................................................................................................... 124
CSDD................................................................................................................................................... 124
DBLC................................................................................................................................................... 124
DLOC .................................................................................................................................................. 124
DOWNSTS .......................................................................................................................................... 125
DSNC................................................................................................................................................... 125
ENAB / ENAG .................................................................................................................................... 125
GLSQ / GSSQ (RLS only) .............................................................................................................. 126
GLSU / GSSU (RLS only) .............................................................................................................. 126
GLQY / GPQY / GSQY (RLS only) ................................................................................................ 127
GLUP / GPUP / GSUP (RLS only) ................................................................................................. 127
IF / ELSE / ENDIF .............................................................................................................................. 128
INQY / INQG ...................................................................................................................................... 129
IPTR..................................................................................................................................................... 130
LINK / LNKL ...................................................................................................................................... 130
MESG .................................................................................................................................................. 131
MSGL .................................................................................................................................................. 131
NEWC ................................................................................................................................................. 132
OPEN / OPEG ..................................................................................................................................... 132
OPTR ................................................................................................................................................... 133
PHAS ................................................................................................................................................... 133
QRYL / QRYS ..................................................................................................................................... 134
RLQY / RPQY / RSQY (RLS only) ................................................................................................. 135
RLSQ / RPSQ / RSSQ (RLS only) .................................................................................................. 135
RLSU / RPSU / RSSU (RLS only) ................................................................................................. 136
RLUP / RPUP / RSUP (RLS only) .................................................................................................. 136
SAPL ................................................................................................................................................... 137
SET ...................................................................................................................................................... 137
SHUT ................................................................................................................................................... 138
STAR DBOC ....................................................................................................................................... 138
STAR / STRL ...................................................................................................................................... 139
STSD ................................................................................................................................................... 140
STSR / STSG ....................................................................................................................................... 140
UNAL / UNAQ.................................................................................................................................... 141
UNAR / UNAG ................................................................................................................................... 141
UPDT / UPDG ..................................................................................................................................... 142
WAIT ................................................................................................................................................... 142
Section VI
Online Programs and Procedures
6.1 Online Overview ................................................................................................................................. 143
6.2 Online Command Processor................................................................................................................ 143
6.2.1 Linking to the Online Command Processor ................................................................................ 144
6.3 Task Delay Utility (MBCPSCN) ........................................................................................................ 144
6.4 Command User Exit (MBCPCMDX) ................................................................................................. 144
6.5 BATSTAT Reset Clean-up Exit (MBCPRSTX)................................................................................. 144
6.6 Sample CICS Log ............................................................................................................................... 145
Section VII
Status Tracking
7.1 Status Tracking Overview................................................................................................................... 146
7.1.1 New Broadened Status Tracking Scope...................................................................................... 146
7.1.2 Startup Manager.......................................................................................................................... 146
7.2 Status Tracking Operation .................................................................................................................. 147
7.2.1 Using Status Tracking without Startup Manager ........................................................................ 147
7.2.2 Using Status Tracking with the Startup Manager ....................................................................... 148
7.2.3 Status Tracking Administration .................................................................................................. 149
7.2.4 Starting PLT Resource Allocation .............................................................................................. 149
7.2.5 Starting Reset Processing from PLT........................................................................................... 149
7.2.6 Modifying MBCBATCH JCL for Status Tracking .................................................................... 150
7.2.7 Periodic Maintenance of the BATSTAT File ............................................................................. 150
7.2.8 Periodic Maintenance of the BATCSTS File.............................................................................. 150
7.3 Status Tracking Batch Utilities ........................................................................................................... 151
7.3.1 BATSTAT Utility (MBCBSUTL) .............................................................................................. 151
7.3.2 Pre-CICS Startup Utility (MBCBCPRE) .................................................................................... 152
7.4 Sample PLT Resource Allocation CICS Log...................................................................................... 153
7.5 Sample Status Tracking Reset Processing CICS Log ......................................................................... 154
Section VIII
Startup Commands
8.1 Startup Commands Overview ............................................................................................................. 155
8.1.1 Storing Startup Commands ......................................................................................................... 155
8.1.2 Executing Startup Commands .................................................................................................... 156
8.1.3 Deleting Startup Commands ....................................................................................................... 156
Section IX
Messages and Codes
9.1 Messages ............................................................................................................................................. 157
9.2 ABEND Codes from Online Programs ............................................................................................... 187
APPENDIX A - EIBFN ............................................................................................................................ 188

APPENDIX B - EIBRCODE .................................................................................................................... 189
APPENDIX C – Running IP Trace ........................................................................................................... 190
APPENDIX D – File List Processing ....................................................................................................... 193
APPENDIX E – CICS System Number and APPLIDs ............................................................................ 195
APPENDIX F – Message Cross Reference .............................................................................................. 196
APPENDIX G – MBCE128 Error Codes ................................................................................................. 197
Index ......................................................................................................................................................... 199

MacKinney Systems
MacKinney Batch to CICS

Installation Information
0.1 Introduction
MacKinney Batch to CICS (MBC) is a software tool to coordinate and control resources and provide general
communication between batch and CICS. MBC uses EXCI (z/OS) or TCP/IP (VSE), both very fast communication
protocols, to route commands from the batch client to the CICS server. Using MBC, you control resources status for files,
RLS datasets, programs, transactions, TCPIP services and TDQs, from the batch client (MBCBATCH) and online with
the Online Command Processor or Administration screens.
Besides controlling the status of supported resources, MBC also provides commands for launching transactions, linking to
programs, sending terminal messages, plus many more, including batch support for CEMT and CEDA commands. For a
complete list of functions, see Section 5. MBC communicates with multiple CICS systems on multiple CPU images or
VM machines.
MacKinney Batch to CICS Administration provides the building blocks to match your environmental needs to your
resources including Resource Groups, Resource Items and Applid Groups. Resource Items allows defining specific
resource handling and identification characteristics. Resource Groups allow grouping Resource Items and allocating or
unallocating all of the member resources with a single command. Applid Groups allows targeting multiple regions with a
single command. Administrative tasks can be handled using one of the many provided batch utilities or online screens.
MacKinney Batch to CICS includes a Status Tracking feature, used to save the last status of CICS resources (files,
transactions, programs and TDQs) and reset their status after CICS is re-cycled. MBC also includes a Startup Manager to
define startup preferences for individual resource on the Resource Item records. The Startup Manager works with Status
Tracking to allow sharing a CSD file with several regions. See Section 7 for a more detailed explanation on using the
Status Tracking and Startup Manager functions.
• MBC uses an EXCI or TCP/IP interface for quick connections between batch and CICS
• Interface with your external security manager for complete resource security
• IF/ELSE/ENDIF logic to allow conditional execution of commands
• SET logic allows overriding return codes to alter JOB flow
• Startup Manager provides allocation and open preferences including DSN handling to allow shared CSDs
• Applid Groups allow routing commands to up to 999 Applids with a single command
• Resource Groups allow up to 999 file/transaction/program/TDQ/TCPIP service resources to allocate or unallocate
with a single command using group commands (ALOG, ALSG, UNAG and more)
• Resource Items allow defining Startup Manager and other handling preferences for individual resources
• Both local (unique to each region) and shared (common amongst all regions) Resource Items are allowed
• Command pre-processor User Exits in Batch and CICS allows sending and processing your own internal commands
• The command User Exit allows blocking commands based on the Userid and the target CICS Applid
• Support for RLS datasets
• Open and close CICS files with an optional verify on the close
• Allocate or unallocate CICS files
• Allocate or unallocate TD Queues (z/OS only)
• Change file attributes from update to read-only and back as required
• Issue CEDA commands from batch, including INSTALL
• Support for DL/I files
• Start and stop the DB2 interface (z/OS only)
• Open and close CA-Datacom/DB databases
• NEWCOPY or PHASEIN programs
• Initiate a CICS Shutdown (this command can be restricted or not allowed)
• Link to programs passing an optional Commarea
• Start a transaction with optional parameters for Userid, Termid, data length and data
Installation Information 9
0.2 Environments Supported
MacKinney Batch to CICS (MBC) requires a minimum CICS level of TS 1.3 for z/OS or TS 1.1 for z/VSE. CICS 2.3 for
z/VSE is not supported. MBC is not dependent on the release of z/OS or z/VSE as long as the operating system is running
supported versions of CICS.
MVS
EXCI is the default communication method enabled within MBC for MVS users. To use TCP/IP, contact MacKinney
Systems to discuss enabling TCP/IP for MVS. Support for EXCI across MVS images requires XCF/MRO links (Sysplex)
be defined. See also the ENQXS Installation Option in Section 3.4 to cross system ENQs.
VSE
TCP/IP support was added for z/VSE because EXCI support for z/VSE does not support cross-systems communications.
This limited MBC to only sending commands to CICS regions on the same image. If all of your CICS regions are on the
same image, contact MacKinney Systems to discuss enabling EXCI for VSE. Other users, see Section 1.5 for TCP/IP
requirements which are dependent on the vendor’s stack you are running. RLS commands are not supported for z/VSE.
10 Installation Information
0.3 Summary of Changes from Prior Releases
Summary of Changes for MacKinney Batch to CICS 2.1
• New Startup Commands feature: process MBC commands during CICS startup
• New USER= parm on STRL command to Start transaction with USERID
• New CLOD and CLDG commands to force disable file option on close regardless of CLODIS setting
• New batch utility MBCBSTAT to support defining, listing and deleting BATSTAT records
• New batch utility MBCBCSTS to print and delete BATCSTS records
• New STSD command to delete Resource Items from BATCSTS file
• New value ‘F’ for APPLSTS option to flush commands but still add commands to BATSTAT
• New ERRDRLS installation option to allow setting separate RC value when using @RLS1GRP header
• New USEPCH card option for batch utility programs to automate creation of DEF cards on LST output
• New user exit, MBCBWTOX for MBCBATCH WTO messages
• New commands RLQY/RPQY/RSQY/GLQY/GPQY/GSQY change Quiesced RLS resources to read-only
• New commands RLUP/RPUP/RSUP/GLUP/GPUP/GSUP change Unquiesced RLS resources to update
• New commands RPSQ/RPSU/GPSQ/GPSU to Quiesce/Unquiesce Primary RLS DSN
• New commands RSSQ/RSSU/GSSQ/GSSU to Quiesce/Unquiesce Secondary RLS DSN
• Status Tracking and command support for new TCPIP services Resource Item type
• New Query options for TCPIPSERVICE, DOCTEMPLATE, URIMAP (z/OS only)
• Added support for new Startup Manager

• Added support for new Resource Items including Startup Manager options
• Pushed Status Tracking from batch to CICS and added new Status Tracking administration programs
• Added new file BATCSTS to support Status Tracking from within CICS
• New CEDACMD option to allow prevention of CEDA and CDAL commands
• New LNKL and STRL commands allow passing up to 320 bytes of data to LINK and START functions
• Optionally save LINK/LNKL and STAR/STRL commands for Status Tracking with new ‘$’ parm
• New STSR and STSG commands to support synchronizing status updates performed outside of MBC
• New API link interface to process application commands through the Online Command Processor
• MBCBCUTL now allows INIT function for all Installation Options
• Added DSN edit for RLS commands
• Added STAR MBCP option to launch applications requiring RECEIVE data
• New ERRWARN option to allow optional RC value for warning conditions
• New TRKNONFI option to optionally allow tracking programs, transactions, TCPIP services and TDQs
• New Shared Resource Items added with fix level 2.0.12
• Added support for multiple administrators in a region at the same time

• Added IPV6 support for IP version
• Added Single Execution Userid support for IP version to route all commands through a single userid
• Added new CEDA and CDAL commands to utilize the CEDA API from a batch job
• Added new parm “?” to hide errors for PHAS and NEWC commands so command can be sent to all
regions even when a program is not installed without incurring an error
• Added installation option LOGXDD in support of an optional SYSLSTX DD (z/OS) or ASSGN (VSE) to
separate extended data returned by CEDA, CDAL, QRYL, QRYS and CEMT commands
• Added new user exit MBCBLXGX to allow user control of data written to the extended data log
• Added installation option EMTMSGS in support of returning extended data output for all CEMT
commands or only CEMT INQUIRE commands
• Enhanced CEMT command support to return extended status and error messages
• Added support of TDQ resources in Resource Groups
• Added QRYL and QRYS commands to perform formatted CICS resource queries from batch
• Alter MBCB path to only modify read-only status if file is initially closed and set for update
• Added MBCBAGRP utility to support defining, listing and deleting APPLGRP records
• Added Resource Group support for RLSQ | RLSU commands by adding GLSQ | GLSU commands
• Added INIT CMDEXIT and INIT OPTS functions to MBCBCUTL
• MBCBCUTL PASS function performs an implicit INIT OPTS function if Options Record is uninitialized
• Status Tracking Utility MBCBSUTL now supports generic resource names in PRT/DEL functions
• Added LSTGRP, LSTALL, DELGRP and DELALL functions to MBCBRGRP utility
• Added LSTDOM function to list Domain Applid records in MBCBDOM utility
• Prevent CEMT SET PROG(value) NEWCOPY|PHASEIN from being loaded to Status Tracking
• Added new optional warning return code to set MAXCC=2 to return code exit MBCBCRCX
• Added View option to MBCS group status fast path transaction
• Support for dynamic modification of BATCNTL file to updatable added for administration (MBCA)
• Added new transaction MBCB for read-only access to administration panels
• Added LIST OPTS report to MBCBCUTL
• Added INIT ENQXS and INIT DOMSEC options to MBCBCUTL to aid in CEMT from Batch migration
allowing these new key installation options to initialize from batch
• Re-organized manual to include multiple installation paths
• Support for RLS commands RLSQ (QUIESCE) and RLSU (UNQUIESCE)

• Support for RLS1GRP to assist in RLS broadcast (first active Applid in group is used as target)
• Domain Applids support to assist in securing target CICS regions within a BATCNTL file domain
• New DOMSEC option added to allow choosing optional Applid access security using Domain Applids
• Fast path Tranid MBCD added for administering Domain Applids
• Added MBCBDOM batch utility for maintaining Domain Applid records via batch
• New TCP/IP version added to lift VSE restriction of target being in same CPU image
• IP Port and Address added to Domain Applid records to identifying target IP Address for TCP/IP version
• New DPWD function added to MBCBCUTL to allow batch delete of product Password
• New List Group Resources for Applid by Group Name report added to MBCBCUTL
• Improved handling of VSAM errors in batch utilities
• Added new ERRSTS option to support for return code from BATSTAT errors
• Improved security and error recovery for Status Tracking Reset Processing function
• Support for alternate DSNAME added to Status Tracking
• New LOADPGM option to issue LOAD PROG before PHAS/NEWC and CEMT SET PROG commands
to give users more flexibility in support of program autoinstall

• VSE EXCI support added (same CPU image only)
• Support for lower-case reply for options supporting WTOR
• Enqueue failures now result in RC=4 being set in addition to message
• Performance improvement on batch logging
• Command Return-code user exit MBCBCRCX added
• Support for tracking CICS down status added with new SAPL command and APPLSTS option
• BATSTAT open user exit added to allow dynamic allocation of the BATSTAT file (z/OS only)
• MBCB006-MBCB008 messages modified to allow for CICS down status tracking
0.4 Related Products
MacKinney Batch to CICS interfaces with CICS/Message with the MESG and MSGL MBCBATCH commands.
0.4.1 CICS/Message
CICS/Message allows sending messages to:
∙ an individual CICS terminal or Netname

∙ an individual CICS userid or operator-id (OPID)
∙ all CICS terminals (including console operator)
∙ all CICS terminals matching a generic terminal or Netname
∙ all CICS terminals matching a generic operator-id (OPID)
∙ all CICS terminals matching a generic userid
∙ all terminals/operators in a user specified list
∙ the computer operator (CONSOLE)
without destroying the contents of the user's current screen. CICS/Message is invoked
∙ by entering a CICS transaction, or
∙ via LINK from a user written COBOL or ASSEMBLER application program
If CICS/Message is installed, messages sent with MacKinney Batch to CICS are automatically routed through
CICS/Message preserving the user's current screen and transaction environment. NOTE: To use the MESG ALL
command, the latest release of CICS/Message is needed. Make sure a ‘=MBC’ entry is defined in the CICS/Message
ALL Authorization Table (see the CICS/Message manual).
For more information on, call, email or see our web site. Try it out with a free 30 day trial. Contact information can
be found on the second page of this manual or check our website www.mackinney.com.
0.4.2 CEMT from Batch

MacKinney Batch to CICS was a re-designed from the ground up to replace the functionality of the MacKinney System’s
CEMT from Batch product with several enhancements worth noting:
• Compatibility with CEMT from Batch command cards (standard usage requires no JCL changes)
• Uses the EXCI (z/OS) or TCP/IP (VSE) interface for much quicker connection from batch to CICS
• Added the ability to Secure commands based on the USERID associated with the batch job (requires an external
security manager such as RACF, ACF2 or Top Secret)
• Status Tracking processing redesigned to minimize contention to the BATSTAT file
• Added support for programs, transactions, TCPIP services and TDQs to status tracking
• Added IF/ELSE/ENDIF logic to allow conditional execution of commands
• Added SET logic to allow overriding the return codes
• Send commands to unlimited Applids (old limit was 99)
• Added Applid Groups which allow routing commands to up to 999 Applids
• Added Resource Groups which allows up to 999 file/transaction/program resources to allocate or unallocate with a
single command using new commands (ALOG, ALSG and UNAG)
• Added command pre-processor User Exits to Batch and CICS to allow customers to send their own internal commands
• Added a command User Exit to allow customers to disallow commands being sent based on the Userid and the
target CICS Applid
• Removed column dependency on the most common commands
• Added ability to override options for an individual job step with OPTR command
• Added QRYS and QRYL commands to query CICS resources from batch
• Added CEDA and CDAL commands allowing Installs and other commands from batch
• Added support for RLS
0.5 Installation File Contents
Source code
1. MBCFDFCT Batch buffer allocation macro

2. MBCFLIST CICS file table used in file list processing
3. MBCBCMDX Sample batch Command user exit
4. MBCBCRCX Sample batch Command Return-code exit
5. MBCBHDRX Sample batch CICS Header user exit
6. MBCBLOGX Sample batch job log user exit (SYSLST)
7. MBCBLXGX Sample batch extended data log user exit (SYSLSTX)
8. MBCBOPSX Sample batch BATSTAT open user exit (z/OS only)
9. MBCBPREX Sample batch pre-execution user exit
10. MBCBWTOX Sample batch WTO user exit
11. MBCM***H Help text for help screens
12. MBCPDLOC Program to handle DL/I commands (VSE only)
13. MBCPCMDX Sample online Command user exit
14. MBCPRSTX Sample program to submit MBCBSUTL job to clean-up BATSTAT records
15. SAMPLNK Sample link to MBCBATCH code
16. SAMPLNK2 Sample link to MBCBATCH code
17. COBB* Sample COBOL user exits
JCL
1. MBCJAGRP Sample JCL to run ApplGrp Utility

2. MBCJASM Sample JCL to assemble batch source
3. MBCJASMC Sample JCL to assemble CICS source
4. MBCJBAT Sample JCL to run program MBCBATCH
5. MBCJCNV Sample JCL to run BATCNTL conversion utility
6. MBCJCNVR Sample JCL to convert pre-MBC 2.0 Resource Items
7. MBCJCNVS Sample JCL to run BATSTAT conversion utility for CMT BATSTAT
8. MBCJCNV2 Sample JCL to convert pre-MBC 2.0 BATSTAT to 2.0 and up BATSTAT
9. MBCJCPRE Sample JCL to run MBCBCPRE for Startup Manager
10. MBCJCPRT Sample JCL to run Applgrp and Resource Group cross reference report
11. MBCJCSTS Sample JCL to run BATCSTS utility program
12. MBCJCUTL Sample JCL to run BATCNTL utility program
13. MBCJDOM Sample JCL to run Domain records batch utility
14. MBCJFILB JCL to define BATCNTL file and load from install tape
15. MBCJFILC JCL to define BATCSTS file and load from install tape
16. MBCJFILS JCL to define BATSTAT file and load from install tape
17. MBCJHELP JCL to load Help screens to BATCNTL file
18. MBCJLOAD Sample JCL to download libraries from tape
19. MBCJRDO RDO definitions for transactions and programs without administration
20. MBCJRDOA RDO definitions for transactions and programs with administration
21. MBCJRDOC RDO definitions for connection and sessions
22. MBCJRDOF RDO definitions for BATCNTL and BATSTAT files (read access)
23. MBCJRDOS RDO definition for BATCSTS file (update access)
24. MBCJRGRP Sample JCL to run Resource Group batch utility
25. MBCJRITM Sample JCL to run Resource Items batch utility
26. MBCJSTAT Sample JCL to run Status Tracking batch utility
27. MBCJSUTL Sample JCL to run BATSTAT utility program
28. MBCJZLU Sample JCL to optionally zap default LU for LOGXDD=Y VSE users
Object Modules
1. MBCBAGRPOM Batch utility program for ApplGrp records

2. MBCBATCH Batch client program
3. MBCBCNV Conversion utility for converting BATCNTL from MacKinney CEMT from Batch
4. MBCBCNVR Conversion utility for converting BATCNTL from pre-2.0 MacKinney Batch to CICS
5. MBCBCNVS Conversion utility for converting BATSTAT from MacKinney CEMT from Batch
6. MBCBCNV2 Conversion utility for converting BATSTAT from pre-2.0 MacKinney Batch to CICS
7. MBCBCSTS BATCSTS file utility program
8. MBCBCUTL BATCNTL file utility program
9. MBCBDOM Batch utility program for Domain Applid records
10. MBCBRGRP Batch utility program for Resource Group records
11. MBCBRITM Batch utility program for Resource Item records
12. MBCBSUTL BATSTAT file utility program
13. MBCB* Other batch utility programs and user exits
14. MBCF* Specialty batch programs
15. MBCP* CICS programs
16. MBCM* CICS maps
17. MBCR* Batch sub programs
Section I
Installation Guide
1.1 Steps for Installing MacKinney Batch to CICS
Download MacKinney Batch to CICS from our Web page at www.mackinney.com.
Unzip the file and follow the instructions on the MBC_READ.ME file to obtain the installation files.
After performing the preceding steps, you have all of the required product files to continue the installation.
There are five installation paths available. Each path uses its own color coded key to aid in identifying steps required on
a particular installation path. For ease of installation, print the one page overview of your installation path (Section 1.1.x)
to use as a checklist.
If you are a z/OS user installing MBC for the first time go to Section 1.1.1. [ZNew]
If you are a z/OS user converting from the CEMT from Batch product, go to Section 1.1.2. [ZCnv]
If you are a VSE user installing MBC for the first time go to Section 1.1.3. [VNew]
If you are a VSE user converting from the CEMT from Batch product, go to Section 1.1.4. [VCnv]
If you are upgrading from a previous release of MBC, go to Section 1.1.5. [Upgd]
If you are upgrading your current release to a new PTF (maintenance) level, go to Section 1.1.6.
16 Section I – Installation Guide

1.1.1 New z/OS Installation Instructions [ZNew]
The instructions in this section are for users installing Mackinney Batch to CICS on z/OS for the first time. If converting
from CEMT from Batch, go to Section 1.1.2. New z/OS MBC users will by default, be installing MBC with the EXCI
interface enabled. MBC can also be configured to use the TCP/IP interface, but this is only recommended if you have a
specific issue with using EXCI. Contact MacKinney Systems if you suspect an issue with EXCI and want to discuss
enabling the TCP/IP interface.
Use the following steps to install for a new z/OS installation for MacKinney Batch to CICS. If converting from CEMT
from Batch go to Section 1.1.2. If upgrading from a previous release of MBC, go to Section 1.1.5.
If this is your correct installation path, print this section to use as a checklist.
1. Review Section 1.2 Description of MBC Files

2. Define and load the BATCNTL file (Section 1.2.1).
3. Define and load the BATSTAT file (Section 1.2.2).
4. Define and load the BATCSTS files (Section 1.2.3).
5. Review Section 1.3 Defining MBC Resource Definition Entries
6. Define MBC Programs and Transactions (Section 1.3.1).
7. Define SHUT Terminal definition (Section 1.3.2).
8. Define SIT entries (Section 1.3.3).
9. Define MBC File definitions (Section 1.3.4).
10. Review Section 1.4 Preparing for EXCI Use
11. Verify your EXCI options (DFHXCOPT) (Section 1.4.1).
12. Define Connection and Session Entries for EXCI (Section 1.4.2).
13. Review Global Resource Serialization requirements (Section 1.6.1).
14. Review considerations for running MBC across multiple systems/Images/LPARs (Section 1.6.2)
15. CA-Datacom/DB users see Section 1.6.3.
16. Make the MBC loadlib available to CICS for testing (Section 1.7.1).
17. Make the MBC Files available for CICS Access (Section 1.7.3).
18. Add the required valid Product Password(s) provided by your vendor (Section 1.7.4).
19. Review and update Installation Options (Section 1.7.5).
20. Copy EXCI modules from SDFHEXCI (Section 1.7.7).
21. Review Security Considerations (Section 1.7.8).
22. MacKinney Batch to CICS is ready to test. Commands can be sent from batch using the batch client program
MBCBATCH. See Section 1.8.1 Sample JCL For Executing MBCBATCH.
23. After testing is complete, consider adding additional BATCNTL and BATSTAT files (Section 1.9.4)
24. Modify the PLT entries (Section 1.9.7).
25. Review Security differences between Test and Production (Section 1.9.9)
Section I – Installation Guide 17

1.1.2 Converting from CMT z/OS Installation Instructions [ZCnv]
The instructions in this section are for users installing Mackinney Batch to CICS on z/OS for the first time and you are
converting from CEMT from Batch. z/OS MBC users will by default, be installing MBC with the EXCI interface
enabled. MBC can also be configured to use the TCP/IP interface, but this is only recommended if you have a specific
issue with using EXCI. Contact MacKinney Systems if you suspect an issue with EXCI and want to discuss enabling the
TCP/IP interface.
NOTE: To parallel test your existing jobs using the new MBC environment alongside your existing CEMT from Batch
environment, do not update the file definitions for BATCNTL and BATSTAT until testing is complete. You will also
not be able to use Status Tracking or any group commands while parallel testing.
1. Review Section 2.2 in its entirety

7. Define MBC Programs and Transactions (Section 1.3.1)
8. Define SHUT Terminal definition (Section 1.3.2)
9. Define MBC SIT entries (Section 1.3.3)
10. Define MBC File definitions (Section 1.3.4) if you are NOT parallel testing.
11. Review Section 1.4 Preparing for EXCI Use
12. Verify EXCI Options (DFHXCOPT) (Section 1.4.1)
13. Define Connection and Session entries (Section 1.4.2)
17. Copy your MTPFLIST source and object to MBC as MBCFLIST (Section 1.6.5)
18. Make the MBC loadlib available to CICS for testing (Section 1.7.1)
19. Convert your CEMT from Batch BATCNTL file (Section 1.7.2). This step also loads your product password
and lets you set new installation options.
20. Make the MBC files available to CICS for testing (Section 1.7.3) if you are NOT parallel testing.
21. Remove MTPSTATR from PLTPI for migration testing (Section 1.7.6).
22. Copy EXCI modules from SDFHEXCI (Section 1.7.7).
24. Review Operational Differences between MBC and CEMT from Batch (Section 1.7.9).
26. Status Tracking users see CEMT from Batch BATSTAT file conversion options (Section 1.9.1)
27. Rename your files for Cutover (Section 1.9.2).
28. After testing is complete, swap out your old CEMT from Batch files (Section 1.9.3).
29. Review Installation Options (Section 1.9.5)
30. Make the MBC Modules available for Batch Access (Section 1.9.6).
31. After testing is complete modify the PLT entries (Section 1.9.7).

1.1.3 New VSE Installation Instructions [VNew]
The instructions in this section are for users installing MacKinney Batch to CICS on VSE for the first time. If you are
converting from CEMT from Batch go to Section 1.1.4. If you are upgrading from a previous release of MBC, go to
Section 1.1.5. VSE MBC users will by default, be installing MBC with the TCP/IP interface enabled. MBC can also be
configured to use the EXCI interface, but this is only recommended if you have a specific issue with using TCP/IP.
VSE/EXCI requires all of your CICS regions be in the same LPAR. Contact MacKinney Systems if you suspect an issue
with TCP/IP and want to discuss enabling the EXCI interface.

6. Define MBC Programs and Transactions (Section 1.3.1).
7. Define SHUT Terminal definitions (Section 1.3.2).
8. Define SIT entries (Section 1.3.3).
9. Define MBC File definitions (Section 1.3.4).
10. Review Section 1.5 Preparing for TCP/IP Use
11. Verify IP Stack (Section 1.5.1).
12. Verify Standard Listener Support (Section 1.5.2)
13. Define Domain Applid Records for target test regions (Section 1.5.3)
17. DL/I Users see Section 1.6.4.
19. Make the MBC Files available for CICS Access (Section 1.7.3).
20. Add the required valid Product Password(s) provided by your vendor (Section 1.7.4).
21. Review and update Installation Options (Section 1.7.5).
24. After testing is complete consider adding additional BATCNTL and BATSTAT files (Section 1.9.4)
25. Modify the PLT entries (Section 1.9.7).
26. Define Domain Records for target production regions (Section 1.9.8)

1.1.4 Converting from CMT VSE Installation Instructions [VCnv]
The instructions in this section are for users installing Mackinney Batch to CICS on VSE for the first time and you are
converting from CEMT from Batch. VSE MBC users will by default, be installing MBC with the TCP/IP interface
enabled. MBC can also be configured to use the EXCI interface, but this is only recommended if you have a specific
issue with using TCP/IP. VSE/EXCI requires all of your CICS regions be in the same LPAR. Contact MacKinney
Systems if you suspect an issue with TCP/IP and want to discuss enabling the EXCI interface.
NOTE: If you intend on parallel testing your existing jobs using the new MBC environment alongside your existing
CEMT from Batch environment, then do not update the file definitions for BATCNTL and BATSTAT until your testing
is complete. You will also not be able to use Status Tracking or any group commands while parallel testing.
1. Review Section 2.2 in its entirety
7. Define MBC Programs and Transactions (Section 1.3.1)
8. Define MBC SHUT Terminal definition (Section 1.3.2)
9. Define MBC SIT entries (Section 1.3.3)
10. Define MBC File definitions (Section 1.3.4) if you are NOT parallel testing
11. Review Section 1.5 Preparing for TCP/IP Use
12. Verify IP Stack (Section 1.5.1).
13. Verify Standard Listener Support (Section 1.5.2)
14. Define Domain Applid Records for target test regions (Section 1.5.3)
17. CA-Datacom/DB users (Section 1.6.3).
18. Copy your MTPFLIST source and object to MBC as MBCFLIST (Section 1.6.5)
20. Convert your CEMT from Batch BATCNTL file (Section 1.7.2). This step also loads your product password
and lets you set new installation options
21. Make the MBC files available to CICS for testing (Section 1.7.3) if you are NOT parallel testing
22. Remove MTPSTATR from PLTPI for migration testing (Section 1.7.6).
24. Review Operational Differences between MBC and CEMT from Batch (Section 1.7.9).
26. Status Tracking users see CEMT from Batch BATSTAT file conversion options (Section 1.9.1)
27. Rename your files for Cutover (Section 1.9.2)
28. After testing is complete, swap out your old CEMT from Batch files (Section 1.9.3)
29. Review Installation Options (Section 1.9.5)
30. Make the MBC Modules available for Batch Access (Section 1.9.6)
31. After testing is complete modify the PLT entries (Section 1.9.7)
32. Define Domain Records for target production regions (Section 1.9.8)

1.1.5 Upgrading from a Previous Release of MBC [Upgd]
The instructions in this section are for users that have MacKinney Batch to CICS (MBC) currently installed and are
upgrading to a new release of MBC.
If this is your correct installation path, print the following checklist along with the upgrade instructions specific to the
current release(s) of MBC you have installed.
1. Messages MBCB001, MBCB170, MBCE170, and MBCE175 have been changed in MBC 2.1 to allow the
addition of Job number in the messages. If screen scraping message be certain to allow for these changes.
2. After backing up the previous release loadlib, replace loadlib contents with the members from the new release
so new members are available in the STEPLIB of your MBCBATCH jobs and the RPL of your CICS regions.
3. If you have customized any MBC user exits (Section 4.3 and Section 6.4), continue reading. For exits other
than MBCBCRCX, review your modifications and either copy them into the current source and reassemble
(recommended for user exits) or copy the old version object into the new release loadlib after backing up the
member shipped with the new release. MBCBCRCX was changed in MBC 2.0 to support new Installation
Option ERRWARN, so review MBCBCRCX and make any necessary modifications to the new version of
MBCBCRCX.
4. If you have copied EXCI (DFH*) members into the MBC loadlib (Section 1.7.7) and are replacing the entire
MBC loadlib, be sure to re-copy EXCI members into the new loadlib.
5. Resource Item records have been separated from pre MBC 2.0 Resource Groups in support of the new Startup
Manager. Run batch conversion program MBCBCNVR if you have any pre-MBC 2.0 Resource Groups
(Section 4.2.4). Also, the input card formats for batch utility MBCBRGRP have changed (Section 3.8.8) and
new batch utility MBCBRITM has been added (Section 3.7.4). You will need to alter any JCL you are using
for MBCBRGRP.
6. Resource definitions are provided in distributed RDO members (Section 1.3). See the following pages for
MBC release specific upgrade information regarding RDO and optional additional changes for upgrading
from previous MBC releases. Refer to the release from which you are upgrading from.
7. Starting with MBC 2.0, usage for the BATSTAT file changed. In versions prior to MBC 2.0, the BATSTAT
file was written to by every job regardless of whether CICS was up or down, now it is written to only when
CICS is down. Remove MBCPPLT from PLTSD (Section 1.9.7). See note below if parallel testing.
8. If you use Status Tracking without Startup Manager, we recommend starting with empty BATSTAT, a new
BATCSTS files and running a COLD START. If you use Status Tracking with Startup Manager, we
recommend starting with an empty BATSTAT file and running sample job MBCJPRE (Section 7.3.2) to
preset BATCSTS file for initial use with Startup Manager.
NOTE: If you cannot start with an empty BATSTAT file (i.e. you require DSN values or previous status from
commands saved in the BATSTAT file), then you will need to run batch utility MBCBCNV2 (Section 4.2.5).
9. You should re-load all help screens regardless of the release you are coming from. JCL can be found in
member MBCJHELP (Section 1.2.1.1).
Parallel Testing MBC 2.1 with MBC 1.2 – 1.6 (WARNING!!!)

If you intend to parallel test with MBC 2.1 and MBC 1.6 (or below), here are a few considerations:
1. You control the verion to test by changing the active LOADLIB both for batch and CICS.
2. The BATCNTL file is backward compatilble, so this file can be shared for testing in both environments. Be
cautious about changing Installation Options and other resources (Groups, Domains, Applgrps) used in both
versions if sharing a common file.
3. If using Status Tracking: The usage of the BATSTAT file changed with MBC 2.0, so you should provide your
MBC 2.1 testing environment with new BATSTAT file(s). Be sure to use this new file when testing MBC 2.1
batch jobs as well as adding to CICS when testing MBC 2.1 startup.
4. Make sure your CICS RPL has the correct LOADLIB version (2.0 and up or 1.6 and below) to go along with the
proper BATSTAT file.

Upgrading to MBC 2.1 from MBC 1.2 – 1.5 (WARNING!!!)
The COMMAREA passed between MBCBATCH and the MBC CICS server has a new format beginning with MBC
1.6. It is recommended to convert batch and CICS regions at the same time. We have made every effort to maintain
compatibility with older releases, but new data is returned which requires format changes. Results from running
mixed releases is not guaranteed (i.e. MBC 2.1 in batch might not work with MBC 1.5 in CICS and MBC 1.5 in
batch might not work with MBC 2.1 in CICS).
Upgrading from MBC 2.0

TRANIDS CHANGE
No changes
PROGRAMS CHANGE
MBCBCSTS Added new batch utility program to print and delete BATCSTS records
MBCBSTAT Added new batch utility program to define, list and delete BATSTAT records
MBCBWTOX Added new WTO user exit program
MBCPCMAL Added new program to support splitting allocation command support
MBCPRLS Added new program to support Record Level Sharing (RLS) commands
MBCPPLQ Added new program to process Startup Commands during PLT
MBCMSCD Added new map to support Startup Command detail
MBCPSCD Added new program to support Startup Command detail
MBCMSCL Added new map to support Startup Command list
MBCPSCL Added new program to support Startup Command list
MBCPSCQ Added new program to build Startup Command queue
MBCPSCW Added new program to write Startup Command records to BATCSTS
FILES CHANGE
BATCNTL Added new APPLSTS=F and ERRDRLS options (Section 3.4). Make sure new options are set
correctly for each BATCNTL file.
BATCSTS File required if Status Tracking enabled (STATFLAG=’Y’) or if using Startup Commands (see
Section 8.1).

TRANIDS CHANGE
MBCH Added new tranid for Help screens; points to MBCPHLP
MBCI Added fast-path administrative of Resource Items; points to MBCPADM (Section 3.7)
MBCP Added new tranid to support STAR MBCP option; points to MBCPRIM (Section 5.2)
MBCU Added read-only administrative of non-system records; points to MBCPADM (Section 3.2)
MBC1 Added fast-path administrative of Status Tracking Maint; points to MBCPADM (Section 3.9)
PROGRAMS CHANGE
MBCBCNVR Added new batch program to convert old Resource Group members to Resource Item records
MBCPCMAR Added new program for allocate and unallocate commands
MBCPCRU Added new program for to update Resource Status records
MBCMGPD Added new map for Define Resource Group
MBCPGPD Added new program for Define Resource Group
MBCPGPW Added new program to write Resource Group records
MBCPHLP Added new program to support MBC Help screens
MBCPHLPU Added new program to support unloading MBC Help screens
MBCPITQ Added new program to build Resource Group Item queue
MBCMITS Added new map to support Resource Group Item selection
MBCPITS Added new program to support Resource Group Item selection
MBCPPLA Added new program to allocate Resources for PLT programs
MBCMRID Added new map to support Resource Item directory
MBCPRID Added new program to support Resource Item directory
MBCMRIE Added new map to support Resource Item update
MBCPRIE Added new program to support Resource Item update
MBCPRIM Added new program to support STAR MBCP
MBCPRIS Added new program to support Resource Item status lookup
MBCMRIX Added new map to support Resource Item cross reference with member groups
MBCPRIX Added new program to support Resource Item cross reference with member groups
MBCPRSTX Added new sample user exit to support optional BATSTAT record clean-up after MBCPRSET
MBCMSTD Added new map to support Resource Status detail
MBCPSTD Added new program to support Resource Status detail
MBCMSTM Added new map to support Status Tracking maintenance
MBCPSTM Added new program to support Status Tracking maintenance
FILES CHANGE
BATCNTL Added new options APPLSTS=F, CEDACMD, ERRDRLS, STRTUPMG and TRKNONFI
See Section 3.4. Make sure new options are set correctly for each BATCNTL file.
Section 8.1).

TRANIDS CHANGE
PROGRAMS CHANGE
MBCPCEDA Added new program to support CEDA and CDAL commands (Section 5.2)
FILES CHANGE
BATCNTL Changed default access to read-only in all regions in support of dynamic update (Section 1.2)
Added new options APPLSTS=F, CEDACMD, EMTMSGS, ERRDRLS, LOGXDD, STRTUPMG
and TRKNONFI (Section 3.4). Make sure new options are set correctly for each BATCNTL file.
Section 8.1).

TRANIDS CHANGE
MBCI Added fast-path administrative of Resource items; points to MBCPADM (Section 3.7)
PROGRAMS CHANGE
MBCPQRY Added new program to support QRYL and QRYS commands (Section 5.2)
FILES CHANGE
Added new options APPLSTS=F, CEDACMD, EMTMSGS, ERRDRLS, LOGXDD, STRTUPMG,
and TRKNONFI (Section 3.4). Make sure new options are set correctly for each BATCNTL file.
Section 8.1).

TRANIDS CHANGE
MBCB Added for read-only administrative access; points to MBCPADM (Section 3.1)
MBCD Changed administration transaction to point to MBCPADM instead of MBCPDMD
MBCG Changed administration transaction to point to MBCPADM instead of MBCPGRP
MBCL Changed administration transaction to point to MBCPADM instead of MBCPAGD
MBCO Changed administration transaction to point to MBCPADM instead of MBCPGRP
MBCS Changed administration transaction to point to MBCPADM instead of MBCPGRP
MBCZ Added operational transaction in support of TCP/IP version; points to MBCPTCI
PROGRAMS CHANGE
FILES CHANGE
BATCNTL Changed default access to read-only in all regions (Section 1.2) Added new options APPLSTS=F,
CEDACMD, DOMSEC, EMTMSGS, ERRDRLS, ERRSTS, LOGXDD, STRTUPMG and TRKNONFI
(Section 3.4). Make sure new options are set correctly for each BATCNTL file.
BATCSTS New file required if Status Tracking enabled (STATFLAG=’Y’) or if using Startup Commands.
A new password engine was implemented with MBC 1.3 which requires a new product password.
z/OS users must copy DFH* members from your.CICS???.SDFHEXCI to the your.MBC.loadlib or batch STEPLIB
concatenation or have available in LINKLIST. See Section 1.7.7.
Removed the text DOWN in messages MBCB006, MBCB007 and MBCB008. Modify any automated message
handlers accordingly.
TRANIDS CHANGE
MBCB Added for read-only administrative access; points to MBCPADM (Section 3.1)
MBCD Changed administration transaction to point to MBCPADM instead of MBCPDMD
MBCG Changed administration transaction to point to MBCPADM instead of MBCPGRP
MBCI Added fast-path administrative of Resource items; points to MBCPADM (Section 3.7)
MBCL Changed administration transaction to point to MBCPADM instead of MBCPAGD
MBCO Changed administration transaction to point to MBCPADM instead of MBCPGRP
MBCS Changed administration transaction to point to MBCPADM instead of MBCPGRP
MBCZ Added operational transaction in support of TCP/IP version; points to MBCPTCI
PROGRAMS CHANGE
MBCMAPL Added map to allow editing of Applid Table (Section 3.4.2)
MBCPAPL Added program to allow editing of Applid Table (Section 3.4.2)
MBCMDMD Added map to support Domain Applid records (Section 3.10)
MBCPDMD Added program to support Domain Applid records (Section 3.10)
MBCMDME Added map to support Domain Applid records (Section 3.10)
MBCPDME Added program to support Domain Applid records (Section 3.10)
MBCPTCI Added program in support of TCP/IP version
FILES CHANGE
Added new options APPLSTS=F, CEDACMD, DOMSEC, EMTMSGS, ERRDRLS, ERRSTS,
LOGXDD, STRTUPMG and TRKNONFI (Section 3.4). Make sure new options are set correctly for
each BATCNTL file.
Section 8.1).
1.1.6 Upgrading Current Release to a new PTF Level

If you are refreshing your release to a new PTF level (i.e. 2.0.5 – 2.0.25), download the new level from our website
(www.mackinney.com) and follow the instructions in the MBC_README.TXT found in the downloaded zip file.
Replacing your existing MBC loadlib with the new loadlib updates your PTF (maintenance) level.
If you have customized any of the MBC user exits (Section 4.3 and Section 6.4) or are using the File List processing
program MBCFLIST (APPENDIX D), continue reading. For exits other than MBCBCRCX, review your
modifications and either copy them into the current source and reassemble (recommended for user exits) or copy the
old version object into the new release loadlib after backing up the member shipped with the new release.
MBCBCRCX was changed in MBC 2.0 to support new Installation Option ERRWARN, so review MBCBCRCX
and make any necessary modifications to the new version of MBCBCRCX.
Program MBCPRLS was added with fix level 2.0.12. If you are upgrading from a release prior to 2.0.12 the program
MBCPRLS should be added to your RDO definitions.

1.2 MBC VSAM Files [ZNew] [ZCnv] [VNew] [VCnv]
BATCNTL: The BATCNTL file is a multi-purpose KSDS VSAM file containing the MBC installation options
(Section 3.4), product passwords (Section 3.3) , Applid Group records (Section 3.6), Resource Item records
(Section 3.7), Resource Group records (Section 3.8) and Domain Applid records (Section 3.10). The BATCNTL
file should be defined with read-only access in all of the CICS regions to allow sharing by many regions. When
administration access is requested within a region via transaction MBCA, the file attributes are dynamically
modified to allow update access. The attributes are modified back to read-only when the last administration
transaction for a region has ended (Section 3.1). Only one region at a time is allowed administrative access.
BATSTAT: The BATSTAT file is also a multi-purpose KSDS VSAM file containing optional Status Tracking
records (Section 7.1) and optional Applid Status records (Section 2.1.3). Status Tracking records are only written
to the BATSTAT file when CICS is down. You can have multiple BATSTAT files and each file can be shared by
multiple CICS regions. The BATSTAT file can be open for update by only one MBCBATCH job at a time. If an
open error occurs, MBCBATCH waits 5 seconds before retrying the open. Option STATRTRY (Section 3.4)
determines the number of intervals to wait before treating an open failure as a command failure. Set STATRTRY
to fit your environment. The default STATRTRY is 2, which attempts to open the BATSTAT file for 10 seconds
before failing. Please adjust your scheduling to allow for optimal throughput. It is suggested to pair your
BATSTAT files with your BATCNTL files.
BATCSTS: The BATCSTS file is a KSDS VSAM file containing optional Startup Command and Status Tracking
records (Section 7.1) created from within CICS. You must have a unique BATCSTS file for each target CICS
region. BATCSTS should be updateable within the CICS region and cannot be shared.
1.2.1 Defining and Loading the BATCNTL File [ZNew] [ZCnv] [VNew] [VCnv]
The JCL and IDCAMS control statements required to define the BATCNTL KSDS file is found in member
MBCJFILB. In addition to defining the file, MBCJFILB loads the online Help screens. Make the required local
changes in the JCL and run the job.
WARNING! SHAREOPTIONS (2, 3) must be specified for the BATCNTL file. If you use Domain Applid
records, one BATCNTL file must be shared by all of the APPLIDs defined in the domain.
1.2.1.1 Loading Help Screens in the BATCNTL File [ZNew] [ZCnv] [VNew] [VCnv]
The Help screens are loaded when you use source member MBCJFILB to create the BATCNTL file. If the
BATCNTL file has already been defined, use member MBCJHELP to load Help screens.
1.2.2 Defining and Loading the BATSTAT File [ZNew] [ZCnv] [VNew] [VCnv]
Skip this step if you are not using Status Tracking (Section 7) or Applid Status (Section 2.1.3). The JCL and
IDCAMS control statements required to define and initially load the BATSTAT KSDS file is in member
MBCJFILS. Make the required local changes in the JCL and run the job.
WARNING! SHAREOPTIONS (2, 3) must be specified for the BATSTAT file. Also, failure to repro the blank
record results in errors opening the file.
NOTE: If you use are upgrading to MacKinney Batch to CICS release 2.1 from release 1.6 or below, it is
recommended to start with an empty BATSTAT file and run a COLD START.
1.2.3 Defining and Loading the BATCSTS File [ZNew] [ZCnv] [VNew] [VCnv]
Skip this step if you are not using Startup Commands (Section 8.1) or Status Tracking (Section 7). The JCL and IDCAMS
control statements required to define and initially load the BATCSTS KSDS file is in member MBCJFILC. Make the
required local changes in the JCL and run the job. Each target CICS region requires a unique BATCSTS file.
WARNING! Failure to repro the blank record results in errors opening the file.

1.3 Defining MBC CICS Resource Definition Entries [ZNew] [ZCnv] [VNew] [VCnv]
Sample CICS Resource Definition Online (RDO) entries are available in following members:
MBCJRDO – sample program and transaction definitions minus administration

MBCJRDOA – sample program and transaction definitions including administration
MBCJRDOC – sample connection and session definitions for EXCI
MBCJRDOF – sample file definitions for BATCNTL and BATSTAT files
MBCJRDOS – sample file definition for BATCSTS file
The z/OS members contain sample JCL to execute CICS utility DFHCSDUP. Change to your CICS loadlib and CSD
before submitting for execution. If multiple CICS systems are to communicate with batch, the table entries listed below
must be made in each CICS system. RDO definitions must be manually installed or you must add the GROUP to your
startup LIST before using.
For VSE, see member MBCJRDO.JCL for sample JCL to execute CICS utility DFHCSDUP. Change to your CICS
loadlib and CSD before submitting for execution. If multiple CICS systems are to communicate with batch, the table
entries listed below must be made in each CICS system. RDO definitions must be manually installed or you must add
the GROUP to your startup LIST before using.
1.3.1 Defining MBC Programs and Transactions [ZNew] [ZCnv] [VNew] [VCnv]
Member MBCJRDO contains Program and Transaction entries required for batch communication. Member
MBCJRDOA contains all of the entries in MBCJRDO, plus the Program and Transaction entries required for
administration. If you want to allow for administration in a region use MBCJRDOA, otherwise use MBCJRDO.
All CICS regions targeted by batch jobs must have either MBCJRDO or MBCJRDOA installed.
Review Section 2.3.2 and the supplied RDO entries for security information on specific transactions. Review Section
2.1.1 for timeout considerations in your environment that might alter your setting for the DTIMOUT parameter in the
MBCX transaction definition. Also refer to the CICS Resource Definition Guide.
1.3.2 Defining SHUT Terminal Definition [ZNew] [ZCnv] [VNew] [VCnv]

This step can be skipped if you do not you plan to use the SHUT command or if you specify EXTSEC=Y. If you
specify EXTSEC=N and plan to use the SHUT command, then MBC needs a terminal on which to initiate a CICS
shutdown (SHUTTERM) from batch client program MBCBATCH. You can either define a new Terminal
definition or use an existing Terminal for the SHUTTERM Installation Option value (Section 3.4). The Terminal
used must be defined with the ATI=YES and the USERID associated with the terminal must be authorized for
Tranid MBCQ (SHUT transaction).
1.3.3 Defining SIT Entries [ZNew] [ZCnv] [VNew] [VCnv]

Be sure each of your CICS regions you intend to target from the MBCBATCH batch client has a unique Applid name
(no wildcards). The Applid is defined using the SIT APPLID parameter (See the CICS Systems Programmer’s
Reference Manual for details) or by using an override parameter on the EXEC JCL card as follows:
// EXEC PGM=DFHSIP,SIZE=2000K,APPLID=TESTCICS,PCT=S2
EXCI users: Must set IRCSTRT=YES in the SIT to enable IRC communications at startup in support of EXCI. Also
review the ISC parameter to see if you need to specify ISC=YES to allow IRC communications. For those not familiar
with IRC and EXCI (z/OS), please review the CICS Resource Definition Guide, CICS Intercommunication Guide and
CICS External Interfaces Guide (z/OS) in addition to the RDO sample definitions provided.
TCP/IP users: Please check the requirements of your individual stack to see if there are any special SIT requirements.
If you are already running a TCP/IP listener, you will not likely need to make any additional SIT changes for MBC.

1.3.4 Defining MBC CICS File Definitions [ZNew] [ZCnv] [VNew] [VCnv]
MBC supplies sample CICS file definitions in source members MBCJRDOF (BATCNTL and BATSTAT) and MBCJRDOS
(BATCSTS). It you do not use Status Tracking or Applid Status, then you do not need to define the BATSTAT or BATCSTS
files.
Read the appropriate section below depending on your installation path for information on installing your MBC files.
Converting from CEMT from Batch users
If you intend on parallel testing with CEMT from Batch, then do not update the file definitions for BATCNTL and BATSTAT
(MBCJRDOF) nor add file BATCSTS (MBCJRDOS) until your testing is complete. If you are not parallel testing, then follow
the instructions for “All Other users”.
All Other users
For other users, we recommend defining a BATCNTL file (MBCJRDOF) with read access in each of your CICS regions
targeted by MBCBATCH batch client commands.
If you intend to use Status Tracking or Applid Status, it is recommended pairing a BATSTAT file (MBCJRDOF) with a
BATCNTL file. The BATSTAT file is also limited to read access which allows you to share one BATSTAT and a paired
BATCNTL file amongst several regions. With Status Tracking active, you must also define a unique BATCSTS file
(MBCJRDOS) in each CICS region.

1.4 Preparing for EXCI Use [ZNew] [ZCnv]
For those not familiar with EXCI, please review the CICS Intercommunication Guide, CICS External Interfaces Guide
and the CICS Resource Definition Guide. IBM requires the CICS SIT to include IRCSTRT=YES for each region you
intend to target MBC commands.
1.4.1 Verifying EXCI Options (DFHXCOPT) [ZNew] [ZCnv]

The DFHXCOPT options table allows you to specify a number of parameters that are required by EXCI. The table is
linked using the name DFHXCOPE (since CTS 3.2) or DFHXCOPT (prior to CTS 3.2). Refer to IBM documentation
on customizing parameters of DFHXCOPT and see the sample source member DFHXCOPT member in SDFHSAMP..
We recommend you assemble and link the new DFHXCOPT (DFHXCOPE) into the MBC loadlib so the module is
available at MBCBATCH execution time.
If you already running a modified version of DFHXCOPT, the modified DFHXCOPT module along with its alias
DFHXCOPE must be available to the MBC Batch jobs. See Section 1.7.7.
Two specific DFHXCOPT values to verify for MBC use are the CICSSVC and XCFGROUP.
CICSSVC
The default CICSSVC value in DFHXCOPT is 0, and this value works fine in environments where batch and CICS are
running on the same image. However, if you intend to run MBCBATCH jobs in an image that does not contain a
CICS, you need to specify a non-zero value for the CICSSVC parameter to let EXCI know the CICS SVC.
XCFGROUP
The default XCFGROUP value is DFHIR000. EXCI supports cross-system coupling facility (XCF) groups such as
DFHDEV or DFHTEST to override the default group. If you have specified an XCFGROUP value other than
DFHIR000 in your SIT, then the DFHXCOPT XCFGROUP value available to the MBCBATCH job must match
the SIT XCFGROUP value for any targeted region (CICS header card). Otherwise the connect will fail with the
following:
MBCB021-CONNECT FAILED: APPL(yourCICS) RESP(00655360) REASON(00078049-00000000)
1.4.2 Defining Connection and Sessions Entries [ZNew] [ZCnv]

Member MBCJRDOC contains Connection and Sessions entries for all target regions which communicate with batch.
Run this member to define the required Connection and Sessions entries for EXCI use. See Section 2.1.6 for special
instructions. RDO definitions must be manually installed or you must add the GROUP to your startup LIST before
using.

1.5 Preparing for TCP/IP Use [VNew] [VCnv]
TCP/IP support was added to MBC primarily to bypass the “same LPAR restriction” imposed by EXCI for VSE users,
however, support is optionally available for z/OS users. z/OS users may contact MacKinney Systems for details on
using TCP/IP instead of EXCI. For those not familiar with TCP/IP, please review the following: CICS
Intercommunication Guide; CICS Resource Definition Guide; TCP/IP for VSE/ESA V1R5.0 IBM Program Setup and
Supplementary Information (VSE before z/VSE 5.2); z/VSE TCP/IP Support (z/VSE 5.2 or later).
1.5.1 IP Stack Considerations [VNew] [VCnv]

Some rules to avoid connection and timeout errors with your stack:
• Your TCP/IP phase library must be available to both your CICS regions and your MBCBATCH jobs
• Verify your stack is running at a priority high enough to avoid contention for resources
• If you are running multiple stacks, the JCL must point to the correct stack in both your CICS regions and your
MBCBATCH jobs (z/VSE OPTION SYSPARM=’nn’ where ‘nn’ is the Stack ID)
• z/VSE 5.2 and later must match the Stack ID value for TCPADDR=SOCKETnn parm in CICS Listener Configuration file.
The TCP/IP version of MBC supports stacks from BSI and CSI on z/VSE as well as the Linux Fast Path (LFP). Refer
to documentation provided by your TCP/IP provider for assistance on configuring the stack. Documentation for LFP is
found in z/VSE TCP/IP Support. See below for minimum release requirements for BSI and CSI stacks.
Running BSI TCP/IP Tools for VSE Stack
Users running BSI TCP/IP Tools for VSE stack must run Build 247 or higher. See the download page at http://www.bsiopti.com.
Running CSI TCP/IP for VSE Stack
Users running CSI TCP/IP for VSE must be at the following release levels or later, otherwise Socket timeouts occur:
1.5F with fixes ZP15F286, ZP15F405, and ZP15F538 on and IPNRBSDC must be 7/10/2009 or later (BSD100I)
1.5G with fix ZP15G070 applied
See http://www.tcpip4vse.com/csi-products/TCPIP/zaps/zaps15f.htm.
If running a customized $SOCKOPT.PHASE, verify BSDCFG2=$OPTGTSP is specified (GiveSocket/TakeSocket run in
same partition as requester), otherwise Socket timeouts occur.
1.5.2 Verifying Standard Listener Support [VNew] [VCnv]

The MBCBATCH client uses the CICS Standard Listener to start the MBC server program for the IP version of MBC.
The Standard Listener is defined with the Listener Configuration file and modified with tranid EZAC. If the Listener
has not been previously defined, see MBCJEZA.JCL or MBCJEZ52.JCL (z/VSE 5.2 or later) for sample JCL using the
EZACICD macro to create the file. To ensure the Listener is available, we recommend putting entries EZASTRUE and
EZACIC20 in the PLTPI and PLTSD, and verifying IMMED=YES is specified in the Listener Configuration (EZAC).
The Listener Configuration is also where the PORT value and Address Family (z/VSE 5.2 and later) are specified for
each CICS Applid (EZAC). For additional information on configuring the Listener refer to TCP/IP for VSE/ESA
V1R5.0 IBM Program Setup and Supplementary Information (VSE prior to z/VSE 5.2) or z/VSE TCP/IP Support
(z/VSE 5.2 or later).
The Userid associated with the CICS Standard Listener should have surrogate authorization to START Tranid MBCZ
with the batch client userid (Section 2.3.2).
1.5.3 Defining Domain Applid Records [VNew] [VCnv]

Domain records must be added for each target Applid. The Domain records define the Port, Address Family (IPV4 or
IPV6) of the stack, IP address of the CICS Listener and optional Execution Userid for each Applid.
[VNew] Add Domain records for each target Applid online (Section 3.10) or via batch (Section 3.10.3).
[VCnv] Add records for each target Applid via batch (Section 3.10.3). If online access to MBC administration is
available, you can also copy Applid records to Domain Applid records via MBCBDOM (Section 3.10.3).

1.6 Customization Steps [ZNew] [ZCnv] [VNew] [VCnv]
1.6.1 GRS Considerations [ZNew] [ZCnv]

z/OS users who run SDSI or Multi-Image Manager (MIM) for global resource serialization should add the MBC batch
client QNAME and/or RNAME values to the tables for those products. The QNAME should be ‘MBCBATCH’.
RNAME is an eight character variable which contains the name of the target CICS Applid. Allow for multiple RNAME
values – one for each Applid used by MBCBATCH.
Users of IBM’s Global Resource Serialization (GRS) do not require any special considerations.
1.6.2 Running MBC across Multiple Systems (Images) [ZNew] [VNew]

If you need to run the MBCBATCH batch client across multiple systems (including LPARs), set option ENQXS to ‘Y’.
MBCBATCH then issues an Enqueue using the ‘SYSTEMS’ (z/OS) or LOCK with SCOPE=EXT (VSE).
EXCI requires XCF/MRO to communicate across images. XCF/MRO requires appropriate cross-system coupling
facility enabling MRO to function between images in a Sysplex environment. XCF/MRO is not a requirement for
running the TCP/IP version (default version for VSE).
1.6.3 CA-Datacom/DB Users [ZNew] [ZCnv] [VNew] [VCnv]

Users wishing to use MBC to Open and Close CA-Datacom/DB databases and receive return code information back can
use the DLBC command (Section 5.1 DBLC) for this function. The DLBC command requires CA-Datacom/DB CICS
Service Facility 2.4 or higher.
1.6.4 VSE DL/I Users [VNew] [VCnv]

Users wishing to use MBC to open and close VSE DL/I databases can use the DLOC command (Section 5.1 DLOC) for
this function. Before using the command you must first customize program MBCPDLOC.
[VNew] All databases to open or close with a DLOC command must be defined to MBC by adding their names to a
table at the end of the MBCPDLOC program. Locate label ‘DBDTABLE’ in the provided program source just a few
lines before the end of the program. Each entry in the DBDTABLE must be 8 characters long. If the database name is
less than 8 characters, pad on the right with '@' up to the 8th character, which must be 'D'. If database names are 8
characters, no pad characters are needed. Field ‘ENDTABLE’ (CL8'FFFFFFFF') must immediately follow the last
database name in the DBDTABLE. MBCPDLOC uses a 'CALL' interface to DL/I (CALLDLI ASMTDLI,...) rather
than an 'EXEC' interface.
[VNew] The field ‘PASSWORD’ specifies the schedule password. The default is DLZPASS1. If your password is
different, please see the comments in the program and modify accordingly.
[VCnv] User converting from CEMT from Batch should locate their MTPDLOC source member and copy the changes
from MTPDLOC to MBCPDLOC as described in the [VNew] sections above
[VNew] [VCnv] After making modifications to MBCPDLOC, assemble using command-level assembly JCL. See
source member MBCJASMC.JCL for sample JCL.
1.6.5 Converting CEMT from Batch MTPFLIST [ZCnv] [VCnv]

Copy your old MTPFLIST source (if available) and object to your MBC source library and loadlib and rename to
MBCFLIST. Verify the end of list (DC CL8’@@@@@@@@’) entry is present for each list. Assemble and link MBCFLIST
into your MBC loadlib.

1.7 Pre-Testing [ZNew] [ZCnv] [VNew] [VCnv]
1.7.1 Making Programs Available for CICS Access [ZNew] [ZCnv] [VNew] [VCnv]
z/OS users, include the MacKinney Batch to CICS loadlib in the DFHRPL DD concatenation of your CICS startup JCL.
VSE users, place the sub-library containing MacKinney Batch to CICS phases in the search chain of your CICS startup
JCL. The CICS program names in the MBC loadlib all begin with MBCP* and MBCM*.
1.7.2 Converting CEMT from Batch BATCNTL File [ZCnv] [VCnv]

For users converting from CEMT from Batch, the BATCNTL file has changed from an RRDS to a KSDS and the
function of the file has changed, so a conversion is required. We supply a two-step conversion job, MBCJCNV
(sample JCL), to assist in the conversion.
STEP1executes MBCBCNV to convert your old installation options and any Applids from your old BATCNTL
file to the new BATCNTL file.
STEP2 executes MBCBCUTL to allow you to customize values for new installation options (see Section 3.4
for information on the new options) and sets your product password. Verify and update your old installation
options before running the conversion utility MBCBCNV.
See Section 4.2.2 for additional information and sample output of the MBCBCNV step and Section 4.2.1 for
additional information and sample output of the MBCBCUTL step.
1.7.3 Making Files Available for CICS Access [ZNew] [ZCnv] [VNew] [VCnv]
Converting from CEMT from Batch users: If you intend on parallel testing with CEMT from Batch, then do not update the
file definitions for BATCNTL and BATSTAT (MBCJRDOF) and make new MBC files available for CICS access until your
testing is complete. If you are not parallel testing, then follow the instructions for “Other users”.
Other users: For other users, the MacKinney Batch to CICS files, BATCNTL, BATSTAT (optional) and BATCSTS
(optional) are made available to each CICS system in one of two ways:
1. The files can be dynamically allocated to CICS by including a non-blank DSNAME parameter in your CSD
file definition. For example DSNAME=MBC.BATCNTL for file BATCNTL. Using this method, the files
are allocated to CICS the first time CICS opens them. This is the recommended method.
2. If not using dynamic file allocation, add a DD or DLBL statement to the CICS start-up JCL as in the
examples below, or for VSE – add to your STANDARD LABELS. This method is not recommended.
z/OS
//BATCNTL DD DSN=MBC.BATCNTL,DISP=SHR
//BATSTAT DD DSN=MBC.BATSTAT,DISP=SHR
//BATCSTS DD DSN=MBC.BATCSTS,DISP=SHR
The above changes must be made in each CICS system where MacKinney Batch to CICS is to run.
VSE
// DLBL BATCNTL,'MBC.BATCNTL',,VSAM,CAT=yourcat
// DLBL BATSTAT,'MBC.BATSTAT',,VSAM,CAT=yourcat
// DLBL BATCSTS,'MBC.BATCSTS',,VSAM,CAT=yourcat
The above DLBLs must be added to each CICS system where MacKinney Batch to CICS is to run
or the files must be added to your STANDARD LABELS.

1.7.4 Updating the Product Password [ZNew] [VNew]
Add the required valid Product Password(s) provided by your vendor. This can be done online from the Administration
Menu (Section 3.3 Password Maintenance) or from batch using the PASS function of the MBCBCUTL utility (Section
3.3.1).
1.7.5 Customizing Installation Options [ZNew] [VNew]

MacKinney Batch to CICS offers several options to tailor for your environment. This can be done online from the
Administration Menu (Section 3.4 Installation Options) or from batch using the MBCBCUTL utility (Section 3.4.1).
1.7.6 Removing MTPSTATR from PLTPI [ZCnv] [VCnv]

Users converting from CEMT from Batch must remove the MTPSTATR entry from your testing region(s) PLTPI
member, even if you are parallel testing. This stops Status Tracking for CEMT from Batch from being started.
1.7.7 Copying EXCI modules from SDFHEXCI [ZNew] [ZCnv]

If running the EXCI version of MBC, modules in your CICS???.SDFHEXCI library (i.e. CICSTS53.CICS.SDFHEXCI)
must be available for batch execution. This can be accomplished by copying modules from the SDFHEXCI library to the
MBC loadlib, inserting the SDFHEXCI library in the STEPLIB concatenation of your MBCBATCH JCL or proc (Section
1.8.1) or if available in LINKLIST.
NOTE: If you are running a modified version of DFHXCOPT, be sure to copy the modified version (and alias
DFHXCOPE) and not the default version shipped with the SDFHEXCI library. Contact your CICS installer if you are not
certain of the name for the SDFHEXCI library. No special action is required to make these modules be available in CICS.
1.7.8 Reviewing Security Considerations [ZNew] [ZCnv] [VNew] [VCnv]

Carefully review Section 2.3 before testing. This Section describes security considerations including running with an
external security manager plus securing transactions and files.
1.7.9 Operational Differences Compared to CEMT from Batch [ZCnv] [VCnv]

Carefully review Section 2.2 before testing. This Section describes the operational differences between MBC and
CEMT from Batch.

1.8 Testing [ZNew] [ZCnv] [VNew] [VCnv]
1.8.1 Sample JCL for Executing MBCBATCH [ZNew] [ZCnv] [VNew] [VCnv]
Following is sample JCL for executing the batch client program, MBCBATCH. This JCL is included in source member
MBCJBAT found in your installation files. MBCBATCH can be added to your jobs to execute as a step before and/or
after existing job steps. If you prefer not to use a STEPLIB, then make all programs beginning with MBCB*, MBCF*,
MBCR* from the MBC loadlib available in the LINKLIST or equivalent. We recommend using PROCs if at all
possible. NOTE: DFH* members (z/OS only) from the SDFHEXCI loadlib must also be available and can be copied
from SDFHEXCI to the MBC loadlib unless already available in the LINKLIST or equivalent.
The BATCNTL DD or DLBL is always required. The BATSTAT DD or DLBL is only required if you are running
Status Tracking.
z/OS
//JOBNAME JOB (ACCT),'NAME',NOTIFY=tsoid,MSGCLASS=X,CLASS=A
//STEP01 EXEC PGM=MBCBATCH,REGION=4M ← (see NOTE1)
//STEPLIB DD DSN=your.MBC.loadlib,DISP=SHR ← change
// DD DSN=your.CICS.SDFHEXCI,DISP=SHR ← change
//SYSLST DD SYSOUT=*
//SYSLSTX DD SYSOUT=* ← optional (see NOTE2)
//BATSTAT DD DSN=MBC.BATSTAT,DISP=SHR ← optional status tracking
//SYSABEND DD SYSOUT=*
//SYSIPT DD *
CICS DBDCCICS ← sample target
CLOS FILE01 ← sample command
/*
//STEP02 EXEC PGM=YOURPROG
/*
//STEP03 EXEC PGM=MBCBATCH,REGION=4M ← (see NOTE1)
// DD DSN=your.CICS.SDFHEXCI,DISP=SHR ← change
//SYSLSTX DD SYSOUT=* ← optional (see NOTE2)
//BATSTAT DD DSN=MBC.BATSTAT,DISP=SHR ← optional status tracking
//SYSABEND DD SYSOUT=*
//SYSIPT DD *
OPEN FILE01 ← sample command
/*
NOTE1: If you get buffer expansion errors, increase the REGION= size on the MBCBATCH step(s).
NOTE2: SYSLSTX is optional to display extended data returned by certain commands. See Section 2.1.5 for additional
information on its usage.

VSE
// JOB MBCBATCH
* The following DLBLs are necessary only if not in Standard Labels
// DLBL BATCNTL,'MBC.BATCNTL',,VSAM,CAT=xxxxxx
// DLBL BATSTAT,'MBC.BATSTAT',,VSAM,CAT=xxxxxx ← optional status tracking
// ASSGN SYS025,cuu ← optional for LOGXDD=Y (NOTE1)
// OPTION SYSPARM=’00’ ← match Stack ID (NOTE2)
// LIBDEF PHASE,SEARCH=VENDOR.MBC,TEMP
// EXEC MBCBATCH,SIZE=512K ← (NOTE3)
/*
// EXEC YOURPROG
/*
* The following DLBLs are necessary only if not in Standard Labels
// DLBL BATCNTL,'MBC.BATCNTL',,VSAM,CAT=xxxxxx
// DLBL BATSTAT,'MBC.BATSTAT',,VSAM,CAT=xxxxxx ← optional status tracking
// OPTION SYSPARM=’0’ ← match stack id (see NOTE1)
// EXEC MBCBATCH,SIZE=512K ← (NOTE3)
/*
/&
NOTE1: If you code LOGXDD=Y and want to separate the extended data returned by certain commands, add the
optional LST and ASSGN statements along with the CUU of the alternate printer. See Section 2.1.5 for additional
information on its usage including how to change SYS025 to a new value if required.
NOTE2: If you are running with a Stack ID different than the default (‘00’), then verify the SYSPARM value identifies
the correct ID (review your TCPSTART JCL). Failure to specify the correct ID results in SOCKET errors when
attempting to connect.
NOTE3: If you get buffer expansion errors, increase the SIZE= size on the MBCBATCH step(s). Also, VSE users
running the EXCI version need to add the OS390 parm on the EXEC MBCBATCH card(s).
(i.e. // EXEC MBCBATCH,SIZE=512K,OS390).

1.9 Preparing for Production [ZNew] [ZCnv] [VNew] [VCnv]
1.9.1 Converting CEMT from Batch BATSTAT File [ZCnv] [VCnv]

Skip this step if you were not using File Status Tracking with CEMT from Batch. Otherwise, note the BATSTAT
file length and format has changed. We recommend starting with an empty BATSTAT file and run a COLD
START. However, if this is not possible, then we provide a conversion utility (MBCBCNVS) to use if you were
running with STATFLAG set to ‘1’. If you were running with STATFLAG set to ‘Y’, then you must start with an
empty BATSTAT file. MBCBCNVS (sample JCL is in member MBCJCNVS) converts your old BATSTAT
(STATFLAG=1) entries. For testing purposes, simply define a new BATSTAT file (run MBCJFILS JCL). New
entries are made to the BATSTAT file as you run MBCBATCH jobs. See Section 4.2.3 for additional information
and sample output of the MBCBCNV step
1.9.2 Renaming Files for Cutover [ZCnv] [VCnv]

To help avoid making JCL changes to your production JCL, we suggest renaming the DSNAME in your
production JCL (old BATCNTL file) to OLD.BATCNTL.DSN and then renaming your new BATCNTL file to the
DSNAME in your production JCL. The same process is required if you are using the BATSTAT file. If you are
using a PROC or STANDARD LABELS, or prefer to change your JCL, then make updates in the appropriate
locations before continuing testing.
1.9.3 Swapping out Files in CICS [ZCnv] [VCnv]

Before you cutover to production, remove old CEMT from Batch BATCNTL and old BATSTAT file definitions from your
CICS regions and replace them with new MacKinney Batch to CICS BATCNTL and new BATSTAT file definitions using
MBCJRDOF. If you do not intend on bouncing your CICS regions, then use the CEMT DISCARD FILE command to remove
the old definitions from your regions before defining the new definitions.
1.9.4 Sharing BATCNTL and BATSTAT Files [ZNew] [VNew]

You can have multiple BATCNTL and BATSTAT (optional) files and each file can be shared by multiple CICS regions. It is
our recommendation to have at least two BATCNTL and BATSTAT files, one for your production regions and one for your
test regions. If you do not use Applid Groups, Resource Items, Resource Groups or Status Tracking, then you can get by
without defining the BATCNTL file in your CICS regions. Otherwise the BATCNTL file must be available in your CICS
regions. The BATSTAT file is only defined in CICS regions when Status Tracking is enabled or if APPLSTS is set to ‘Y’ or
‘F’. Use MBCJRDOF for these definitions. The BATCSTS file cannot be shared.
1.9.5 Reviewing Installation Options [ZCnv] [VCnv]

For users converting from CEMT from Batch, your old Installation Options were copied over when you ran
MBCJCNV (Section 1.7.2). You should now have online access to the Installation Options. Select Installation
Options from the Administration Menu (Section 3.4 Installation Options), review all of the options carefully and
change as needed. Verify none of the options are blank. Press enter to update the options.
WARNING! If you modify EXTSEC=Y, review Section 2.3.2 at this time.

1.9.6 Making MBC Modules available for Batch Access [ZCnv] [VCnv]
[ZCnv] z/OS: Program MTPBATCH was replaced by MBCBATCH, but an alias was created to allow you to continue
executing MTPBATCH. If you are using a STEPLIB, be sure to remove all MTP* programs from the STEPLIB
dataset and replace them with the members from the new MBC loadlib. Also, be certain all DFH* members from the
SDFHEXCI Library are copied to this STEPLIB or available in the LINKLIST or equivalent.
[VCnv] VSE: Verify all MTP* programs in the SEARCH chain are removed and replaced with MBC* members from
the new MBC loadlib.
1.9.7 Defining PLT Entries [ZNew] [ZCnv] [VNew] [VCnv]

STARTUP PLT
There are three optional startup PLT entry programs that can be added to your PLTPI member, MBCPPLA, MBCPPLT
and MBCPPLQ. If using TCP/IP version of MBC, you must add EZACIC20 and EZASTRUE to PLTPI.
MBCPPLA can be added if you need to allocate Resource Items required for other PLT programs. While MBCPRSET
normally handles resource allocations it does not run until after PLT processing is finished. MBCPPLA reads special
Resource Group PLT.applid and all Resource Items defined in this group are allocated while this program is executing.
You should place this program before any other PLT programs requiring the defined Resource Items. See Section 7.2.4.
MBCPPLT is used to launch program MBCPRSET to reset Status Tracking resources to the last known status (i.e.
CLO/DIS, OPE/ENA). See Section 7.1. MBCPPLT is only executed if the if the Status Tracking feature is enabled
(STATFLAG=Y). If you already have a start-up PLT, add MBCPPLT after DFHDELIM in the PLTPI.
MBCPPLQ is used to process any Startup Commands saved in the region BATCSTS file. See Section 8.1 for more
information on how might make use of Startup Commands.
DFHPLT TYPE=INITIAL,SUFFIX=PI ← defines startup PLT

DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM ← CICS/ESA only
DFHPLT TYPE=ENTRY,PROGRAM=MBCPPLA ← Allocate resources for PLT programs
DFHPLT TYPE=ENTRY,PROGRAM=MBCPPLT ← Enable Status Tracking
DFHPLT TYPE=ENTRY,PROGRAM=MBCPPLQ ← Process Startup Commands
DFHPLT TYPE=ENTRY,PROGRAM=EZASTRUE ← Only for TCP/IP Use
DFHPLT TYPE=ENTRY,PROGRAM=EZACIC20 ← Only for TCP/IP Use
DFHPLT TYPE=FINAL
[ZCnv] [VCnv] Remove any MTP* (i.e. MTPPPLT, MTPSTATR, MTPONLIN) entries from the startup PLT.
SHUTDOWN PLT
Only if using TCP/IP version of MBC do you need any entries in PLTSD, EZASTRUE and EZACIC20. Prior to MBC
2.0, MBCPPLT could be added to PLTSD to dynamically add a SAPL DN record (Section 2.1.3) to BATSTAT file.
This method was unreliable, since MBCPPLT was bypassed if CICS was shut down with the IMMEDIATE option or
skipped due to errors. With MBC 2.0 and up, this method for adding the SAPL DN record is no longer supported.
If the SAPL DN record to needed to denote CICS is down, we recommend adding a new MBCBATCH STEP in your
CICS JCL after your CICS STEP to perform the SAPL DN add function.
DFHPLT TYPE=INITIAL,SUFFIX=SD ← defines shutdown PLT

DFHPLT TYPE=ENTRY,PROGRAM=EZASTRUE ← Only for TCP/IP Use
DFHPLT TYPE=ENTRY,PROGRAM=EZACIC20 ← Only for TCP/IP Use
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM ← CICS/ESA only
DFHPLT TYPE=FINAL
[ZCnv] [VCnv] Be sure to remove any MTP* (MTPPPLT, MTPONLIN) entries as well as MBCPPLT from the
shutdown PLT.

1.9.8 Defining Domain Applid Records [VNew] [VCnv]
If you are running the TCP/IP version of MBC, Domain records must be added for each target Applid. The Domain
records define the Port, Address Family (IPV4 or IPV6) of the stack, IP address of the CICS Listener and optional
Execution Userid for each Applid.
[VNew] Add Domain records for each target Applid online (Section 3.10) or via batch (Section 3.10.3).
[VCnv] Add records for each target Applid via batch (Section 3.10.3). If online access to MBC administration is
available, you can also copy Applid records to Domain Applid records via MBCBDOM (Section 3.10.3).
1.9.9 Security Differences between Test and Production [ZNew] [ZCnv] [VNew]
[VCnv]
You should carefully review your Security definitions for any possible discrepancies between your Test and Production
environments. For example, end users might submit jobs in Test regions for test purposes, but after cutover to
production, a scheduler is used to submit jobs. You should verify the authority required or permitted to your scheduler.
Or you might have a user defined with SUPERUSER authority submitting jobs for test and an operator submitting jobs
for production.
WARNING! Differences in your security settings for your Test and Production regions might cause error messages and
job failures in Production after testing successfully in your Test regions.

Section II
Special Considerations
2.1 General Considerations [ZNew] [ZCnv] [VNew] [VCnv]
2.1.1 MBC Timeout Considerations [ZNew] [ZCnv] [VNew] [VCnv]

The default timeout for the MBC CICS server is two minutes. This value can be adjusted by changing the
DTIMOUT parameter on the Transaction definition for MBCX (see member MBCJRDO). The DTIMOUT parm
allows you to specify a value up to 68 minutes in the format MMSS (minutes and seconds). Be sure to also specify
SPURGE(YES). See the Resource Definition Guide for additional information on these parameters. Resource
changes must be installed before they take effect.
An example scenario where timeout comes into play would be if the MBCX transaction attempts to alter (open,
close, etc.) a resource and the resource is locked by a long running task. After the DTIMOUT time has passed, the
MBCX server transaction is ended with an AEXY ABEND. The error is treated as a command failure and the
action taken by the batch client (MBCBATCH) is determined by the FAILACT option (Section 3.4).
NOTE if running TCP/IP version: TCP/IP has its own timeout variables that can override the DTIMOUT value.
2.1.2 Consideration if Autoinstalling programs [ZNew] [ZCnv] [VNew] [VCnv]

MBC provides an installation option, LOADPGM, which allows you to control whether or not a program is pre-loaded to
prevent a PGMIDERR when you issue a NEWC/PHAS or CEMT SET PROG command for a specific program (option
ignored for generic NEWC|PHAS requests). If autoinstall is active (PROGAUTOINST=AUTOACTIVE) and
LOADPGM=Y, an EXEC CICS LOAD is executed before the command to force an autoinstall of the program definition.
Without the LOAD, the command would possibly fail with a PGMIDERR if the definition for the target program has not
been installed due to previous activity (LOAD, XCTL, LINK, etc.).
WARNING! Care must be taken if using these commands with LOADPGM=Y, since a mistyped name results in a
LOAD and possible autoinstall for the wrong program.
2.1.3 CICS Down / Applid Status Tracking [ZNew] [ZCnv] [VNew] [VCnv]
Whether you are running MBC with EXCI (z/OS) or TCP/IP (VSE), neither can distinguish between a CICS region being
down and other scenarios preventing a successful open pipe (such as IRC being closed, invalid RDO connection or session
definitions). If you need to distinguish between these situations, we suggest setting the APPLSTS installation option to ‘Y’
or ‘F’ to enable Applid Status Tracking. Applid Status Tracking makes use of a special SAPL DN record added in the
BATSTAT file. This SAPL DN record can be added in one of two ways:
1. By adding an MBCBATCH step after the CICS job step with an SAPL DN command (Recommended)
2. By an operator reply of ‘DOWN’ to MBCB007 message.
If MBCBATCH finds the SAPL DN record present for the target Applid, then subsequent action is determined by the
APPLSTS setting.
If APPLSTS is ‘Y’, then a connection error will cause MBC to bypass commands to the next header card, bypass writing
Status Tracking records and to not set a return code.
If APPLSTS is ‘F’, then a connection error will cause MBC to bypass commands to the next header card, write Status
Tracking records (if STATFLAG=Y) and to set return code to ERRDOWN.
The SAPL DN tracking record is automatically deleted when a successful connect to the Applid is complete or when a new
SAPL UP command is passed to MBCBATCH. The SAPL DN record is also deleted by the MBCPRSTX BATSTAT
clean-up exit (Section 6.5).
42 Section II – Special Considerations

2.1.4 TCP/IP Debugging [VNew] [VCnv]
If you are having problems connecting or with other issues running the TCP/IP version of MBC, first verify you are
running a supported release of the CSI or BSI stack (Section 1.5.1). If you are, obtain tracing information to assist in
debugging the issue. See Appendix C for information on obtaining TCP/IP trace data.
2.1.5 Handling Extended Data [ZNew] [ZCnv] [VNew] [VCnv]

Several MBC commands provide the opportunity to send back large amounts of data from CICS to batch including CDAL,
CEDA, CEMT, QRYL and QRYS commands. In order to offer flexibility in how you choose to handle the extended data,
MBC provides the following: Installation Options EMTMSGS and LOGXDD and batch user exit MBCBLXGX.
The EMTMSGS option acts the same for MVS and VSE users and tells MBC whether to return extended data for CEMT
INQUIRE commands (EMTMSGS=Q) or all CEMT commands (EMTMSGS=A). If there are errors, then extended data is
returned regardless of the EMTMSGS setting. User exit MBCBLXGX is called allowing you to choose what to do with the
extended data, even if it is for errors.
The LOGXDD option is described separately for z/OS and VSE users below:
z/OS users
The LOGXDD option tells MBC whether or not to support an optional SYSLSTX DD to use for the extended data returned
from commands. If LOGXDD=Y and the SYSLSTX DD is present in your batch JCL, the extended data is written to the
SYSLSTX DD. Additionally, before each extended data line is written to the SYSLSTX DD, a call is made to the user exit
MBCBLXGX allowing you to choose what to do with the data line. By modifying the exit, you could choose for example
to skip the line, skip all of the extra data if there are errors, or write the data to a file.
If LOGXDD=Y and the SYSLSTX DD is not present, then LOGXDD=N is forced. If LOGXDD=N is set (or forced) then
extended data is written to the SYSLST DD, intermixed with normal data.
VSE users
The LOGXDD option tells MBC whether or not to support an optional target via an ASSGN where the extended data
returned from the commands is sent. If LOGXDD=Y, add an ASSGN card as follows in your MBCBATCH JCL:
// ASSGN SYS025,cuu where cuu is a secondary printer for the partition
SYS025 is the default DEVADDR. If SYS025 is already assigned in any of your MBCBATCH jobs, find a new unique LU
number to include in special job MBCJZLU which zaps the new LU into program MBCRLXGO. If for example you
choose SYS039, then you would need to run job MBCJZLU to zap SYS039 in place of SYS025 and also replace SYS025
with SYS039 in the above ASSGN card in your MBCBATCH JCL. POWER users could also add a POWER LST card
with different attributes to manage the separate output if desired:
* $$ LST DISP=H,CLASS=Q,LST=cuu
If the ASSGN card is present, the extended data is written to the cuu target. Additionally, before each extended data line is
written to cuu, a call is made to the user exit MBCBLXGX allowing you to choose what to do with the data line. By
modifying the exit, you could choose for example to skip the line, skip all of the extra data if there are errors, or write the
data to a file.
If LOGXDD=Y and the ASSGN is not present, then LOGXDD=N is forced. If LOGXDD=N is set (or forced), extended
data is written to the SYSLST DD, intermixed with normal data.
Section II – Special Considerations 43

2.1.5.1 Sample Extended Data Log [ZNew] [ZCnv] [VNew] [VCnv]
Below is a sample Extended Data Log with results from sample CEMT and CEDA commands.
{Start of sample CEMT INQ URI extended data log}

MBCB060-START OF CEMT LOG FOR T540 ++++++++++++++++++++++++++++++++++++++++
CEMT INQ URI(*)
URI(DFH$WUUR) SER ENA HTTP TCP(DFH$WUTC) HOST(*
) PATH(/CICSSystemManagement/* )
IPR(0.0.0.0 ) UNK TR
A(CWWU) PRO(DFHWUIPG)
URI(XFHWUURI) SER ENA HTTP TCP(XFHWUTCP) HOST(zos
) PATH(/SM/Atom/* ) ANA
IPR(0.0.0.0 ) UNK TR
A(CWBA) PRO(DFHW2IPG)
MBCB061-END OF CEMT LOG FOR T540 LINES(0000009) RESOURCES(0000002) -------
{End of sample CEMT INQ URI extended data log showing total log lines and number of resources}
{Start of sample CEDA IN GR(MACKQED) extended data log}

MBCB060-START OF CEDA LOG FOR T540 ++++++++++++++++++++++++++++++++++++++++
IN GR(MACKQED)
MBCX INSTALL
ALL
ATOMSERVICE ==>
BUNDLE ==>
CONNECTION ==>
. . .
TYPETERM ==>
URIMAP ==>
WEBSERVICE ==>
GROUP ==> MACKQED
LIST ==>
MBCB061-END OF CEDA LOG FOR T540 LINES(0000040) --------------------------
{End of sample CEDA IN GR(MACKQED) extended data log showing total log lines}
NOTE: The total lines returned do not include the MBCB060 and MBCB061 messages. Also, except for QRYL and
QRYS commands, MBC is displaying the lines as formatted by the corresponding CICS API interface (CEDA or CEMT).
2.1.6 Running with EXCI Session Userid [ZNew] [ZCnv]

If you run the EXCI version of MBC, have STATFLAG=Y and run with a USERID value specified in the SESSION
definition for an APPLID (see NOTE below) then please read the following. Others may skip this section.
If the XUSR field in message MBCB012 found in your JOB LOG under MBCB010 BATSTAT PROCESSING does not
match your SESSION USERID for the corresponding APPLID, then you should run batch utility MBCBDOM (Section
3.10.3) to add the USERID value using a DEFDOM card. If no Domain record exists, then use a DEFDOM card,
specifying the APPLID, descriptions and USERID. If a Domain record already exists for the APPLID, insert a DELDOM
card for the APPLID before the DEFDOM card. You can use a LSTDOM ALL card to verify the USERID value for all
APPLIDs defined in the BATCNTL Domain.
NOTE: We do not recommend specifying a USERID value in the EXCI SESSION definition for security reasons, since
all commands processed by the MBC CICS server would execute under this one USERID and not the Userid submitting
the batch job.

2.1.7 Transient Data Queue Handling
Manipulating TDQs defined as Resource Items
When you define a TDQ as a Resource Item, then you can use resource commands ALOR, ALSR, ALOG, UNAR and
UNAG. Intrapartition TDQs to enable with AL* commands and disable with UN* commands. Extrapartition TDQs are
more like files and are allocated, opened and enabled with AL* commands and unallocated, closed and disabled with
UN* commands.
ALOR TD qqqq
UNAR TD qqqq
qqqq - Name of Queue in CICS
Manipulating TDQs regardless of whether they are defined as Resource Items
You can use the CEMT SET command to enable or disable an Intrapartition or Extrapartition TDQ. Additionally, you
can add closed or open to the CEMT SET for an Extrapartition TDQ. An Extrapartition TDQ can be allocated or
unallocated using the ALOQ and UNAQ commands, although you must reference the DDNAME/DLBL (file) and not
the TDQ name in the command. An Extrapartition TDQ must be closed and disabled before it can unallocated and it
must be allocated before it can be opened and enabled.
CEMT SET TDQ(qqqq) CLOSED DISABLED

UNAQ ffffffff
ALOQ ddd ffffffff dsn
CEMT SET TDQ(qqqq) OPEN ENABLED
qqqq - Name of Queue in CICS

ffffffff - DDNAME/DLBL of the Extrapartition dataset in the CICS JCL
dsn - Dataset Name of the Extrapartition dataset
ddd - Disp = SHR, MOD or OLD
2.1.8 DL/I File Handling for z/OS

CEMT SET DLIDATABASE[(fileid)] [ALL] [STARTED|STOPPED|RECOVERDB|DUMPDB]
STARTED - The database is available for processing. It is physically opened when the first schedule request is
made against it.
STOPPED - Causes a physical close of the database.
RECOVERDB - Prohibits reads and updates. This allows a recovery utility to run in another region, following
which the database may be returned to online operation by setting it STARTED. The current system log is
closed and the next is opened.
DUMPDB - Prohibits updates on DL/I databases. You can run a backup utility in another region, after which you
can return the database to online operation by setting it STARTED.
For further explanation, please refer to IBM manual CICS - Supplied Transactions.

2.2 Conversion Considerations [ZCnv] [VCnv]
Review the following sections if you are converting to MacKinney Batch to CICS from CEMT from Batch.
2.2.1 Installation Option Changes [ZCnv] [VCnv]

Installation options ERRCODE and ERRCMD were replaced by a single ERRCMD. The previous default for ERRCODE
was 255 and for ERRCMD was 16. If you ran the MBCJCNV job in Section 1.7.2, the new ERRCMD value is copied from
the old ERRCODE value. Command errors whether they are an input error or an execution error are now treated the same.
Several installation options related to the old BATCNTL file transport method were removed (ICINTRVL,
ENAWRITO, DELAYCNT, INUSECNT, DISABLD). The status tracking function was redesigned making options
DISONLY and STATDEL unnecessary and those were removed. CONSFLAG was removed due to a restructuring of
all logging activity.
The following installation options were renamed: CLOREQST to CLOSRQST; CLOSECNT to CLOSRTRY;
CEMTCNT to CEMTRTRY; ERRFLSH to ERRCNCL; PERFORM to CEMTPERF; RETRYCNT to STATRTRY.
FAILACT and ERRWTOR were combined into a new FAILACT value. Values are converted automatically when you
run the MBCJCNV job in Section 1.7.2.
Old FAILACT Old ERRWTOR New FAILACT

C C C-Cancel
C Y W-WTOR
C N G-Go
F - G-Go
Option ENQXS is new and replaced the need to rename the old MTPBATXS module if you were using a cross-system
ENQ (z/OS) or LOCK (VSE). Set the value according to your current needs (Section 3.4).
Option EXTSEC is new and identifies whether you are using an external security manager (ESM). If you are using an
ESM (such as RACF), you must set up security on the CICS side in order to allow access to protected resources.
The following options are new. See the proper section for descriptions: DOMSEC (Section 3.10); LOGXDD and
EMTMSGS (Section 2.1.5); STRTUPMG and TRKNONFI (Section 7.2.1); CEDACMD (Section 3.4).
2.2.2 Message and Logging Changes [ZCnv] [VCnv]

The message format and numbers have changed significantly with MacKinney Batch to CICS. Logging on both the
batch and online side is more consistent with additional information available. The old CEMT from Batch product
created messages with a prefix of ‘<CMTx’ where x is ‘B’ for Batch messages, ‘E’ for Online messages, ‘I’ for
informational messages, and ‘W’ for warning messages. However, many of the ‘B’ and ‘E’ messages were
informational or warning messages. The new product uses a simpler system with a prefix of ‘MBCx’ where x is ‘B’ for
Batch messages and ‘E’ for online messages.
If you are running an automated operations or similar product intercepting messages, review the product to verify
whether you are checking for messages created by CEMT from Batch (<CMT prefix messages). See Appendix F for an
old and new message cross reference.
CEMT from Batch logged several non-critical messages to the console. MBC by default only writes critical
messages to the console. You can alter the MBC behavior to write all or select messages to the console by
modifying user exit, MBCBLOGX (Section 4.3.4).

2.2.3 New, Modified and Removed Commands [ZCnv] [VCnv]
One difference in MBCBATCH and MTPBATCH command processing is MTPBATCH ignored extraneous characters
after the last command parameter while MBCBATCH treats these as errors. A few customers have used this
undocumented “feature” to serve as command comments. Remove the extraneous characters using the MBCBCMDX
command exit or manually correct the cards for MBCBATCH. See Section 5.2 for details on the commands described
below.
New Commands:
ALOG/ALSG/CLOG/CLVG/ENAG/INQG/OPEG/UPDG/STSG are new commands for Resource

Groups (Section 3.8).
ALOQ/UNAQ are new commands using SVC 99 to allocate and unallocate TD Queues and files
defined in your startup JCL.
ALOR/ALSR/UNAR/STSR are new commands for Resource Items (Section 3.7).
CDAL sends a CEDA command (up to 4 lines) to CICS
CEDA sends a one line CEDA command to CICS
CLOV/CLVG does an OPEN before the CLOS to force VSAM to verify the file.
DOWNSTS is used in conjunction with IF logic to help determine which commands are
processed by Status Tracking if a CICS is down.
IF/ELSE/ENDIF commands allow conditional execution logic to control command flow.
IPTR displays trace information when running MBC TCP/IP option.
LNKL allows you to pass up to 320 bytes of commarea to a CICS program
OPTR allows overrides to most installation options for the current job run.
QRYL/QRYS allows you to query various CICS resources and return the results back to batch
RL*SQ, R*QY, R*UP, GL*SQ, G*QY and G*UP commands (z/OS only) perform functions on RLS
datasets (see Section 5.1.2 for all of the RLS commands).
SET allows you to SET both a MAXCC value and user variables to facilitate additional flow control.
STRL allows you to pass up to 320 bytes of data to a CICS program
WAIT command now supports seconds as well as minutes.
Modified Commands:
ALOC/UNAL command logic was modified to take advantage of the built-in dynamic allocation and
unallocation within CICS TS (Section 2.2.4). The method used for the UNAL command in CICS TS requires
simply closing the file to force unallocation. The UNAL can only be used with files that are dynamically
allocated the first time the file referencing the dataset is opened (the DSNAME and DISP must be specified in
the FILE definition). This is different from the old CEMT from Batch product which used SVC 99 to perform
the unallocation. If the performance of SVC 99 is needed, you can use ALOQ and UNAQ commands in place
of ALOC and UNAL.
LINK command logic requires consideration. The batch processor transaction (MBCX) has a default
TASKDATALOC of ANY. If you attempt a LINK command to a 24-bit program, an AEZC ABEND occurs.
Either re-link the user program to 31-bit or change TASKDATALOC for transaction MBCX to BELOW.
Also, if the target LINK program issues any terminal related CICS commands (CONVERSE, SEND,
RECEIVE, SIGNON, etc.), an AEPL ABEND occurs. This is due to EXCI using a DPL link. Remove
terminal related commands or change to use STAR command rather than LINK.
Removed Commands:
IDIS and RINT were removed. The default action in the batch command user exit MBCBCMDX is to
ignore these commands. The exit can be modified if you desire a different action or you can simply
remove the IDIS and RINT commands from your JCL.

2.2.4 Changes in Dynamic Allocation [ZCnv] [VCnv]
With CICS Transaction Server (TS), IBM introduced CICS internal dynamic allocation and de-allocation which is
implemented by adding the DSNAME in the RDO file definition and by removing the file DD from the CICS startup
JCL. MBC supports this method without changes to your JCL. However, unless you are changing the dataset name, you
should remove the unnecessary UNAL and ALOC commands since a CLOS command forces de-allocation and an
OPEN command forces allocation to occur.
If you have files defined in your startup JCL, the UNAL and ALOC commands will no longer work for dynamic
allocation for these files.. Either (1) convert the UNAL/ALOC commands to new UNAQ/ALOQ commands which use
the old SVC 99 method for dynamic allocation or (2) define the DSNAME values in your RDO and remove the file
definitions from your startup JCL. The latter is our recommended approach if at all possible. If you require changing the
commands to UNAQ and ALOQ, you can use user exit MBCBCMDX to aid in the conversion. MBCBCMDX can be
easily tailored to modify UNAL commands to UNAQ and ALOC commands to ALOQ. See Section 4.3.2 for additional
details on customizing MBCBCMDX.
If you have TDQ datasets defined in your startup JCL, use UNAQ/ALOQ instead of UNAL and ALOC commands.
See the discussion above on using MBCBCMDX to aid in the conversion.
2.2.5 Source Code Modifications [ZCnv] [VCnv]

If you have modified your version of CEMT from Batch for example to add support for a new command, restrict a
command or have made other unique changes for your environment, then read on, otherwise you can skip this section.
Source code is not provided for the MacKinney Batch to CICS product, however, many new user exits are available.
See Section 4.3 for available Batch User Exits and Section 6.4 for Online User Exits.
We provide exit points at locations most likely required. If you have modifications not fitting in one of these exit points,
please contact MacKinney Systems.
2.2.6 File Status Tracking Changes [ZCnv] [VCnv]

The old File Status Tracking product was completely redesigned and is now included as a feature in the new MBC
product. ‘File’ was dropped from the old product name when referring to the new feature because Status Tracking also
handles transactions, programs and TDQs.
Contention issues for the BATSTAT file with other batch jobs prevented many users from taking advantage of this
optional feature. The old BATSTAT file was opened for update in CICS when the STATDEL=Y option was set,
creating contention during CICS startup. To rectify this issue, the STATDEL option was removed. This was done to
remedy the contention issue and prevent possible data corruption that could occur when deleting the last entry after
processing (which potentially places a file being in an improper status after an unexpected CICS restart). All
BATSTAT file updates are now done in batch - helping minimize contention. Make sure you remove the old
BATSTAT RDO (FCT) entries from your CICS definitions and use the new definition (see MBCJRDOF).
WARNING! Because all entries are not deleted after running the startup program, manually remove older entries to
prevent an excessive build-up of data in the file. The build-up can occur for files removed from an Applid or invalid
resource names. See Section 7.2.7 for tips on Periodic Maintenance.
2.2.7 Using BATCNTL Domain Applid Records to Limit Access [ZCnv] [VCnv]
If you were using multiple BATCNTL files for the purpose of restricting access to only the Applids defined in the
Applid table, refer to Section 3.10 for a similar method to use with MBC. This new method allows you to use Domain
Applid Records (Section 3.10) in combination with setting DOMSEC=Y. This approach requires creating multiple
BATCNTL files (one for each domain such as test or production) and defining specific Domain Records (one for each
Applid to allow access) within each of the BATCNTL files. When DOMSEC=Y is specified, the target CICS Applid
is used to search the Domain Records within the BATCNTL defined in the MBCBATCH JCL. If a matching Domain
Record is found, processing continues; otherwise a security error is generated and the commands are not sent.

2.2.8 Security Conversion Considerations [ZCnv] [VCnv]
A design consideration for MBC security was to provide a means of basing the security on the MBCBATCH Userid.
MBC EXCI always propagates the MBCBATCH Userid to CICS regardless of configuration settings. MBC TCPIP can
be set to work this way by setting MBC installation option EXTSEC=Y.
CEMT from Batch commands ran under a single Userid based on who enables the Online Interface. If the Online
Interface was started from the PLT, then the single Userid was PLTPIUSR, or Region Userid if there was no
PLTPIUSR. If the Online Interface was started manually, then the single Userid was the Userid starting the Online
Interface.
MBC users using the TCPIP interface can simulate this single Userid approach for Security by adding an IP Exec User
value within the Domain Record for the Applid (Section 3.10.2). The EXCI interface does not support the single Userid
approach. For z/OS users not wanting security based on the MBCBATCH Userid and instead preferring to use the
single Userid approach (used by CEMT from Batch), contact MacKinney Systems to discuss options.
2.2.9 Tips to avoid Production JCL Changes [ZCnv] [VCnv]

In most cases, CEMT from Batch is converted to MacKinney Batch to CICS without changing your production
Batch JCL. The commands are backwards compatible, so no changes are required. That leaves Datasets, the
STEPLIB or LIBDEF modules, and the EXEC program:
Datasets
When you are ready to cutover to production, rename the new BATCNTL and BATSTAT (optional) dataset
names to the dataset names used for CEMT from Batch (Section 1.9.2).
STEPLIB or LIBDEF
If you have used a STEPLIB or LIBDEF for CEMT from Batch, remove all old modules and replace with all of the
modules from the MacKinney Batch to CICS Loadlib (Section 1.9.6). If you are running the EXCI version of
MacKinney Batch to CICS, you must also copy the CICS???.SDFHEXCI modules to the STEPLIB or LIBDEF
(Section 1.7.7) or those modules be made available in the LINKLIST or equivilant.
EXEC program
CEMT from Batch executes MTPBATCH and MacKinney Batch to CICS executes MBCBATCH. . To avoid a
rename, MacKinney Batch to CICS supplies an alias module MTPBATCH executing MBCBATCH. As long as
the alias MTPBATCH module is copied to the STEPLIB or search chain to replace the original MTPBATCH
program, the correct module executes.
If you are z/VSE and have to specify a SYSPARM to identify the Stack ID (Section 1.8.1), see sample program
(SAMPPRM) to avoid changing the JCL. Customize SAMPPRM to allow selecting SYSPARM dynamically
depending on the CICS applid. Customize this program and catalog as MTPBATCH. This sample program
launches MBCBATCH after setting the parm value.

2.3 Security Considerations [ZNew] [ZCnv] [VNew] [VCnv]
2.3.1 Security Overview [ZNew] [ZCnv] [VNew] [VCnv]

MacKinney Batch to CICS works along with your External Security Manager (i.e. RACF, ACF2, Top Secret) to limit
access to MBC usage and to protect resources from unauthorized access. MBC uses Systems Programming Interface
(SPI) commands in CICS, so if RESTYPE SPCOMMAND is protected, you must allow UPDATE authority for this
profile to each user allowed to submit MBCBATCH jobs or execute online operations.
2.3.1.1 Securing access to the MBC CICS server

USING EXTERNAL SECURITY
The recommended approach for both EXCI and TCPIP to prevent users from submitting commands through MBC is
using your External Security Manager to restrict READ access to the BATCNTL file(s).
NOTE for EXCI users: MBC’s connection to CICS is defined as specific which implies security is based on the
MBCBATCH job’s submitting USERID. The name supplied for the specific pipe is MBCRXCI which is protected by
profile DFHAPPL.MBCRXCI. If you protect this profile (not recommended), you must ensure you supply appropriate
entries for MRO logon and bind-time security for each submitting USERID (allow UPDATE authority).
USING DOMAIN SECURITY
Another approach to restrict access to specific regions without requiring an External Security Manager is to use Domain
Records (Section 3.10) in combination with setting installation option DOMSEC=Y. This approach requires creating
multiple BATCNTL files (one for each domain such as production or test) and defining specific Domain Applid
Records (one for each Applid where access is allowed) within each BATCNTL file. When DOMSEC=Y is specified,
the target CICS Applid is used as a search key to the Domain Records within the BATCNTL file defined in the
MBCBATCH JCL. If a matching Domain Applid Record is found for the target Applid, processing continues;
otherwise a security error is generated and the commands are not sent.
COMBINING EXTERNAL SECURITY AND DOMAIN SECURITY
These two approaches can be combined if you have an external security manager. You can permit READ access to the
BATCNTL file for limited users. Users without access are not able to submit commands to any MBCBATCH job using
the BATCNTL file. If allowed READ access, a user can still be denied access to a target Applid, if the target Applid is
not found in a search of the Domain Applid Records within the BATCNTL file.
2.3.1.2 Securing your CICS resources (files and transactions)

Resource protection (i.e. files and transactions) is determined by the Execution Userid associated with MBCX (see
tables in this section), the transaction executing your batch commands in CICS, along with various settings in your
External Security Manager. Also review CMDSEC and RESSEC settings for the MBC transactions (defaults are NO)
and the SIT settings for XCMD. XFCT, XTRAN, etc. See Section 2.3.2 and 2.3.3 for information on MBC transactions
and files to assist in determining how to secure these resources.
Most MBC commands changing the status (i.e. OPEN/CLOS) of a resource (i.e. FILE/TRANID), require UPDATE
access. See the “Resource and command check cross reference” section in the CICS RACF Security Guide (or
equivalent for other ESM) for help in determining access levels and resources required.
If you specify EXTSEC=Y in your MBC Installation Options and XUSER=YES in your SIT, then surrogate privileges
must be allowed for both the CICS Region Userid and the PLTPIUSR Userid as both Userids start transactions with a
new userid for several of the MBC transactions. Carefully review Section 2.3.2.
TIP: Review Section 1.9.9 for security considerations in cutting over to production.

For EXCI, the Execution Userid is determined by the Link Userid (Userid submitting batch job MBCBATCH) and the
CICS Region Userid (Userid submitting CICS startup job or is associated with the CICS Started task). If the Link
Userid and the CICS Region Userid are the same (not recommended), then CICS forces the Execution Userid to be the
SIT Default User. If the Link Userid and the CICS Region Userid are different (recommended), then the Execution
Userid becomes the Link Userid. The following table offers an illustration assuming CICSUSER is the SIT Default
User value and STCCICS is the Region Userid.
MBCBATCH CICS Execution Userid

Link Userid Region Userid
Userid associated w/commands
STCCICS STCCICS STCCICS CICSUSER
USERA USERA STCCICS USERA
Contact MacKinney Systems if you prefer using a single Execution Userid regardless of who is submitting the
MBCBATCH job.
For TCP/IP, the Execution Userid is determined by a combination of the Userid submitting batch job MBCBATCH,
the value for the EXTSEC installation option and the optional override single Execution Userid specified on the
Domain Applid Record for the target Applid. The following table offers an illustration assuming USERA is the Userid
submitting the MBCBATCH job.
MBCBATCH EXTSEC DOMSEC Domain Exec CICS Exec Userid

Userid value value Userid associated w/commands
USERA Y * CICSTS51 CICSTS51
USERA Y * blank USERA
USERA N * Ignored Userid of the IP Listener
* NOTE: DOMSEC=Y is assumed regardless of the displayed value shown for TCP/IP since TCP/IP requires the
Domain Applid Record to connect to the target region.
2.3.2 Securing MBC CICS Transactions [ZNew] [ZCnv] [VNew] [VCnv]

Below is a list of MBC transactions to aid in determining Transaction Security.
WARNING for Status Tracking Users! If Status Tracking is active, you are running an external security
manager and are running with SIT parameter XUSER=YES, then carefully review your security for the CICS
Region Userid and PLTPIUSR Userid with respect to surrogate authority. These userids need authority to start the
MBCR Non-Terminal transaction with a surrogate userid. Failure to allow surrogate authority prevents Non-
Terminal transactions from starting which ultimately prevent Status Tracking from correctly setting resources to
their proper status and batch jobs from successfully propagating security or running commands.
WARNING for TCP/IP MBC Version Users! If IPVERS=Y, you specify a non-blank IP Exec User value in
your Domain Applid profile(s), EXTSEC=Y, and you are running with SIT parameter XUSER=YES, then
carefully review your security for the CICS Region Userid and PLTPIUSR Userid with respect to surrogate
authority. These userids need authority to start the MBCZ Non-Terminal transaction with a surrogate userid.
Failure to allow surrogate authority prevents Non-Terminal transactions from starting which ultimately can
prevent the TCP/IP Connection from running commands.
MBCA – Tranid for the main product administration panel. Authorized users can change installation options,
product password(s), administer Applid Groups, Resource Items, Resource Groups, Status Tracking
Maintenance and Domain Applids, including the ability to alter the status of files, transactions,
programs and TDQs using Resource Items and Groups.

MBCB – Tranid for the read-only version of product administration panel. Authorized users can view
installation options, product password(s), Applid Groups, Resource Items, Resource Groups and
Status Tracking Maintenance and Domain Applids.
MBCC – Tranid for the Online Command Processor panel. Authorized users can execute a subset of the batch
commands using an online interface including commands that update the resource status for files,
transactions, programs and TDQs.
MBCD – Fast path tranid for administering Domain Applid records. Authorized users can add and update
Domain Applid records. (Section 3.10)
MBCG – Fast path tranid for administering status of a selected Resource Group. Authorized users can update
the status of resources (files, transactions, programs, TCPIP services, and TDQs) as well as view the
current status. New Resource Groups can be created, updated and deleted.
MBCH – Internal use tranid for displaying Help screens.
MBCI – Fast path tranid for administering Resource Items. Authorized users can update the status of
resources (files, tranids, programs, TCPIP services,and TDQs) as well as view the current status.
New Resource Items can be created, updated and deleted.
MBCL – Fast path tranid for administering a selected Applid Group. No online resources can be directly altered.
See Section 3.6 for usage information about Applid Groups.
MBCM – Internal use tranid started by command processor (MBCX) under the Execution Userid to send a
message to a terminal (MESG, MSGL).
MBCO – Fast path tranid for administering status of a selected Resource Group. Authorized users can update
the status of resources (files, transactions, programs and TDQs) as well as view the current status.
MBCP – Tranid for support of STAR MBCP command to allow sending data to applications requiring
RECEIVE (not RETRIEVE) to pass data.
MBCQ – Tranid is not used if SHUTCMD=N, otherwise MBCQ is started by command processor (MBCX)
to shut down CICS. If EXTSEC=Y, then the Execution Userid value is first checked for authorization for
MBCQ using QUERY SECURITY. If the test fails, then MBCQ is not started and the SHUT command
fails. If the Execution Userid passes authorization checking, then MBCQ is started with the Execution
Userid. If EXTSEC=N, then MBCQ is started on the SHUTTERM Termid running under the Userid
associated with the SHUTTERM terminal. The Userid for the SHUTTERM terminal should also be
authorized for MBCQ. It is recommended to use a Preset Security USERID value for SHUTTERM
to ensure MBCQ is authorized to run.
MBCR – Non-Terminal transaction started by optional PLT program to process BATSTAT file if Status
Tracking is enabled. Access required by PLTPI Userid. Other userids can be restricted.
MBCS – Fast path tranid for administering status of a selected Resource Group. Authorized users can use this
tranid to view the status of resources (files, transactions, programs and TDQs) but cannot alter the current
status.
MBCU – Tranid for the read-only version of product administration panel except for options 0-2. Authorized
users can view records for Applid Groups, Resource Items, Resource Groups, Status Tracking
Maintenance and Domain Applids
MBCX – Internal use tranid started on session terminal by CICS EXCI listener (z/OS) under the Execution
Userid to process commands coming from MBCBATCH (all commands come through this tranid).
Access required for each userid submitting commands via MBCBATCH. Securing this transaction
denies access to all CICSs. Limiting access to the BATCNTL file is one method to prevent
unauthorized users from accessing CICS resources via the MBCBATCH EXCI interface.

MBCZ – Non-Terminal internal use tranid started by CICS TCP/IP Listener (VSE) under the Execution Userid
to process commands coming from MBCBATCH (all commands come through this tranid). Access
required for each userid submitting commands via MBCBATCH. Securing this transaction along
with limiting access to the BATSTAT file is one method to prevent unauthorized users from accessing
CICS resources via the MBCBATCH TCPIP interface.
MBC1 – Fast path tranid for administering Status Tracking Maintenance. Authorized users can use this
tranid to view the status of resources (files, transactions, programs and TDQs) from the BATCSTS file.
Users cannot alter the current status with this tranid.
2.3.3 Securing MBC Files [ZNew] [ZCnv] [VNew] [VCnv]

MBC only has three files. But when it comes to security, almost everything that happens with MBC passes
through one of these files.
• Executing commands with MBCBATCH uses the BATCNTL (read-only) and BATSTAT (update) files
in batch and BATCNTL (read-only) and BATCSTS (update) files in CICS.
• Executing commands online (CICS) uses the BATCNTL (read-only) and BATCSTS (update) files
• Online administration uses primarily the BATCNTL (update) file with the exception of Status Tracking
Maintenance, which uses the BATCSTS (update) file
• Batch administration utilities use the BATCNTL file ((MBCBAGRP, MBCBCPRT, MBCBDOM,
MBCBRGRP and MBCRITM). LST* functions for all utilities are read-only, but other functions require
the BATCNTL file to be opened for update.
• MBCBCUTL and MBCBCPRT utilities use the BATCNTL file. LIST and XREF functions are read-
only, but other functions require the BATCNTL file to be opened for update.
• MBCBSUTL utility uses the BATSTAT file. PRT* functions are read-only, but other functions require
the BATSTAT file to be opened for update.
• MBCBCPRE Startup Manager pre-CICS startup utility uses all three files. The BATCNTL file is
opened read-only, while the BATCSTS and BATSTAT file are opened for update.
TIP! Since most administration can be performed using Batch utilities, it is important to keep these utilities in
mind when designing your security.
Below is a list of the MBC files and additional notes to aid in designing Security.
BATCNTL – File contains MBC administrative options and resource definitions. Each BATCNTL file can be
shared by multiple CICS regions which is termed a domain. Options are usually updated only in one
primary administrative region of the domain or by batch. Security to allow updates in the primary
region is optional and can be controlled through limiting access to Tranid MBCA (Section 2.3.2)
UPDATE access may also be required for batch administration utilities, depending on the function.
READ access is needed for MBCBATCH jobs, as well as regions other than the primary
administrative region.
BATCSTS – File used for tracking CICS Resource Status if Status Tracking is enabled (STATFLAG=Y). The
BATCSTS file cannot be shared so there is one unique BATCSTS file per region. All users
submitting MBCBATCH jobs and users eligible for running transactions MBCA, MBCG and
MBCC must have UPDATE access to BATCSTS file. This file is also used by the Startup Manager
pre-CICS startup utility MBCBCPRE with UPDATE access.
BATSTAT – File used for tracking Resource Status commands when CICS is down and Status Tracking is
enabled (STATFLAG=Y). Each BATSTAT can be shared by multiple CICS regions. All users
submitting MBCBATCH jobs must have UPDATE access to BATSTAT file. This file is also used
by the Startup Manager pre-CICS startup utility MBCBCPRE with UPDATE access.

Section III
Administration
3.1 Administration Overview
MacKinney Batch to CICS provides online administration for defining installation options, product password(s), Resource
Items, Resource Groups, Applid Groups, Domain Applid records and CICS Status Tracking records. All of the
administration records are kept on the BATCNTL file. The BATCNTL file can be shared by more than one region and all
of the regions sharing administrative records combine to form the domain of the file. We recommend minimally creating a
Test and Production domain (defining at least two BATCNTL files). If you need to maintain separate options or group
definitions beyond the Test and Production domains, you can define additional BATCNTL file(s) with each file associated
with its own domain of CICS regions.
Most administrative functions have batch alternatives which are described under the function. Updates in batch require
exclusive control of the BATCNTL file, so no CICS regions can have the BATCNTL file open for update.
By default, the attributes of the BATCNTL file are set to read-only in all regions. MacKinney Batch to CICS dynamically
adjusts the attributes of the BATCNTL file to update mode when a user enters the administrative update transaction,
MBCA. When MBC detects the first usage of MBCA in a region, special TSQ, MBCADMFQ is created and a counter of
concurrent users is initialized. If another user issues MBCA in the region, the counter is incremented. The counter is
decremented when a user exits the Administration screens. As long as the counter is positive, the file definition remains in
update mode. When the last user exits Administration, the attributes of the BATCNTL file are changed back to read-only.
This method allows administration to take place in any region where the BATCNTL file is defined, but only in one region
at a time.
TIP! If you notice the BATCNTL file is not reset to read-only after all users have exited from administration screens, go
through the following steps to resolve the issue:
1. Enter ‘MBCA,CLR’ from a blank screen – this should open the Administration Menu screen and resets the TSQ
counter. If the Administration Menu does not open in update mode when you enter ‘MBCA,CLR’, then the
BATCNTL file is open for update in another CICS or batch region. For the CICS regions, use CEMT INQ
FIL(BATCNTL) to check each region looking for UPD, ADD, DEL flags and when found, try this step again
(assuming no one is using MBCA).
2. After successfully entering ‘MBCA,CLR’ and seeing the Administration Menu displayed, the BATCNTL file
should be reset to read-only mode when you exit the menu.
54 Section III – Administration

3.2 The Administration Menu
The Administration Menu provides access to the online administrative functions. Enter ‘MBCA’ for update access to this
menu, ‘MBCB’ for read-only access or ‘MBCU’ for read-only access to options 3-7. If you are sharing the BATCNTL
file among several regions, then only one region at a time can be opened for update access. If you enter ‘MBCA’ and
update access is not available for the region, an error message is displayed.
MBCMADM MacKinney Batch to CICS Rel x.x 05/22/20 09:40:36

Mode: UPDATE Administration Menu Applid: DBDCICSA
BATCNTL: MACS.MBC.BATCNTL
0 - Password Maintenance
1 - Installation Options
2 - Display PTFs
3 - Applid Groups
4 - Resource Items
5 - Resource Groups
6 – Status Tracking Maintenance (STATFLAG=Y Only)
7 – BATCNTL Domain Applids
OPTION ==> _ OPTION DATA==> ________
ENTER=Select Option PF1=Help PF3=End
To select an option on the Administration Menu, enter the number corresponding to the desired option after the OPTION
==> prompt and press the ENTER key. To end the administration session, press the PF3/PF15 key.
OPTION - Enter the number corresponding to the desired option.

0 – Select option 0 to display the Password Maintenance screen.
1 – Select option 1 to display the Installation Options screen.
2 – Select option 2 to display PTFs applied to MacKinney Batch to CICS.
3 – Select option 3 to maintain Applid Groups. Applid Groups let you define lists of Applids used in CICS headers to simplify
the process of routing to multiple Applids. See Section 3.6.
4 – Select option 4 to maintain Resource Items. Resource Items let you define resources (files, transactions, programs
and TDQs) for use with Resource Groups and for use with the optional Startup Manager. See Section 3.7.
5 – Select option 5 to maintain Resource Groups. Resource Groups let you define multiple resources (files, transactions,
programs and TDQs) used with ALOG, ALSG and UNAG commands to operate on several resources at one time.
See Section 3.8.
6 – Select option 6 to maintain Status Tracking (CICS Resource Status) records. CICS Resource Status records are used
by Status Tracking to reset to the last status (warm start emulation) or by the Startup Manager for specific resource
control. CICS Resource Status records are stored in the BATCSTS file (one per region). See Section 3.9. Option is
ignored if Status Tracking is not enabled (STATFLAG=N). See Section 7.1.
7 – Select option 7 to maintain Domain Applid records. Domain Applid records let you limit the target Applids for the
BATCNTL file defined to the current region if option DOMSEC is set to ‘Y’. See Section 3.10.
OPTION DATA – Is reserved for overriding the default action for a selected Option. Currently, no normal use option data
values are supported.
Section III – Administration 55

3.3 Password Maintenance
The Installation Passwords screen displays when selecting option 0 from the Administration Menu. This screen lets you
specify your MBC installation passwords for site authorization.
MBCMPWD MacKinney Batch to CICS 05/22/20 11:15:36

Mode: UPDATE Installation Passwords Applid: DBDCICSA
BATCNTL: MACS.MBC.BATCNTL CPUID: 12345
Overtype Password Fields Below, One For Each CPU.
PASSWORD 1: AAAAAAAAAAAAAAAA
PASSWORD 2: BBBBBBBBBBBBBBBB
PASSWORD 3: CCCCCCCCCCCCCCCC
PASSWORD 4: DDDDDDDDDDDDDDDD
PASSWORD 5: EEEEEEEEEEEEEEEE
PASSWORD 6: FFFFFFFFFFFFFFFF
Enter=Update PF3=End
To update values on the Installation Passwords screen, enter the password value supplied by MacKinney Systems in the
Password fields 1 through 6. Up to 6 password values may be entered for each site, one for each CPU. Press PF3/PF15 to
return to the Administration Menu.
3.3.1 Installation Passwords via Batch

Batch utility MBCBCUTL allows you to list, add, modify and delete MBC installation passwords. Functions DPWD and
PASS require exclusive access to the BATCNTL (file must not be open for Update in any CICS region). Sample JCL is in
source member MBCJCUTL. The format of the password-related control cards are listed below. Multiple cards can be
input in the same job
See Section 4.2.1 for a full description of MBCBCUTL functions.

LIST PWDS list passwords.
PASS n pppppppppppppppp add/modify password. Requires Exclusive access of BATCNTL.
DPWD n delete password. Requires Exclusive access of BATCNTL.
n - identifies password slot (1-6) used to add or modify (PASS) or delete (DPWD)
pppppppppppppppp – identifies password value to add or modify (PASS) or delete (DPWD)
Example MVS JCL
//STEP1 EXEC PGM=MBCBCUTL

//STEPLIB DD DSN=your.MBCxx.LOADLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//BATCNTL DD DSN=your.BATCNTL,DISP=SHR
//SYSIN DD *
PASS 1 1234567890123456
LIST PWDS
/*
Example VSE JCL
// JOB MBC$CPRT BATCH UTILITY

// LIBDEF PHASE,SEARCH=your.MBCxx.LOADLIB
// DLBL BATCNTL,'your.BATCNTL',,VSAM,CAT=yourCAT
// EXEC MBCBCUTL
PASS 1 1234567890123456
LIST PWDS
/*

3.4 Installation Options
The Installation Options screen displays by selecting option 1 from the Administration Menu. This screen lets you update
the options described below. Most options can be overridden in the batch client using command OPTR (see OPTR
command in Section 5.2).
MBCMOPT MacKinney Batch to CICS 05/22/20 11:15:36

Mode: UPDATE Installation Options Applid: DBDCICSA
BATCNTL: MACS.MBC.BATCNTL CICSRel: 0680
Online Options:
PREFIX : MBC TDMESGQ : CSMT SHUTTERM: CMDEXIT : N
CLOSDIS : Y CLOSRQST: N CLOSRTRY: 002 CEMTRTRY: 001
LOADPGM : N RLUPDIS : Y
Batch Options:
ERRWARN : 000 ERRDOWN : 004 ERRDRLS : 006 ERRCMD : 008
ERRSEC : 012 ERRCNCL : 016 DOWNNON : B DOWNSPC : F
FAILACT : G HDROVER : N COLUMN80: N ENQXS : N
APPLSTS : F LOGXDD : Y EMTMSGS : A
Security Options:
EXTSEC : Y DOMSEC : N CEMTPERF: N SHUTCMD : N
CEDACMD : Y
Status Tracking Options:

STATFLAG: N STATRTRY: 002 ERRSTS : 000 STRTUPMG: N
TRKNONFI: Y
Enter=Update PF1=Help PF3=End PF8=ApplNum
To update values on the Installation Options menu, overtype the option(s) you desire to change and press ENTER to save
the new values. Press PF3/PF15 to return to the Administration Menu. Press PF1/PF13 for Help. Press PF8/20 to display
the compatibility CICS APPLID Number/Name Definition screen which allows you to update CICS Applids defined in the
BATCNTL file. Explanations of the option fields follow.
Online Options: - These options control the operation of the online programs.
PREFIX - 3-character prefix for all transactions, programs and maps. Default is ‘MBC’ (MBCA, MBCMADM, etc.).
WARNING! If value is changed, all programs (MBCP*) and maps (MBCM*) must be renamed in the MBC load library
and all CICS transaction(MBC*), program(MBCP*) and map(MBCM*) definitions changed to match the new prefix.
TDMESGQ - The CICS transient data queue where messages are written. The default value is 'CSMT'.
SHUTTERM - Specify the CICS TERMID where the shutdown command (Tranid MBCQ) executes for sites running with
EXTSEC=N. For sites running with EXTSEC=Y, the SHUT command runs under the Execution Userid. The
SHUTTERM parm is ignored if SHUTCMD=N or if EXTSEC=Y. Suggested value is 'CNSL'.
TIP! It is recommended using a Termid definition to include a pre-assigned USERID value authorized for transaction
MBCQ. See SHUT command.
CMDEXIT - Specify 'Y' to use command user exit MBCPCMDX, or 'N' (DEFAULT) to not use the exit. Exit must be
modified and assembled to before using (Section 6.4). NOTE: Batch user exit MBCBCMDX is always called regardless
of the setting for CMDEXIT.
CLOSDIS - Specify 'Y' (DEFAULT) to set files DISABLED for close commands. 'N' closes files without the DISABLED
option; CICS sets them UNENABLED.
CLORQST - Specify 'Y' to accept CLOSE REQUESTED as a successful completion of a close command. 'N' (DEFAULT)
treats it as an error.

CLOSRTRY - Number of times to attempt a CLOS command before treating the error as a command failure. Each retry
has a 5-sec delay. Default is 2, so after initial CLOS attempt, the CLOS is retried once. Only applicable when using CLOS
commands and commands issuing a CLOS, such as INQY and UPDT.
CEMTRTRY - Number of times to attempt a CEMT command before treating the error as a command failure. Each retry
has a 5-sec delay. Default is 1, so if a CEMT command fails, it is not retried. Only applicable when using CEMT
commands.
LOADPGM – Specify ‘Y’ to LOAD PROGRAM before PHAS/NEWC or CEMT SET PROG command to prevent
PGMIDERR when program autoinstall is active (PROGAUTOINST=AUTOACTIVE). ‘N’ (default) is forced if
PROGAUTOINST=AUTOINACTIVE. See Section 2.1.2.
RLUPDIS - Specify 'N' (DEFAULT) to set files for update, RLS use and leave files ENABLED after R*UP and G*UP
commands. Specify 'Y' to set files for update and RLS use, but leave files DISABLED after the commands.
Batch Options: - These options control the operation of the batch client program MBCBATCH.
ERRWARN: - Default Job MAXCC (0-255) when command encounters a warning condition (i.e. PGMIDERR on generic
PHASEIN, DSIDERR on group file operation, or "NO MATCHING ENTRIES" on QRYS/QRYL command) during
execution. If ERRWARN value is set to a non-zero value, you can excluded matching conditions by specifying them in
MBCBCRCX (see comments in MBCBCRCX source). Return code exit MBCBCRCX is not called if a command
encounters a warning condition and ERRWARN=0. Default is 0.
ERRDOWN - Default LASTCC value (0-255) used when a pipe cannot be opened for a target CICS Applid. Default is 4.
See also DOWNNON and DOWNSPC.
ERRDRLS - Default LASTCC value (0-255) used when an @RLS1GRP header pipe cannot be opened for any target
CICS in the specified ApplGrp. Default is 6. ERRDRLS is ignored if DOWNNON = ‘B’ (Bypass - CC is not set) or
DOWNNON = ‘C’ (Cancel - CC is set to ERRCNCL). See DOWNNON.
ERRCMD - Default LASTCC value (0-255) used when a command failure occurs. Default is 8. See also FAILACT.
ERRSEC - Default LASTCC value (0-255) used when a security error occurs. Default is 12.
ERRCNCL - Default LASTCC value (0-255) used when either an Option parameter (DOWNNON, DOWNSPC or
FAILACT) or Operator requests the job to cancel after an error. Default is 16.
DOWNNON - Default action when a connection failure occurs while using CICS ALL, APPLGRP or RLS1GRP headers.
Enter W-WTOR | C-Cancel | F-Flush | B-Bypass. Default is 'F'. WTOR prompts operator for action (Retry | Bypass | Flush
| Cancel). Cancel immediately cancels step with CC=ERRCNCL. Flush flushes cards until the next CICS header, produces
Status Tracking records (STATFLAG=’Y’) and sets CC=ERRDOWN or ERRDRLS (RLS1GRP). Bypass is similar to
flush except CC is not set and no Status Tracking records are produced. WTOR reply ‘Retry’ retries connect.
DOWNSPC - Specify action when a connection failure occurs while using a header for a specific target CICS Applid.
Enter W-WTOR | C-Cancel | F-Flush | B-Bypass. Default is ‘F’. WTOR prompts operator for action (Retry | Bypass | Flush
| Cancel). Cancel cancels step with CC=ERRCNCL. Flush flushes cards until the next CICS header, produces Status
Tracking records (if STATFLAG=’Y’) and sets CC=ERRDOWN. Bypass acts like flush except CC is not set and no Status
Tracking records are produced. WTOR reply ‘Retry’ retries connect.
FAILACT - Default action when a command failure occurs. Enter G-go | C-cancel | W-WTOR. Default is 'G'. WTOR
prompts operator for action (Retry | Cancel | Go). Go continues the job with the next command and sets RC=ERRCMD.
Cancel immediately cancels the step and sets RC=ERRCNCL. Retry (WTOR reply) retries the command.

TIP! *HDROVER and *COLUMN80 options are provided for compatibility with old CEMT from Batch users.
The recommended path is to set HDROVER to ‘N’ and use CICS header cards.
*HDROVER - Specify ‘Y’ to allow override of a CICS header card by adding a CICS number in command card column
80 (or 72) determined by COLUMN80. Specify ‘N’ (DEFAULT) to not allow override of CICS header cards.
*COLUMN80 - Specify ‘Y’ (DEFAULT) to use CICS number in column 80 of each command card or ‘N’ to use CICS
number in command card column 72. COLUMN80 is ignored if HDROVER=’N’.
ENQXS - Specify ‘Y’ to ENQ across multiple systems (including LPARs) or ‘N’ (DEFAULT) to ENQ only on the
LOCAL system. ‘Y’ causes MBCBATCH to ENQ/DEQ using the ‘SYSTEMS’ parameter rather than the ‘SYSTEM’
parameter for z/OS or LOCK/UNOCK with SCOPE=EXT rather than SCOPE=INT for VSE.
APPLSTS - Specify ‘Y’ or ‘F’ to support Applid Status Tracking (Section 2.1.3). If Applid Status DOWN record is present
in the BATSTAT file, then any errors MBCBATCH has trying to open the pipe are treated like DOWNSPC=B (bypassed)
for APPLSTS=Y or DOWNSPC=F (flushed) for APPLSTS=F. The default value ‘N’ does not allow SAPL command or
‘DOWN’ reply to a DOWNNON or DOWNSPC WTOR prompt.
LOGXDD - Specify 'Y' to allow or 'N' (DEFAULT) to not allow support for a SYSLSTX DD (z/OS) or ASSGN (VSE) for
separating additional output written to the log on return from QRYS, QRYL, CEDA, CDAL and CEMT commands. This
option can be overridden (OPTR), so only steps requiring output separation would require the extra DD. See Section 2.1.5.
EMTMSGS - Specify 'Q' to return additional output for only CEMT INQ commands or 'A' to return additional output on
all CEMT commands. See Section 2.1.5.
Security Options: - These options are related to MBC security.
EXTSEC - Specify ‘Y’ if you have an external security manager (ESM) active in your CICS regions or ‘N’ if you do not.
‘N’ is the default. Specifying ‘Y’ enables QUERY SECURITY on STAR commands, forces Status Tracking to START
sub-processor programs with the original Execution Userid of the command (Section 2.3.2), and for TCPIP users uses the
Execution Userid instead of the Listener Userid for running commands.
DOMSEC - Specify ‘Y’ if you want to require the CICS header card target Applid be defined in the Domain Applid record
of the current BATCNTL file or ‘N’ to not require a definition be present. ‘N’ is the default. If you use multiple
BATCNTL files (i.e. TEST and PROD) you can use this option in combination with Domain Applid records to prevent
sending commands intended for a TEST region to one of your Prod regions (Section 3.10).
CEMTPERF - Specify 'Y' to allow 'CEMT PERFORM...' commands as input to MBCBATCH or 'N' to not allow. Default
is 'N'. The 'CEMT PERFORM SHUT' command is disallowed regardless of this setting. You must use SHUT command.
See SHUTCMD installation option below.
SHUTCMD - Specify ‘Y’ to allow SHUT command input to MBCBATCH to initiate CICS shutdown. Specify ‘N’
(DEFAULT) to not allow SHUT command input. The shutdown tranid MBCQ is executed under the Execution Userid.
CEDACMD - Specify ‘Y’ (DEFAULT) to allow CEDA command input to MBCBATCH. Specify ‘N’ to not allow CEDA
command input.

Status Tracking Options: - These can be used to control the operation of the optional Status Tracking feature.
STATFLAG - Specify ‘Y’ to enable Status Tracking or ‘N’ to not use the Status Tracking feature. Default value is ‘N’. If
‘Y’ is specified, you must add a BATSTAT DD or DLBL to your MBCBATCH execution JCL. See Section 7 for details.
STATRTRY - Number of times to retry opening file BATSTAT if the open fails due to the file being in use by another job.
There is a 3-second delay between attempts. The default value is 2 retry attempts (6 seconds wait time).
ERRSTS - Default LASTCC value (0-255) used when an error occurs in Status Tracking processing. Default is 0.
WARNING! Changing to a non-zero value may prevent your batch jobs from executing even when there may be no
errors in the execution phase (i.e. all files were successfully closed).
STRTUPMG - Specify ‘Y” to activate Startup Manager to use Resource Item settings to determine CICS Startup allocation
preferences. (STATFLAG must = 'Y'). Specify ‘N’ (default) to not use the Startup Manager.
TRKNONFI - Specify ‘Y’ to track non-file activity; programs, transactions, TCPIP services and TDQs. Specify ‘N’
(default) to only track File activity.
3.4.1 Installation Options via Batch

Batch utility MBCBCUTL allows you to list and initialize MBC Installation Options. The INIT Functions require
exclusive access to the BATCNTL (file must not be open for Update in any CICS region). Sample JCL is in source
member MBCJCUTL. The format of the option-related control cards are listed below. Multiple cards can be input in the
same job
See Section 4.2.1 for a full description of MBCBCUTL functions.
LIST OPTS List installation options report

INIT OPTS Initialize options to default values if Option record does not already exist
INIT {option}({value}) See Section 3.4 for option names and acceptable values (see NOTE below)
Example cards:
INIT ERRWARN(000)
INIT STATRTRY(001)
INIT EXTSEC(Y)
LIST OPTS

3.4.2 Online APPLID Number/Name Screen
The CICS APPLID Number/Name Definition screen displays when pressing PF8/20 on the Installation Options screen.
This screen is supplied for compatibility mode with the CEMT from Batch product (Appendix E) for users who may have
CEMT from Batch JCL using numbers for the CICS header card or who may be using an override number
(HDROVER=Y) in column 80 or 72. It is recommended new MBC users do NOT use this option and instead use an
Applid header or Applid Groups (see CICS command description in Section 5.2).
TIP! The APPLID values can be copied over to Domain Security records by using the PF9/PF21 function.
MBCMAPL MacKinney Batch to CICS 05/22/20 11:15:36

Mode: CICS APPLID Number/Name Definition Applid: DBDCICSA
01 DBDCCICS 02 CICSTEST 03 04 05 06
07 08 09 10 11 12
13 14 15 16 17 18
19 20 21 22 23 24
25 26 27 28 29 30
31 32 33 34 35 36
37 38 39 40 41 42
43 44 45 46 47 48
49 50 51 52 53 54
55 56 57 58 59 60
61 62 63 64 65 66
67 68 69 70 71 72
73 74 75 76 77 78
79 80 81 82 83 84
85 86 87 88 89 90
91 92 93 94 95 96
97 98 99
Above Applids used for CICS header cards with numbers and Col 72/80 overrides
PF9 to copy to Domain Applids which can be used to limit CICS target selection
Enter=Update PF7=Options PF9=Copy To Domain
To update values on this screen, add or overtype the APPLID corresponding to the APPLID Number you wish to change,
then press ENTER to update the BATCNTL file. Press PF7/PF19 to return to Installation Options screen 1. Press
PF9/PF21 to copy Applids to Domain Applid Records (Section 3.10).
Applid values must be left-justified. To remove an Applid from the list, space out the APPLID value you wish to remove.

3.5 Display PTFs and Level Set
Selecting option 2 on the Administration Menu shows the PTFs applied to MacKinney Batch to CICS plus the product base
Level Set. The Level Set is modified when you do a complete refresh update from our web-site (www.mackinney.com).
MBCMPTF MacKinney Batch to CICS 01/10/20 11:07:26

Level Set: xx01 List of PTFs Installed Applid: DBDCICSA
001 ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___
Hit any key to RETURN
This screen is display–only and cannot be updated. Press any key to return to the Administration Menu.
3.5.1 Level Set via Batch

In addition to viewing the PTF Level Set via administration, the Level Set is displayed on the first line of the batch
job log as follows:
MACKINNEY BATCH TO CICS RELEASE x.x LEVEL SET(nn) <==== nn – level set
OPTIONS IN EFFECT FOR THIS STEP
OPTS: PREFIX (MBC) CMDEXIT (N) CLOSDIS(Y) CLOSRQST(N) TDMESGQ (CSMT)
OPTS: ERRWARN(000) LOADPGM (N) HDROVER(N) COLUMN80(Y) SHUTTERM( )
OPTS: ERRDOWN(004) DOWNNON (F) DOWNSPC(F) APPLSTS (N) CLOSRTRY(002)
OPTS: ERRDRLS(006) FAILACT (G) LOGXDD (Y) EMTMSGS (A) CEMTRTRY(001)
OPTS: ERRCMD (008) EXTSEC (Y) DOMSEC (N) CEMTPERF(N) STATRTRY(001)
OPTS: ERRSEC (012) STATFLAG(Y) SHUTCMD(N) STRTUPMG(Y) TRKNONFI(Y)
OPTS: ERRCNCL(016) CEDACMD (Y) ENQXS (N) RLUPDIS (N) IPVERS (N)
OPTS: ERRSTS (000)
MBCB001-MBCBATCH x.x STARTING JOB(JOB12345:MBC$RUN) USER(RJS2)
MBCB003-COMMAND PRE-PROCESSING STARTING
MBCB004-COMMAND EXECUTION PHASE STARTING USING EXCI
CICS T540 <HDR
...
MBCB002-MACKINNEY BATCH TO CICS x.x ENDING MAXCC(000)

3.6 Applid Groups (ApplGrps)
Applid Groups (ApplGrps) allow MBCBATCH command(s) to route to multiple Applids using a single CICS header card. Up
to 999 Applids can be defined in a single ApplGrp record. ApplGrps are also used for RLS processing by using the RLS1GRP
parameter in the CICS header card. When the RLS1GRP parameter is used, command(s) are routed to the first successfully
connected Applid in the group so following RLS command(s) are propagated only once (see RLSQ/RLSU and GLSQ/GLSU
in Section 5.1).
You can also use Applid Groups for indirect referencing. For example is you have an ApplGrp, DEVCICS and you want to
change the name of the Applid defined in DEVCICS, simply update the Applid Group record modifying the Applid value in
the record without the need to modify your JCL.
You can update Applid Groups via the Administration Menu Option 3, using the batch utility MBCBAGRP (Section 3.6.5) or
by entering fast-path transaction (MBCL). The following sections discuss the creation and modification of Applid Groups.
3.6.1 Defining ApplGrps to Use With Shared Resources

You can use specially named ApplGrps to identify regions that share common Resource Items and Resource Groups. Specify
an ApplGrp name beginning with ‘@’ and with a length of no more than 8 characters (i.e. @APGRP01) to use ApplGrps in
combination with Resource Groups and shared Resource Items,. This @ApplGrp name must be specified as the target Applid
(GrpAppl) value for the Resource Group definition (see example in Section 3.8.1.1) and as the Applid value for shared
Resource Item defintions (see Section 3.7.3). See additional information on shared and non-shared Resource Items (Section
3.7.1) and Resource Groups (Section 3.8.1).
3.6.2 ApplGrp Directory Screen – MBCL

All administration of ApplGrps is done through the ApplGrp Directory screen. Display the screen by entering fast-path Tranid
MBCL or selecting option 3 from the Administration Menu.
MBCMAGD MacKinney Batch to CICS 01/10/20 14:09:08

Mode: UPDATE ApplGrp Directory Applid: DBDCICSA
Enter E-edit C-copy D-del or V-view selected group
*___________ <-Filter
S ApplGrp Description Upd User Upd Date-Time
@AGRP1 APPL GROUP FOR RESOURCE GRPS CICSUSER 01/10/20 10:18
PRODACCTING PROD ACCOUNTING GROUP CICSUSER 10/25/19 13:05
PRODHUMRES PROD HUMAN RESOURCES GROUP CICSUSER 10/25/19 14:19
TESTHUMRES TEST HUMAN RESOURCES GROUP CICSUSER 10/25/19 14:19
TESTPGMRS TEST PROGRAMMERS GROUP CICSUSER 11/29/19 15:50
ENTER=Process PF1=Help PF3=End PF6=Add PF7=Bwd PF8=Fwd
Press PF6/PF18 to add a new ApplGrp, PF8/PF20 to scroll forward, PF7/PF19 to scroll backward or PF3/PF15 to return back
to the previous screen. Each entry may be selected for Edit, Copy, Delete or View by entering an ‘E’, ‘C’, ‘D’, or ‘V’ in the S
column before the entry.

3.6.3 ApplGrp Update Screen
The ApplGrp Update screen allows you to enter up to 999 Applids for a Group. Specify up to 999 Applids for the group. Press
PF3 to save.
MBCMAGU MacKinney Batch to CICS 01/10/20 14:10:51

Mode: UPDATE ApplGrp Update Applid: DBDCICSA
ApplGrp: PRODACCTING Desc: PROD ACCOUNTING GROUP
Enter unique APPLID entry(s) for Group or blank to remove. PF9 for RESEQ mode
001 DBDCCICS 002 DBDCICS2 003 DBDCICS3 004 005
006 007 008 009 010
011 012 013 014 015
016 017 018 019 020
021 022 023 024 025
026 027 028 029 030
031 032 033 034 035
036 037 038 039 040
041 042 043 044 045
046 047 048 049 050
051 052 053 054 055
056 057 058 059 060
061 062 063 064 065
066 067 068 069 070
071 072 073 074 075
076 077 078 079 080
Enter=Process PF1=Help PF3=Save PF7=Bwd PF8=Fwd PF9=ReSeq PF12=Cancel
Press PF8/PF20 to scroll forward, PF7/PF19 to scroll backward, PF9/PF21 to toggle the display between RESEQ and
UPDATE modes, PF3/PF15 to Save changes or PF12/PF24 to Cancel changes and return to the previous screen. To remove
an entry, blank out the value of the entry you wish to remove. An example of RESEQ (PF9) mode is shown on the following
page.
ApplGrp – Displays unique name identifying the ApplGrp. If you intend to use this ApplGrp for identifying the owing
Applids for shared Resource Items and Resource Groups, then this name must begin with an ‘@’ and be limited to 8-
characters in length.
Desc – Displays description to help further identify the ApplGrp.
Specify unique APPLID values in slots 001 through 999.

To re-sequence the Applids press the PF9 key and the number field changes to unprotected while the Applids fields are
protected. Overtype the number fields to place the Applids in the desired order and press ENTER to process. For example, to
move DBDCCICS after DBDCICS3, overtype 0010 with 0035.

Mode: RESEQ ApplGrp Update Applid: DBDCICSA
Enter new sequence number and press Enter to resequence. PF9 for UPDATE mode
0035 DBDCCICS 0020 DBDCICS2 0030 DBDCICS3 0040 0050
0060 0070 0080 0090 0100
0110 0120 0130 0140 0100
0160 0170 0180 0190 0200
0210 0220 0230 0240 0250
0260 0270 0280 0290 0300
0310 0320 0330 0340 0350
0360 0370 0380 0390 0400
0410 0420 0430 0440 0450
0460 0470 0480 0490 0500
0510 0520 0530 0540 0550
0560 0570 0580 0590 0600
0610 0620 0630 0640 0650
0660 0670 0680 0690 0700
0710 0720 0730 0740 0750
0760 0770 0780 0790 0800
Enter=Process PF1=Help PF3=Save PF7=Bwd PF8=Fwd PF9=Reseq PF12=Cancel
After pressing ENTER, the new order displays. Press PF9 to toggle back to UPDATE mode where you can continue adding
Applids. If more than 80 Applids are needed, use PF8 and PF7 to scroll forward and backward to work with additional
entries.

0010 DBDCICS2 0020 DBDCICS3 0030 DBDCCICS 0040 0050
0060 0070 0080 0090 0100
0110 0120 0130 0140 0100
0160 0170 0180 0190 0200
0210 0220 0230 0240 0250
0260 0270 0280 0290 0300
0310 0320 0330 0340 0350
0360 0370 0380 0390 0400
0410 0420 0430 0440 0450
0460 0470 0480 0490 0500
0510 0520 0530 0540 0550
0560 0570 0580 0590 0600
0610 0620 0630 0640 0650
0660 0670 0680 0690 0700
0710 0720 0730 0740 0750
0760 0770 0780 0790 0800
Press PF3 to save your changes and return back to the ApplGrp Directory screen or press PF12 to cancel your changes.

3.6.4 ApplGrp Copy Screen
From the ApplGrp Directory screen, enter a ‘C’ in the S column to copy one group to another. For example, copy
PRODACCTING group to another group.

*___________ <-Filter
S Group Description Upd User Upd Date-Time
C PRODACCTING PROD ACCOUNTING GROUP CICSUSER 10/25/19 13:05
The ApplGrp Copy screen allows you to copy from a selected source group to target group(s). Below is an example copying
group PRODACCTING to group TESTACCTING. After filling in the fields Target Group, Target Desc fields and pressing
ENTER you see the following:
MBCMAGC MacKinney Batch to CICS 01/10/20 14:45:09

Mode: COPY ApplGrp Copy Applid: DBDCICSA
Fill in Target fields and press ENTER to copy. Press PF3 when done.
Source Group: PRODACCTING Source Applid group name
Source Desc: PROD ACCOUNTING GROUP Source group desc
Target Group: TESTACCTING Specify target Applid group name for copy
Target Desc: PROD ACCOUNTING GROUP Specify target group desc
ENTER=Copy PF1=Help PF3=End

MBCE356-GROUP TESTACCTING HAS BEEN ADDED BY USER CICSUSER
Press ENTER to copy the group or PF3/PF15 to end back to the previous screen (does not process the copy).
Pressing PF3 returns to the ApplGrp Directory screen where you see the newly added ApplGrp.

*___________ <-Filter
S Group Description Upd User Upd Date-Time
PRODACCTING PROD ACCOUNTING GROUP CICSUSER 10/25/19 13:05
TESTACCTING TEST ACCOUNTING GROUP CICSUSER 10/25/19 14:25

3.6.5 ApplGrp Via Batch (MBCBAGRP)
Batch utility MBCBAGRP allows you to list, delete and define Applid group records in the BATNCTL file. Updating group
resources using MBCBAGRP requires update access to the BATCNTL file (file must not be open for update in any CICS
region). Sample JCL is in source member MBCJAGRP. The format of the column specific control cards are listed below.
Multiple cards can be input in the same job.
column 8 21
DEFAGP nnnnnnnnnnnn description

DEFAPL aaaaaaaa
DELAGP nnnnnnnnnnnn
DELALL
LSTAGP nnnnnnnnnnnn
LSTALL
USEPCH
DEFAGP – define an Applid Group (ApplGrp) name. A DEFGRP card must come before DEFAPL card(s)
DEFAPL – define an Applid entry. DEFAPL card(s) must follow a DEFAGP card
DELAGP – delete target Applids for a specific group name
DELALL – delete all ApplGrps
LSTAGP – list target Applids for a specific group name
LSTALL – list all ApplGrps
USEPCH - creates DEF* cards from LSTAGP and LSTALL options in SYSPCH DD or DLBL (see TIP! Below)
nnnnnnnnnnnn – Applid group name

description – group description (up to 30-bytes) and must begin in col 21
aaaaaaaa – Applid aaaaaaaa to use as a target
TIP! You can use the LSTAGP and LSTALL functions to create a batch backup. Copy and paste the LSTAGP and
LSTAPL lines created on the report output, perform a “change all LST prefix to DEF prefix” or use USEPCH option. Then
use the altered cards or SYSPCH file as input to for DEFAGP and DEFAPL entries.
Example 1: Define Resource Groups BATCHGROUP1 and BATCHGROUP2 with multiple items in each group.
LSTAGP TESTREGIONS
DELAGP TESTREGIONS
DEFAGP TESTREGIONS MBC TARGET TEST REGIONS
DEFAPL T520
DEFAPL T530
DEFAPL DBDCICSA
DEFAGP PRODREGIONS MBC TARGET PROD REGIONS
DEFAPL P520
DEFAPL P530
DEFAPL P540
MACKINNEY BATCH TO CICS - REL x.x PAGE 1

DSN:MACS.MBC.BATCNTL BATCNTL APPLID GROUP UTILITY 10/25/2019
LSTAGP TESTREGIONS <OK

LSTAPL T420
LSTAPL T510
2 APPLIDS LISTED FOR APPLGRP(TESTREGIONS )
DELAGP TESTREGIONS <OK

2 APPLIDS DELETED FOR APPLGRP(TESTREGIONS )
DEFAGP TESTREGIONS MBC TARGET TEST REGIONS <OK

DEFAPL T520 <ADD
DEFAPL T530 <ADD
DEFAPL DBDCICSA <ADD
3 APPLIDS ADDED FOR APPLGRP(TESTREGIONS )
DEFAGP PRODREGIONS MBC TARGET PROD REGIONS <OK

DEFAPL P520 <ADD
DEFAPL P530 <ADD
DEFAPL P540 <ADD
3 APPLIDS ADDED FOR APPLGRP(PRODREGIONS )
BATCNTL APPLID GROUP UTILITY ENDING MAXCC(000)

3.7 Resource Items
Resource Items allow you to define information about a CICS resource for use by MBC in processing the item as an
individual Resource, member of a Resource Groups or for use with the Startup Manager. Supported resources include files
(FI), programs (PG), transactions (TR), TCPIP services (IP), non-Extrapartition TDQs (TD), and Extrapartition TDQs (TX -
z/OS only). Use MBC Commands ALOR, ALSR, UNAR and their corresponding group commands (ALOG, ALSG, UNAG)
with Resource Items. You can update Resource Items via the Administration Menu Option 4, using the batch utility
MBCBRITM (Section 3.7.4) or by entering the fast-path transaction MBCI.
3.7.1 Shared and Non-Shared Resource Items

Even though you may have resources common to several regions (i.e. file names), for MBC purposes, they are usually defined
as a non-shared Resource Item with the definition for each region having a different DSN or other unique attributes. These
non-shared resources are owned by the Applid identified in the Resource Item definition.
MBC also supports shared Resource Items for sharing amongst several regions. Each of the shared Resource Items are defined
once and are identified as a shared resource by specifying an @ApplGrp name for the Resource Item Applid value.
3.7.2 Resource Item Directory Screen – MBCI

Enter transaction MBCI or select option 4 from the Administration Menu to display the Resource Item Directory as shown.
MBCMRID MacKinney Batch to CICS 07/25/20 13:35:40

Mode: UPDATE Resource Item Directory Applid: DBDCICSA
Enter E-edt C-cpy D-del G-grps S-sts V-view A-alo ds1 2-alo ds2 U-unal resource
*_______ *_ *_______ * *_____________________________ <-Filters
S Applid Resource S Primary DSN1
DBDCICSA FI BATCNTL S MACS.MBC.BATCNTL
DBDCICSA FI BATCSTS MACS.T540.BATCSTS
DBDCICSA FI BATSTAT MACS.MBC.BATSTAT
DBDCICSA FI SMGFILE S MACS.SMGFILE
DBDCICSA PG SMGPADM
DBDCICSA TD CADO
DBDCICSA TD CDB2
DBDCICSA TD CEJL
DBDCICSA TD CPLI
ENTER=Process PF1=Help PF3=End PF6=Add PF7=Bwd PF8=Fwd PF9=Toggle DSN
Press PF6/PF18 to add a new item (Section 3.7.3), PF8/PF20 to scroll forward, PF7/PF19 to scroll backward or PF3/PF15 to
return back to the previous screen. Press PF9/PF21 to change the column header from ‘Primary DSN1’ to ‘Secondary DSN2’.
For TYPE=FI entries, if there is no Secondary DSN2 value, the Primary DSN1 value displays in Yellow. Enter Applid,
Resource, Secondary DSN indicator (‘S’), and DSN filter values to display only records matching the filters.
S – Use one of the following selection codes in the initial S column (before the entry):
Enter ‘E’ to edit the item definition values on the Resource Item Update screen (Section 3.7.3)
Enter ‘C’ to copy the item definition values to another item (Section 3.7.3)
Enter ‘D’ to delete the item
Enter ‘G’ to display all groups where the selected item belongs via the Resource/Group XREF screen (Section 3.7.5)
Enter ‘S’ to display the item status value.
Enter ‘V’ to display the item. These are the allocation values used when the resource is allocated with the ALOR command.
Enter ‘A’ to allocate/enable the item. For Type ‘FI’ items, the item DSN1 value is used for allocation.
Enter ‘2’ to allocate/enable the item. For Type ‘FI’ items, the item DSN2 value is used in the allocation, unless DSN2 is
blank, in which case the DSN1 value is used.
Enter ‘U’ to unallocate/disable the item
Applid – displays the Applid for the Item resource or an @ApplGrp name if this is a shared resource owned by an @ApplGrp.
Resource – displays the Resource Type and Resource Name of the Item.
S – an ‘S’ indicates the presence of a non-blank Secondary DSN value (DSN2) and a blank indicates no Secondary DSN
value (DSN2) is present.
DSN – Displays Primary DSN1 or Secondary DSN2 for Type ‘FI’ Resource Items (PF9/PF21 to toggle)
If Startup Manager option STRTUPMG=Y, the Resource Item Directory screen has additional column headers for ALO and
OPE preferences as shown below.

*_______ *_ *_______ * *_____________________________ <-Filters ALO OPE
S Applid Resource S Primary DSN1 C A CAO
DBDCICSA FI BATCNTL S MACS.MBC.BATCNTL P L LLY
DBDCICSA FI BATCSTS MACS.T540.BATCSTS P L LLY
DBDCICSA FI BATSTAT MACS.MBC.BATSTAT P L LLY
DBDCICSA FI SMGFILE S MACS.SMGFILE P P UUN
DBDCICSA PG SMGPADM Y Y
DBDCICSA TD CADO Y Y
DBDCICSA TD CCVX Y Y
DBDCICSA TD CDB2 Y Y
DBDCICSA TD CEJL Y Y
DBDCICSA TD CPLI Y Y
ALO - displays the “Startup Aloc” Resource Item Update screen values for the resource.
C column – display Cold (or Initial) start value (P|N|L for files; Y|N for non-file resources). For files: P allocates file
with Primary DSN value; N does not allocate file; and L allocates file with the last-known DSN value in
the BATCSTS file. For non-file resources: Y enables the resource and N disables the resource.
A column display Auto start value (P|N|L for files; Y|N for non-file resources). Values are same as described in the
C column above.
OPE – displays the “Open on Aloc” Resource Item Update screen values for file resources.
C column – display Cold (or Initial) start value (I|U|N|L for files; Y|N for extra-partition TDQ). For files: I opens the
file for Inquiry mode after an allocate; U opens the file for Update mode after an allocate; N keeps the file
closed but enabled after an allocate; and L keeps the file attributes the same as the last-known status in the
BATCSTS file. For extra-partition TDQs; Y opens the TDQ and N keeps the TDQ closed but enabled after
an allocate.
A column display Auto start value (I|U|N|L). Values are same as described in the C column above.
O column display “Open on Aloc” value for non-startup file (FI) and extra-partition TDQ (TX) resource allocations
(Y|N). Y opens the file and N leaves the file closed but enabled after an allocate.

3.7.3 Resource Item Update Screen
The Resource Item Update Screen allows you to add or change Resource Items. Enter the Applid, Resource Type and Resource
Name, then press Enter and the screen displays additional options depending on the Resource Type. This screen is displayed when
you press PF6/PF18 or by selecting a Resource Item with a ‘V’ or ‘E’ on the Resource Item Directory screen
MBCMRIE MacKinney Batch to CICS 07/25/20 13:40:59

Mode: ADD Resource Item Update Applid: DBDCICSA
Fill in fields and press ENTER for additional options or PF3 to cancel
Resource Applid: DBDCICSA Specify Resource Applid

Resource Type: FI FI-Fil|PG-Pgm|TR-Trn|TD-TDQ|TX-Ext TDQ|IP-IPSvc
Resource Name: NEWFILE Specify CICS Resource Name
ENTER=Opts PF1=Help PF3=End
Press Enter to display additional options depending on the Resource Type, PF1/PF13 for help, or Press PF3/PF15 to return to
previous screen with no changes.
Resource Applid - serves to limit the scope of the Resource Item to the specified Applid. Specify an @ApplGrp name if this is
a shared resource owned by an @ApplGrp.
Resource Type – specify the type of resource to define: FI-File | PG-Program | TR-Transaction | TD-TDQ | TX –
Extrapartition TDQ (z/OS only) | IP-TCPIP Service.
Resource Name – specify the name of the resource (no wildcards). This name much match the resource name as defined in the
CICS CSD for the specified Resource Applid.

3.7.3.1 Resource Items (FI)
The following options are available for Resource Type=FI items.

Fill in options and press ENTER to add or PF3 when done with adds

Resource Type: FI FI-Fil|PG-Pgm|TR-Trn|TD-TDQ|TX-Ext TDQ|IP-IPSvc
Resource Name: NEWFILE Specify CICS Resource Name
Resource Options
Open on Aloc: Y (Y/N) Open after non-startup allocation
File Disp: S (S-Shr|O-Old)
File in JCL: N (Y/N)
Primary DSN1: MY.NEWFILE.PRIM
Secondary DSN2: MY.NEWFILE.SEC
Startup Manager Options

Startup Aloc Cold: P (P/N/L) Auto: L (Primdsn/No/Lastdsn)
Open on Aloc Cold: L (I/U/L/N) Auto: L (Inqy/Updt/Last/No)
ENTER=Add PF1=Help PF3=End
Press Enter to add, PF1/PF13 for help, or Press PF3/PF15 to return to previous screen with no changes.
Resource Options
Open on Aloc – specify Y to open file or N to not open file after the file is allocated with MBC (ALO* command or Item or
Group allocate Operation).
File Disp – specify file disposition value S-Shr or O-Old to use for allocation.
File in JCL – specify Y if the file is defined in the CICS Startup JCL or N if the file is defined in the CSD. If Y is specified,
the file is allocated (and unallocated) using SVC 99 rather than using the preferred Transaction Server dynamic allocation
method.
Primary DSN1 – specify the primary dataset name to use for allocation (ALOC/ALOR/ALOG) and unallocation
(UNAL/UNAR/UNAG). The primary DSN1 is also used for Item or Group allocations where ‘A’ is specified.
Secondary DSN2 – specify the secondary dataset name (DSN2) to use for allocation (ALSR/ALSG). The secondary DSN2 is
also used for Item or Group allocations where ‘2’ is specified. If DSN2 value is blank, then DSN1 value is substituted.
Startup Manager Options (only appear if Status Tracking Option STRTUPMG=Y)
Startup Aloc Cold – specify P (default) to allocate file with Primary DSN1, N to not allocate file, or L to use the Last file
allocation status and DSN found in the BATCSTS file when Cold or Initial start was specified in the MBCBCPRE pre-CICS
startup step. NOTE: If L is specified and there is no previous status record found, then P is assumed.
Startup Aloc Auto – specify P to allocate file with Primary DSN1, N to not allocate file, or L (default) to use the Last file
allocation status and DSN found in the BATCSTS file when Auto start was specified in the MBCBCPRE pre-CICS startup step.
NOTE: If L is specified and there is no previous status record found, then P is assumed.
Open on Aloc – specify Y to open, I to open INQY, U to open UPDT, L (default) to use last open status, or N to not open file
after the file is allocated using MBC. Specify a value for each type of startup (Cold/Auto). Values are used in the
MBCBCPRE pre-CICS startup step to flag whether the file should be opened after it is allocated. NOTE: If L is specified
and there is no previous status record found, then status defaults to OPEN for allocate and CLOSED for unallocate.

3.7.3.2 Resource Items (PG)
The following options are available for Resource Type=PG items.


Resource Type: PG FI-Fil|PG-Pgm|TR-Trn|TD-TDQ|TX-Ext TDQ|IP-IPSvc
Resource Name: NEWPROG Specify CICS Resource Name

Startup Ena Cold: Y (Y/N) Auto: Y (Y/N)
Resource Options
There are no resource options for programs, so this section does not appear.
Startup Ena – specify Y (default) to enable program or N to not enable program at CICS startup. Specify a value for each type
of startup (Cold/Auto). Values are used in the MBCBCPRE pre-CICS startup step to determine whether the program should
be enabled.

3.7.3.3 Resource Items (TR)
The following options are available for Resource Type=TR items.


Resource Type: TR FI-Fil|PG-Pgm|TR-Trn|TD-TDQ|TX-Ext TDQ|IP-IPSvc
Resource Name: TRAN Specify CICS Resource Name

Resource Options
There are no resource options for transactions, so this section does not appear.
Startup Ena – specify Y (default) to enable transaction or N to not enable transaction at CICS startup. Specify a value for each
type of startup (Cold/Auto). Values are used in the MBCBCPRE pre-CICS startup step to flag whether the transaction should
be enabled.

3.7.3.4 Resource Items (IP)
The following options are available for Resource Type=IP items.


Resource Type: IP FI-Fil|PG-Pgm|TR-Trn|TD-TDQ|TX-Ext TDQ|IP-IPSvc
Resource Name: HTTPNSSL Specify CICS Resource Name

Startup Ope Cold: Y (Y/N) Auto: Y (Y/N)
Resource Options
There are no resource options for TCPIP services, so this section does not appear.
Startup Ope – specify Y (default) to open or N to not open TCPIP service at CICS startup. Specify a value for each type of
startup (Cold/Auto). Values are used in the MBCBCPRE pre-CICS startup step to flag whether the TCPIP service should be
opened (allocated).

3.7.3.5 Resource Items (TD)
The following options are available for Resource Type=TD items.


Resource Type: TD FI-Fil|PG-Pgm|TR-Trn|TD-TDQ|TX-Ext TDQ|IP-IPSvc
Resource Name: TDQN Specify CICS Resource Name

Resource Options
There are no resource options for TDQs, so this section does not appear.
Startup Ena – specify Y (default) to enable TDQ or N to not enable TDQ at CICS startup. Specify a value for each type of
startup (Cold/Auto). Values are used in the MBCBCPRE pre-CICS startup step to flag whether the TDQ should be enabled.

3.7.3.6 Resource Items (TX)
The following options are available for Resource Type=TX items (z/OS only).


Resource Type: TX FI-Fil|PG-Pgm|TR-Trn|TD-TDQ|TX-Ext TDQ|IP-IPSvc
Resource Name: TDQX Specify CICS Resource Name
Resource Options
Open on Aloc: Y (Y/N) Open after non-startup allocation
File Disp: S (S-Shr|O-Old|M-Mod)
SVC99 Aloc: Y (Y forced for TX) TX DDNAME: TDQXDDN
Primary DSN1: MY.NEWFILE.PRIM

Startup Aloc Cold: Y (Y/N) Auto: Y (Y/N)
Open on Aloc Cold: Y (Y/N) Auto: Y (Y/N)
Resource Options
Open on Aloc – specify Y to open or N to not open Extrapartition TDQ after the TDQ is allocated with MBC (ALO*
command or Item or Group allocate Operation).
File Disp – specify TDQ disposition value S-Shr, O-Old, or M-Mod to use for allocation. Value ignored for VSE.
SVC99 Aloc – Y is forced for resource type TX. The SVC99 method of allocation is currently the only supported allocation
method for Extrapartition TDQs. Value ignored for VSE.
TX DDNAME – specify the DDNAME for the Extrapartition TDQ. Value ignored for VSE.
Primary DSN1 – specify the dataset name, DUMMY or leave blank for SYSOUT to use for allocation and unallocation.
Value ignored for VSE.
Startup Aloc Cold – specify Y (default) to allocate file with Primary DSN1 or N to not allocate file when Cold or Initial start
was specified in the MBCBCPRE pre-CICS startup step.
Startup Aloc Auto – specify Y (default) to allocate file with Primary DSN1 or N to not allocate file when Auto start was
specified in the MBCBCPRE pre-CICS startup step.
Open on Aloc – specify Y (default) to open file or N to not open file after the file is allocated using MBC. Specify a value for
each type of startup (Cold/Auto). Values are used in the MBCBCPRE pre-CICS startup step to flag whether the file should be
opened after it is allocated.

3.7.4 Resource Item Update via Batch (MBCBRITM)
Batch utility MBCBRITM allows you to list, delete and define Resource Item records in the BATNCTL file. Updating
resources using MBCBAGRP requires update access to the BATCNTL file (file must not be open for update in any CICS
region). Sample JCL is in source member MBCJRITM. The format of the column specific control cards are listed below.
Multiple cards can be input in the same job.
column 8 11 20
DEFITM tt rrrrrrrr aaaaaaaa {For all Type resources}

DEFITA FI rrrrrrrr ALO(ca) OPE(cao) DSP(d) JCL(j) {Type=FI resource}
DEFITA TX rrrr ALO(ca) OPE(cao) DSP(d) DDN=ddnvalue {Type=TX resource; z/OS only}
DEFITA tt rrrrrrrr ALO(ca) {Type=PG/TR/TD/IP resource}
DEFITP tt rrrrrrrr DSN1=dsnvalue ... 44 ... dsnvalue {Type=FI/TX only}
DEFITS FI rrrrrrrr DSN2=dsnvalue ... 44 ... dsnvalue {Type=FI only}
DELITM tt rrrrrrrr aaaaaaaa
DELALL aaaaaaaa | ‘ALL’
LSTITM tt rrrrrrrr aaaaaaaa
LSTALL aaaaaaaa | ‘ALL’
USEPCH
DEFITM – define a Resource Item record. A DEFITM is joined with DEFITA, DEFITP and DEFITS cards to build a record.
DEFITA – DEFITA card must follow a DEFITM card and determines various Resource Item options
DEFITP – DEFITP card must follow a DEFITA card and determines Primary DSN value for Resource Item (Type FI/TX only)
DEFITS – DEFITS card must follow a DEFITP card and determines Secondary DSN value for Resource Item (Type FI only)
DELITM – delete Resource Item record for a specific Resource and Applid
DELALL – delete all Resource Items for a specific Applid or ‘All’ Applids
LSTITM – list Resource Item record values for a specific Resource and Applid
LSTALL – list all Resource Items for a specific Applid or ‘All’ Applids
USEPCH - creates DEF* cards from LSTITM and LSTALL options in SYSPCH DD or DLBL (see TIP! Below)
aaaaaaaa – Identifies Applid aaaaaaaa owning the Item. Can be an @ApplGrp if the Item is a shared resource owned by an
@ApplGrp.
tt – Resource Type (tt = FI-file|PG-program|TR-tranid|TD-TDQ|TX-Ext TDQ|IP-TCPIP service) and begins in col 8.
rrrrrrrr – 8-character (FI|PG) or 4-character (TR|TD|TX – blank filled) Resource Name and begins in col 11.
Type=FI
ALO(ca) – startup allocation preferences for COLD (P/N/L) and AUTO(P/N/L) startups. Value must begin in col 24. Specify
P to allocate resource with Primary DSN, N to not allocate resource or L to use the last allocate status and DSN value
saved in BATCSTS. Value is not used unless STSFLAG=Y and STRTUPMG=Y.
OPE(cao) – open preferences for COLD and AUTO startups (Y/I/U/L/N) plus “Open After Allocate” (Y/N) preference for
online allocations. Value must begin in column 32. Specify Y to open file, I to open file INQY, U to open file UPDT, L to
use the last open status saved in BATCSTS or N to not open file. Value is not used unless STSFLAG=Y and
STRTUPMG=Y.
DSP(d) – specify file disposition S-SHR or O-OLD. Disposition value must be in column 41.
JCL(j) – specify Y if file is specified in CICS startup JCL or N if not. If Y is specified, the SVC99 routine is used for
allocation and unallocation of file. Disposition value must be in column 48.
dsnvalue - specify the primary DSN1 or secondary DSN2 value. DSN value must be in column 25 of DEFITP/DEFITS cards.
Type=TX (z/OS only)

ALO(ca) – startup allocation preferences for COLD (Y/N) and AUTO(Y/N) startups. Value must begin in col 24. Specify Y to
allocate resource or N to not allocate resource at startup. Value is not used unless STSFLAG=Y and STRTUPMG=Y.
OPE(cao) – open preferences for COLD and AUTO startups plus “Open After Allocate” preference for online allocations.
Value must begin in column 32. Specify Y to open file or N to not open file. Value is not used unless STSFLAG=Y and
STRTUPMG=Y.
DSP(d) – specify file disposition S-SHR, O-OLD or M-MOD. Disposition value must be in column 41.
DDN=ddnvalue – specify DD name value for TDQ. Disposition value must be in column 48.
dsnvalue - specify the primary DSN1 value. DSN value must be in column 25 of DEFITP cards. Secondary DSN values are
not supported for TYPE=TX resources.
Type=PG/TR/TD
ALO(ca) – startup enable preferences for COLD (Y/N) and AUTO(Y/N) startups. Value must begin in col 24. Specify Y to
enable resource or N to disable resource at startup. Value is not used unless STSFLAG=Y and STRTUPMG=Y.
Type=IP
ALO(ca) – startup open preferences for COLD (Y/N) and AUTO(Y/N) startups. Value must begin in col 24. Specify Y to
open resource or N to close resource at startup. Value is not used unless STSFLAG=Y and STRTUPMG=Y.

TIP! You can use the LSTITM and LSTALL functions to create a batch backup. Copy and paste the LSTITM and
LSTALL lines created on the report output, perform a “change all LST prefix to DEF prefix” or use USEPCH option. Then
use the altered cards or SYSPCH file as input for DEFITM, DEFITA, DEFITP and DEFITS entries.
Example 1: Define Resource Items in Applid DBDCICSA for program SMGPADM, transaction SMGA, and file
SMGFILE
DEFITM PG SMGPADM DBDCICSA
DEFITA PG SMGPADM ALO(YY)
DEFITM TR SMGA DBDCICSA
DEFITA TR SMGA ALO(YY)
DEFITM FI SMGFILE DBDCICSA
DEFITA FI SMGFILE ALO(PL) OPE(LLY) DSP(S) JCL(N)
DEFITP FI SMGFILE DSN1=MACS.SMGFILE

DSN:MACS.MBC.BATCNTL BATCNTL RESOURCE ITEM UTILITY 10/25/2019
DEFITM PG SMGPADM DBDCICSA <OK

DEFITA PG SMGPADM ALO(YY) <OK
1 RECORD(S) DEFINED
DEFITM TR SMGA DBDCICSA <OK

DEFITA TR SMGA ALO(YY) <OK
1 RECORD(S) DEFINED
DEFITM FI SMGFILE DBDCICSA <OK

DEFITA FI SMGFILE ALO(PL) OPE(LLY) DSP(S) JCL(N) <OK
DEFITP FI SMGFILE DSN1=MACS.SMGFILE <OK
1 RECORD(S) DEFINED
BATCNTL RESOURCE ITEM UTILITY ENDING MAXCC(000)
Example 2: List Resource Items for in Applid DBDCICSB and list program SMGPADM for Applid DBDCICSA.
LSTITM PG SMGPADM DBDCICSA
LSTALL DBDCICSA

DSN:MACS.MBC.BATCNTL BATCNTL RESOURCE ITEM UTILITY 10/25/2019
LSTITM PG SMGPADM DBDCICSA <OK

*----------------------------------------------------------------------
LSTITA PG SMGPADM ALO(YYY)
*----------------------------------------------------------------------
1 RECORD(S) LISTED
LSTALL DBDCICSA <OK

*----------------------------------------------------------------------
LSTITM FI SMGFILE DBDCICSA
LSTITA FI SMGFILE ALO(PLL) OPE(LLY) DSP(S) JCL(N)
LSTITP FI SMGFILE DSN1=ACS.SMGFILE
*----------------------------------------------------------------------
LSTITA PG SMGPADM ALO(YY)
*----------------------------------------------------------------------
LSTITM TR SMGA DBDCICSA
LSTITA TR SMGA ALO(YY)
*----------------------------------------------------------------------
3 RECORD(S) LISTED
BATCNTL RESOURCE ITEM UTILITY ENDING MAXCC(000)

3.7.5 Resource/Group XREF Screen
The Resource/Group XREF Screen allows you to display all Resource Groups where a Resource Item belongs and to optionally
remove the Resource from the group (UPDATE mode only). This screen is displayed by selected option ‘G’ on the on the Resource
Item Directory screen
MBCMRIX MacKinney Batch to CICS 07/25/20 13:40:59

Mode: UPDATE Resource/Group XREF Applid: DBDCICSA
Enter R-remove resource item from group: FI SMGFILE
* * <-Filters
S GrpAppl GrpName GrpDesc Upd User Upd Date
DFHT540 EML EML GROUP SEC1USER 09/11/19
DFHT540 PLT.T540 SPECIAL PLT STARTUP GROUP RJS1 08/30/19
DFHT540 TSTRESGRP TEST RESOURCE GROUP RJS1 08/16/19
ENTER=Process PF1=Help PF3=End PF7=Bwd PF8=Fwd
PF8/PF20 to scroll forward, PF7/PF19 to scroll backward, PF3/PF15 to return to the previous screen or PF1/PF13 for help.
Use one of the following selection codes in the S column before the entry:
Enter ‘R’ to remove the displayed Resource Item from the selected Group. This option only appears if Mode=UPDATE.

3.8 Resource Groups
Resource Groups allow you to connect up to 999 Resource Items (files, transactions, programs and TDQs) to a named group
and process these items using a single command. For example, use command UNAG to disable all transactions and programs
and close all files for a particular application with one group command. Use ALOG or ALSG to enable and open these
resources. See Section 5.1 for additional group commands that can be used with Resource Groups.
Each Resource Group must be given a name (up to 12-chars). The name is combined with the Group Applid to form a key.
Since the Group Applid is part of the key, you can use the same group name for more than one region. The Group Applid is
most often the region Applid, but can also be an ApplGrp name (See Section 3.8.1).
Update Resource Groups via the Administration Menu Option 5, use the batch utility MBCBRGRP (Section 3.8.8) or enter
one of the three fast-path transactions, MBCG, MBCO or MBCS. The transactions can be secured using a security manager,
such as RACF, to allow users the appropriate functionality.
MBCG - is the group update transaction allowing the user full functionality to create, modify, view, allocate/unallocate
and display status of groups. This level is assumed for access from the Administration Menu.
MBCO - is the operation transaction allowing the user to allocate/unallocate, view and display status of a group, but not
to create or modify groups.
MBCS - shows status of group resources and does not allow the user the ability to create, modify or execute groups.
3.8.1 Shared and Non-Shared Resource Groups

Typically you will define a Resource Group to connect non-shared Resource Items for a specific target Applid. You would
specify this target Applid for the Group definition Applid value to let MBC know from where to read the connected Resource
Items when processing a group command.
MBC also supports Shared Resource Groups which share connected resources common to all of the regions defined in an
ApplGrp. For a shared Resource Group, you would specify an @ApplGrp name as the Applid value for the Group definition
(ApplGrp names must begin with an ‘@’ and be no more than 8 characters long). For a shared Resource Group, you must also
specify the @ItemScope value to determine from where to read (and how you will need to define) the connected Resource
Items. Possible values for the @ItemScope are as follows:
U - Define unique Resource Items for each of the @ApplGrp regions using the region name as the Applid value for the
common Resource Item definition. If there are 5 regions defined in the the ApplGrp, you will need to define each resource
in the 5 different regions. This is the default value.
S - Define Resource Items once specifying the @ApplGrp name as the Applid value for the Resource Item definitions.
Each Item definition will be shared amongst all of the regions defined in the @ApplGrp. If there are 5 regions defined
in the ApplGrp, you will still only define each resource once. RLS files would be a candidate for this option.
R - The Group Applid value represents a single region because it is not an @ApplGrp even though it beins with an ‘@’.
Define each of the connected Resource Items only once specifying the region name as the Applid value for the
Resource Item definitions.

3.8.1.1 Using Shared Resource Groups
Example using Shared Resource Groups with (@ItemScope=S): Because @ItemScope=S (shared), each region would use
a common shared Resource Item definition for the allocate (same DSN and other file attributes).
1. This example would allocate the shared resources in the PRDFINSHR group in all of the Applids defined in the group
@APGRP01. The three Group Items defined in the Group PRDFINSHR will be processed in DBDCICS1 using the
shared Item definitions for @APGRP01. Then the same three Group Items will be processed in DBDCICS2 using the
same shared Item definitions for @APGRP01.
CICS @APPLGRP @APGRP01
ALOG PRDFINSHR
2. To send commands to only one of the regions in your ApplGrp then specify the target Applid (DBDCICS1) for your
CICS header card and use the optional Applid parm @APGRP01 on Group command(s). The three Group Items
defined for PRDFINSHR for Group Applid @APGRP01 will be processed using the three Resource Item defintions for
DBDCICS1.
CICS DBDCICS1
ALOG PRDFINSHR @APGRP01

ApplGrp: @APGRP01 Desc: APPL GROUP FOR RESOURCE GRPS
0010 DBDCICS1 0020 DBDCICS2 0030 0040 0050
0060 0070 0080 0090 0100
-------------------------------------------------------------------
Shared Resource Items defined only once using the ApplGrp used for the Applid in the definitions …

*_____ *_ *_______ * *_____________________________ <-Filters ALO OPE
@APGRP01 FI FINMSTR DEV.FINMSTR P L LLY
@APGRP01 FI FIN$FIL DEV.FIN$FIL P L LLY
@APGRP01 TR FINA
-------------------------------------------------------------------
… the Resource Group is also defined with the ApplGrp used for the Applid in the definition. The three shared Resource
Items can then be selected for the group.
MBCMGPM MacKinney Batch to CICS 07/25/20 10:48:38

Mode: UPDATE Group Item Maintenance Applid: DBDCICSA
GrpAppl: @APGRP01 GrpName: PRDFINSHR GrpDesc: SHARED PROD FINANCE
Enter "D" on Seq to deselect or new seq number to resequence. PF6 to Sel Items.
Filters-> *_ *_______
Seq Applid Resource
0010 @APGRP01 FI FINMSTR
0020 @APGRP01 PG FIN$FLE
0030 @APGRP01 TR FINA
-------------------------------------------------------------------
PF1=Help PF3=Save PF6=Sel Items PF7=Bwd PF8=Fwd PF12=Cncl

Examples using Shared Resource Groups with (@ItemScope=U): Because @ItemScope=U (unique), each region would
use a unique Resource Item definition for the allocate (unique DSN and other file attributes).
1. This example will allocate shared resources group PRDFINSHR in all of the Applids defined in the AppGrp @APGRP01
using the three Resource Items defined for DBDCICS1 when connected to DBDCICS1 and then the three Resource Items
defined for DBDCICS2 when connected to DBDCICS2.
CICS @APPLGRP @APGRP01
ALOG PRDFINSHR
2. To send commands to only one of the regions in your ApplGrp specify the target Applid (DBDCICS1) for your CICS
header card and add the optional Applid parm (@APGRP01) on Group command(s). The three Group Items defined for
PRDFINSHR for Group Applid @APGRP01 will be processed using the three Resource Item defintions for
DBDCICS1.
CICS DBDCICS1
ALOG PRDFINSHR @APGRP01

ApplGrp: @APGRP01 Desc: APPL GROUP FOR RESOURCE GRPS
0010 DBDCICS1 0020 DBDCICS2 0030 0040 0050
-------------------------------------------------------------------
Unique Resource Items are defined in each of the ApplGrp regions …

*_____ *_ *_______ * *_____________________________ <-Filters ALO OPE
DBDCICS1 FI FINMSTR DEV1.FINMSTR P L LLY
DBDCICS1 FI FIN$FIL DEV1.FIN$FIL P L LLY
DBDCICS1 TR FINA
DBDCICS2 FI FINMSTR DEV2.FINMSTR P L LLY
DBDCICS2 FI FIN$FIL DEV2.FIN$FIL P L LLY
DBDCICS2 TR FINA
-------------------------------------------------------------------
… the Resource Group is also defined with the ApplGrp used for the Applid in the definition. The three common Resource
Items can then be selected for the group.

GrpAppl: @APGRP01 GrpName: PRDFINSHR GrpDesc: SHARED PROD FINANCE
Filters-> *_ *_______
Seq Applid Resource
0010 >ApplGrp FI FINMSTR
0020 >ApplGrp PG FIN$FLE
0030 >ApplGrp TR FINA
-------------------------------------------------------------------
Note: When @ItemScope=U, the Applid column will display “>ApplGrp” and the “S” and DSN columns will not be
displayed. This is a reminder that unique Resource Items (including DSN values) will be read from each of the regions
defined in the @ApplGrp (i.e. @APGRP01) when Group Commands using GrpName (i.e. PRDFINSHR) are
processed, and that you must define unique Resource Items for each of the regions in the @ApplGrp.

Example combining the usage of Resource Groups (@ItemScope=R): For @ItemScope=R (region), the GrpAppl values
represents a single region Applid and not an ApplGrp. Resource Items would be owned by a single region Applid whose name
just happens to begin with an ‘@’ as the first character.
CICS @MYCICSA
ALOG PRDACCT
Unique Resource Items are defined for the region whose name is identified by @MYCICSA…

*_____ *_ *_______ * *_____________________________ <-Filters ALO OPE
@MYCICSA FI FINMSTR DEV.FINMSTR P L LLY
@MYCICSA FI FIN$FIL DEV.FIN$FIL P L LLY
@MYCICSA TR FINA
-------------------------------------------------------------------
… the Resource Group is also defined by the region Applid in the definition. The three non-shared Resource Items can then be
selected for the group.

GrpAppl: @MYCICSA GrpName: PRDACCT GrpDesc: SHARED PROD FINANCE
Filters-> *_ *_______
Seq Applid Resource
0010 @MYCICSA FI FINMSTR
0020 @MYCICSA PG FIN$FLE
0030 @MYCICSA TR FINA
-------------------------------------------------------------------

3.8.2 Group Directory Screen – MBCG
Enter transaction MBCG or select option 5 from the Administration Menu to display the Group Directory as shown below.
MBCMGRP MacKinney Batch to CICS 07/25/20 10:52:44

Mode: UPDATE Group Directory Applid: DBDCICSA
BATCNTL: MACS.MBC.BATCNTL Cur Order: GrpName
Enter E-edt C-cpy D-del I-itms S-sts V-view A-alo ds1 2-alo ds2 U-una group
*_______ *___________ * <-Filters
S GrpAppl GrpName SCO GrpDesc Upd User Upd Date
DBDCCICS ACCTING ACCOUNTING GROUP CICSUSER 10/25/19
DBDCCICS ACCTING2 ACCOUNTING SECONDARY GROUP CICSUSER 10/25/19
CICSPROD FINANCE FINANCE PRIMARY GROUP CICSUSER 11/29/19
CICSPROD FINANCE2 FINANCE SECONDARY GROUP CICSUSER 11/29/19
@AGRP1 PRDFINSHR S SHARED PROD FINANCE CICSUSER 01/10/20
ENTER=Process PF1=Help PF3=End PF6=Add PF7=Bwd PF8=Fwd PF9=ToggleOrder
Press PF6/PF18 to add a new group (Section 3.8.3), PF8/PF20 to scroll forward, PF7/PF19 to scroll backward, PF9/PF21 to
toggle the display order between GrpName and GrpAppl, or PF3/PF15 to return back to the previous screen. Enter a GrpAppl,
GrpName or SCO filter value to display only records matching the filter. GrpAppl names that begin with an ‘@’ and that have
an @ItemScope = ‘S’ will be displayed in yellow.
Enter ‘E’ to edit the group definition values on the Define Resource Group screen (Section 3.8.3)
Enter ‘C’ to copy the group definition values to another group (Section 3.8.5)
Enter ‘D’ to delete the group.
Enter ‘I’ to display the member items for the Resource Group.
Enter ‘S’ to display the resource status values. Any errors are identified on the status screen. All resources in the group
display their current dataset allocation (if files) and status.
Enter ‘V’ to display group information. From the MBCMGPD screen, press PF5 to display Resource Item values.
Enter ‘A’ to allocate/enable the group resources. For Type ‘FI’ items, the item DSN1 value is used for allocation.
Enter ‘2’ to allocate/enable all of the group resources. For Type ‘FI’ items, the item DSN2 value is used in the allocation,
unless DSN2 is blank, in which case the DSN1 value is used.
Enter ‘U’ to unallocate/disable the group resources.
GrpAppl – displays the CICS Applid name or optional shared @ApplGrp name for the current selected Resource Group.
Grp Name – displays the name for the Resource Group.
SCO – displays the @ItemScope value for the group. Value will be blank for GrpAppl names that do not begin with an ‘@’ or
if the shared group has not been updated.
GrpDesc – displays the description for the Resource Group.

Example of Group Directory Toggle Function
Use PF9 to toggle to APPLID order.

BATCNTL: MACS.MBC.BATCNTL Cur Order: GrpAppl
*_______ *___________ * <-Filters
S GrpAppl GrpName SCO GrpDesc Upd User Upd Date
@AGRP1 PRDFINSHR S SHARED PROD FINANCE CICSUSER 01/10/20
CICSPROD FINANCE FINANCE GROUP CICSUSER 11/29/19
CICSPROD FINANCE2 FINANCE SECONDARY GROUP CICSUSER 11/29/19
DBDCCICS ACCTING ACCOUNTING GROUP CICSUSER 10/25/19
DBDCCICS ACCTING2 ACCOUNTING SECONDARY GROUP CICSUSER 10/25/19
GrpAppl names that begin with an ‘@’ and that have an @ItemScope = ‘S’ will be displayed in yellow.

3.8.3 Group Define Screen
The Group Define Screen lets you define a new Resource Group. This screen is launched by pressing PF6/PF18 from the
Group Directory screen.
MBCMGPD MacKinney Batch to CICS 07/25/20 10:52:44

Mode: ADD Define Resource Group Applid: DBDCICSA
Specify new GrpName, then PF5 to open Items List->PF3 to Save or PF12 to Cncl
GrpName: Specify unique Group Name Group Items:
GrpDesc: Group description
GrpAppl: Region Applid / ApplGrp Name that begins with an "@"

Region Applid: Resource Items for Group cmds limited to single Region Applid
GrpAppl begins with "@": Usage determined by @ItemScope
@ItemScope: Where to define Items for Group cmds when GrpAppl begins with "@"
U-Define unique items for each ApplGrp region with Applid=region (default)
S-Define items once with Applid=@applgrp to share amongst all ApplGrp regions
R-GrpAppl value is not an ApplGrp; define items once for Region Applid use
PF1=Help PF3=Save PF5=Grp Items PF12=Cncl
Specify new GrpName, GrpDesc, GrpAppl and optional @ItemScope then press PF5 to open the Group Item Maintenance
Screen where Resource Items are assigned or press PF12 to cancel the define and return back to the previous screen (does not
process the define).
GrpName – specify a unique 1-12 character uppercase name for this Group (no wildcards). This name is specified as the
target group for group commands such as CLOG, ALOG, UNAG, etc.
TIP! Special GrpName PLT.applid is used in combination with program MBCPPLA to allocate Resource Items required by
PLT programs (see Section 1.9.7). For example, create group PLT.DFHTEST1 to be read by MBCPPLA in APPLID
DFHTEST1.
GrpDesc – specify a unique 1-30 character name for this Group. This name appears on the Group Directory screen to help
identify the group.
GrpAppl – serves to limit the scope of the Resource Items allowing you to define different DSN values for files in sandbox,
test, or production regions. Specify a CICS Region Applid name or optional ApplGrp name that begins with an ‘@’ prefix and
is limited to a total of 8 characters. If you have Applids sharing resources, using an ApplGrp name allows you to route
Resource Group commands to multiple Applids. See Section 3.8.1.1 for examples.
@ItemScope – determines from where to define (and read) connected Resource Items for Group commands when using a
GrpAppl that begins with an ‘@’. Value is ignored, if GrpAppl does not begin with an ‘@’. Specify one of the following:
U - Define unique Resource Items for each of the @ApplGrp regions using the region name as the Applid value for the
common Resource Item definition. If there are 5 regions defined in the the ApplGrp, you will need to define each
resource in the 5 different regions. This is the default value.
S - Define Resource Items once specifying the @ApplGrp name as the Applid value for the Resource Item definitions.
Each Item definition will be shared amongst all of the regions defined in the @ApplGrp. If there are 5 regions defined
in the ApplGrp, you will still only define each resource once. RLS files would be a candidate for this option.
R - The Group Applid value represents a single region because it is not an @ApplGrp even though it beins with an ‘@’.
Define each of the connected Resource Items only once specifying the region name as the Applid value for the
Resource Item definitions

3.8.4 Group Maintenance Screen
The Group Maintenance Screen allows you to add, change or delete Resource Group member Items and change the order of the
Items in a Resource Group. This screen is launched by entering ‘I’ in the Sel field from the Group Directory screen or by pressing
PF5/PF17 from the Group Define screen.

GrpAppl: DBDCICSA GrpName: BAT GrpDesc: SAMPLE FILES AND TDQS
Filters-> *_ *_______* *_____________________________
Seq Applid Resource S Primary DSN1
0010 DBDCICSA FI EMLDIR S MACS.EMLDIR
0020 DBDCICSA TD CPLI
0030 DBDCICSA TD CEJL
PF1=Help PF3=Save PF6=Sel Items PF7=Bwd PF8=Fwd PF9=Toggle DSN PF12=Cncl
Press PF6/PF18 to add new item(s), PF8/PF20 to scroll forward, PF7/PF19 to scroll backward, PF3/PF15 to save changes to
the group and return back to the previous screen, PF9/PF21 to toggle the display order between Primary and Secondary DSN,
PF1/PF13 for help or PF12/PF24 to cancel changes to the group and return back to the previous screen. Enter Resource,
Secondary DSN indicator (‘S’), and DSN filter values to display only records matching the filters.You can remove an Item
from the Group by entering a ‘D’ in the Seq column aligned with the Resource. The order of the items is altered by entering a
new sequence number in the Seq column and pressing Enter.
Display headings:
GrpAppl – displays the CICS Applid name or optional shared @ApplGrp name for the current selected Resource Group.
Grp Name – displays the name for the current selected Resource Group.
GrpDesc – displays the description for the current selected Resource Group.
Column headings:
Seq – overtype sequence number to re-order Items in Resource Group. For example to move Item 0030 after Item 0010
overtype 0030 with 0015 and press enter. Items are re-numbered by 10’s. You can also remove a Resource Item from a group
by entering a ‘D’ in the Seq field (the Resource Item record is not deleted, just the record associating the Item with the
Group).
Applid – displays the Applid of the Item resource as confirmation you are selecting Items belonging to the correct Applid.
Resource – displays the Resource Type and Resource Name of the Item.
S – an ‘S’ indicates the presence of a non-blank Secondary DSN value (DSN2) and a blank indicates no Secondary DSN
value (DSN2) is present.
DSN – Displays Primary or Secondary DSN for Type ‘FI’ Resource Items (PF9/PF21 to toggle). The Secondary DSN
displays in yellow if the name is the same as the Primary DSN.

3.8.4.1 Group Item Selection Screen
The Group Item Selection Screen lets you select Resource Items (files, programs, transactions, TCPIP services or TDQs) as
member Items in the current Resource Group. Items previously selected for the group are colored Blue and cannot be
selected. Items not selected are colored Green. Below is a sample screen for a Group that has a specific GrpAppl (Applid).
MBCMITS MacKinney Batch to CICS 07/25/20 13:35:40

Group Item Selection Applid: DBDCICSA
Enter "S"-to select Item(s) for GrpName: BAT GrpAppl: DEDCICSA
*_ *_______ <-Filters
Sel Applid Resource Primary DSN1
DBDCICSA FI BATCNTL MACS.MBC.BATCNTL
DBDCICSA FI BATCSTS MACS.DBDCICSA.BATCSTS
DBDCICSA FI BATSTAT MACS.MBC.BATSTAT
DBDCICSA FI SMGFILE MACS.SMGFILE
DBDCICSA PG SMGPADM
DBDCICSA TD CCVX
DBDCICSA TD CDB2
DBDCICSA TD CEJL
DBDCICSA TD CPLI
PF1=Help PF3=End PF7=Bwd PF8=Fwd PF9=Toggle DSN PF12=Cancel
Enter an ‘S’ by Item(s) and press ENTER to add new item(s), PF3/PF15 to end back to the previous screen (does not add or
re-add the current displayed item). Define up to 999 items for each group.
Resource Type - Displays ‘FI’ for a File, ‘PG’ for a Program, ‘TR’ for a Tranid, ‘IP’ for a TCPIP Service, ‘TD’ for a TDQ or
‘TX’ for Extrapartition TDQ.
Resource Name – Displays the RDO defined name of the File, Program, Tranid, TCPIP Service or TDQ.
DSN – Displays Primary or Secondary DSN for the corresponding Type ‘FI’ Resource Item (PF9/PF21 to toggle) defined in
the Applid (GrpAppl).

Below is a sample Group Item Selection screen for a shared Resource Group with an @ItemScope=U (Unique Resource Items
defined in each region of the ApplGrp).
MBCMITS MacKinney Batch to CICS 07/25/20 13:35:40

Group Item Selection Applid: DBDCICSA
BATCNTL: MACS.MBC.BATCNTL SelAppl DBDCICSA
Enter "S"-to select Item(s) for GrpName BAT GrpAppl @PRODGRP
*_ *_______ <-Filters
Sel Applid Resource
>ApplGrp FI BATCNTL
>ApplGrp FI BATCNTL
>ApplGrp FI BATCSTS
>ApplGrp FI BATSTAT
>ApplGrp FI SMGFILE
>ApplGrp PG SMGPADM
>ApplGrp TD CCVX
>ApplGrp TD CDB2
>ApplGrp TD CEJL
>ApplGrp TD CPLI
PF1=Help PF3=End PF7=Bwd PF8=Fwd PF9=Toggle DSN PF12=Cancel
Enter an ‘S’ by Item(s) and press ENTER to add new item(s), PF3/PF15 to end back to the previous screen (does not add or
re-add the current displayed item). Define up to 999 items for each group.
SelAppl - Displays the first Applid in the current shared @ApplGrp. This the Applid from which any shared Resource Items
will be presented for selection. You should verify all selected Resource Items are defined in each of the ApplGrp regions.
Resource Type - Displays ‘FI’ for a File, ‘PG’ for a Program, ‘TR’ for a Tranid, ‘IP’ for a TCPIP Service, ‘TD’ for a TDQ or
‘TX’ for Extrapartition TDQ.
Resource Name – Displays the RDO defined name of the File, Program, Tranid, TCPIP Service or TDQ.

3.8.5 Group Copy Screen
The Group Copy Screen copies resources (file/program/transaction/TDQ) from the source group to a new target group.
Enter ‘C’ in the S column from the Group Directory to display the Group Copy Screen. For example, copy DBDCCICS
FINANCE group. . .

*_______ *___________ <-Filters
S GrpAppl GrpName GrpDesc Upd User Upd Date-Time
DBDCCICS ACCTING ACCOUNTING GROUP CICSUSER 10/25/19 13:05
DBDCCICS ACCTING2 ACCOUNTING SECONDARY GROUP CICSUSER 10/25/19 14:19
CICSPROD FINANCE FINANCE PRIMARY GROUP CICSUSER 11/29/19 14:33
CICSPROD FINANCE2 FINANCE SECONDARY GROUP CICSUSER 11/29/19 15:50
C DBDCCICS FINANCE FINANCE PRIMARY GROUP CICSUSER 12/06/19 09:30
. . . to FINANCE2 group in the same APPLID.
MBCMGPC MacKinney Batch to CICS 01/10/20 15:47:49

Mode: COPY Group Copy Applid: DBDCICSA
Fill in Target fields below and press ENTER to copy. Press PF3 when done.
Source GrpAppl: DBDCCICS Source APPLID
Source GrpName: FINANCE Source group name
Source GrpDesc: FINANCE PRIMARY GROUP Source group desc
Resource Items not defined in Target GrpAppl will be copied (check values)
Target GrpAppl: DBDCCICS Specify target APPLID for copy
Target GrpName: FINANCE2 Specify target group name for copy
Target GrpDesc: FINANCE SECONDARY GROUP Specify target group desc
ENTER=Copy PF1=Help PF3=End
Specify new Target GrpAppl, Target GrpName and Target GrpDesc then press ENTER to copy the group or PF3/PF15 to end
back to the previous screen (does not process the copy).

*_______ *___________ <-Filters
C DBDCCICS FINANCE FINANCE PRIMARY GROUP CICSUSER 12/06/19 09:30

3.8.6 Group Operation Screen – MBCO
Transaction MBCO displays the Group Directory for Operations screen. The example screen below shows the resources for
the group FINANCE for Applid DBDCCICS being allocated.

Enter A-aloc dsn1 2-aloc dsn2 U-unal V-view S-status of selected group
*_______ *___________ <-Filters
CICSPROD FINANCE FINANCE GROUP CICSUSER 11/29/19 14:33
A DBDCCICS FINANCE FINANCE GROUP CICSUSER 12/06/19 09:30
DBDCCICS FINANCE2 FINANCE SECONDARY GROUP CICSUSER 12/06/19 09:35
Message MBCE350-ALOC FOR GROUP FINANCE SUCCESSFUL displays at the bottom of the screen if there are no
errors.
Enter ‘A’ to allocate/enable the resources within the group using the Primary DSN1 for Type ‘FI’ resources.
Enter ‘2’ to allocate/enable all of the resources within the group. For TYPE=FI items, the DSN2 value specified for the
item is used in the allocation, unless DSN2 is blank, in which case the DSN1 value is used.
Enter ‘U’ to unallocate/disable the resources within the group.
Enter ‘V’ to display the group resources and datasets associated with each resource. These are the allocations and statuses
to implement when the group is allocated with the ALOG or ALSG commands.
Enter ‘S’ to display the resource status values. Any errors are identified on the status screen. All resources in the group
display their current dataset allocation (if files) and status.
GrpAppl – displays the CICS Applid name or optional ApplGrp name for the current selected Resource Group.
Grp Name – displays the name for the current selected Resource Group.
GrpDesc – displays the description for the current selected Resource Group.

3.8.7 Group Status Screen – MBCS
Enter transaction MBCS to display the Group Directory for Status screen. The example screen below shows the resources for
the group FINANCE for Applid DBDCCICS being selected for status viewing.

*_______ *___________ <-Filters
S DBDCCICS FINANCE FINANCE PRIMARY GROUP CICSUSER 12/06/19 09:30
DBDCCICS FINANCE2 FINANCE SECONDARY GROUP CICSUSER 12/06/19 09:35
After selecting the FINANCE group from Applid DBDCCICS, the status screen below displays.
MBCMGPS MacKinney Batch to CICS 01/10/20 10:15:26

Group Status Applid: DBDCICSA
GrpAppl: DBDCICSA GrpName: FINANCE GrpDesc: FINANCE PRIMARY GROUP
Resource Ena Ope Upd Add Del DSN/Info
FI FINMSTR ENA OPE UPD ADD DEL YOUR.FINANCE.MASTER
PG FINPGM ENA
TR FINA ENA
FI FIN$FLE ENA OPE NOU NOA NOD YOUR.FINANCE.FILE
TR FIN$ ENA
TD FNTD ENA TYP=INT TRI=00001 TRN=LOGF
TD FNTQ ENA TYP=IND NAM=CSSL
TX FNTX ENA OPE DD=FNTXFIL YOUR.FINANCE.TDQFIL
PF1=Help PF3=End PF5=Refresh PF7=Bwd PF8=Fwd
NOTE: If the GrpAppl value is for a remote CICS, the value is be displayed in Yellow.
Resource – displays the Resource Type and Name values.
NOTE: If the Resource Status record indicates “not allocated”, the Resource Type (i.e. FI, PG, TR) is displayed in Yellow. If
MBC is unable to INQUIRE the Resource (not defined to CICS), the Resource Name is displayed in Red and additional error
information displays in the DSN/Info column.
Ena – displays the current Enable status value (ENA|DIS|DSA|UNE) for the resource.
Ope – displays the current Open status value (OPE|CLO|OPG|CLG|CLR) for the resource.
Upd Add Del - displays current Update/Add/Delete file attributes for FI resources and TDQ DD name for TX resources
DSN/Info – displays DSN for FI resources or additional resource information for TD resources.
3.8.8 Resource Groups via Batch (MBCBRGRP)
Batch utility MBCBRGRP allows you to list, delete and define Resource Group records in the BATNCTL file. Updating
group resources using MBCBRGRP requires update access to the BATCNTL file (file must not be open for update in
any CICS region). Sample JCL is in source member MBCJRGRP. The format of the column specific control cards are
listed below. Multiple cards can be input in the same job.
column 8 13 16 17 30 64
DEFGRP aaaaaaaa nnnnnnnnnnnn description SCO(c)

DEFITM ssss tt rrrrrrrr
DELGRP aaaaaaaa nnnnnnnnnnnn
REMITM aaaaaaaa nnnnnnnnnnnn tt rrrrrrrr
DELALL aaaaaaaa | ‘ALL’
LSTGRP aaaaaaaa nnnnnnnnnnnn
LSTALL aaaaaaaa | ‘ALL’
USEPCH
DEFGRP – define a Resource Group name. A DEFGRP card must come before DEFITM card(s)
DEFITM – connect a Resource Item to a Resource Group. DEFITM card(s) must follow a DEFGRP card
DELGRP – delete group resources for a specific Applid / group name
REMITM – remove Resource Item from a specific Applid / group name
DELALL – delete all groups for a specific Applid or ‘All’ Applids
LSTGRP – list group resources for a specific Applid / group name
LSTALL – list all groups for a specific Applid or ‘All’ Applids
USEPCH - creates DEF* cards from LSTGRP and LSTALL options in SYSPCH DD or DLBL (see TIP! Below)
aaaaaaaa – Applid aaaaaaaa for the group. Begins in col 8 for max 8 bytes.
nnnnnnnnnnnn – group name. Begins in col 17 for max 12 bytes.
description – group description. Begins in col 30 for max 30 bytes.
c – Optional @ItemScope value for Resource Group that references shared Resource Items begins in Col 64. Group Applid must
begin with an ‘@’ and be no more than 8 characters in length. Value can be one of the following:
U- Define unique Resource Items for each of the @ApplGrp regions using the region name as the Applid value for the common
Resource Item definition. If there are 5 regions defined in the the ApplGrp, you will need to define each resource in the 5
different regions. This is the default value.
S- Define Resource Items once specifying the @ApplGrp name as the Applid value for the Resource Item definitions. Each Item
definition will be shared amongst all of the regions defined in the @ApplGrp. If there are 5 regions defined in the ApplGrp, you
will still only define each resource once. RLS files would be a candidate for this option.
R- The Group Applid value represents a single region because it is not an @ApplGrp even though it beins with an ‘@’. Define each
of the connected Resource Items only once specifying the region name as the Applid value for the Resource Item definitions
ssss - 4-digit item sequence number for determining the order 0001-9999 in which Resource Items are processed (limit for items
is 999). See WARNING below.
rrrrrrrr – 8-character (FI|PG) or 4-character (TR|TD|TX – blank filled) Resource Name and begins in col 16.
WARNING! Sequence numbers for items added in batch are not automatically re-numbered in increments of 10 as they
are online (Section 3.8.4). Editing the Resource Items online after they have been added in batch will cause automatic
renumbering to occur.
TIP! You can use the LSTGRP and LSTALL functions to create a batch backup. Copy and paste the LSTGRP and
LSTALL lines created on the report output, perform a “change all LST prefix to DEF prefix” or use USEPCH option. Then
use the altered cards or SYSPCH file as input for DEFGRP and DEFITM entries.

Example 1: Define Resource Groups BATCHGROUP1 and BATCHGROUP2 with multiple items in each group.
LSTGRP DBDCICSA BATCHGROUP1
DELGRP DBDCICSA BATCHGROUP1
DEFGRP DBDCICSA BATCHGROUP1 BATCH ADDED TEST GROUP
DEFITM 0010 FI EMLDOC
DEFITM 0020 FI EMLSTS
DEFGRP DFHCICSB BATCHGROUP2 BATCH ADDED TEST GROUP
DEFITM 0010 FI EMLDOC
DEFITM 0020 FI EMLSTS

DSN:MACS.MBC.BATCNTL BATCNTL RESOURCE GROUP UTILITY 10/25/2019
LSTGRP DBDCICSA BATCHGROUP1 BATCH ADDED TEST GROUP <OK

LSTITM 0010 FI EMLDOC MACS.EMLDOC
LSTITM 0020 FI EMLSTS MACS.EMLSTS
2 ITEMS LISTED FOR GROUP(BATCHGROUP1 ) APPLID(DBDCICSA )
DELGRP DBDCICSA BATCHGROUP1 <OK

2 ITEMS ADDED FOR GROUP(BATCHGROUP1 ) APPLID(DFHCICSA )
DEFGRP DBDCICSA BATCHGROUP1 BATCH ADDED TEST GROUP <OK

DEFITM 0010 FI EMLDOC MACS.EMLDOC <ADD
DEFITM 0020 FI EMLSTS MACS.EMLSTS <ADD
2 ITEMS ADDED FOR GROUP(BATCHGROUP1 ) APPLID(DBDCICSA )
DEFGRP DFHCICSB BATCHGROUP2 BATCH ADDED TEST GROUP <OK

DEFITM 0010 FI EMLDOC MACS.EMLDOC <ADD
DEFITM 0020 FI EMLSTS MACS.EMLSTS <ADD
2 ITEMS ADDED FOR GROUP(BATCHGROUP2 ) APPLID(DFHCICSB )
BATCNTL RESOURCE GROUP UTILITY ENDING MAXCC(000)

3.9 Status Tracking Maintenance
If Status Tracking is enabled (STATFLAG=Y), MBC stores status information in CICS Resource Status records kept in file
BATCSTS. The Status Tracking Maintenance administrative function allows you to view detail of records kept in the file, to
delete records which could be necessary if resources are removed from CICS and to synchronize records with current CICS
status.
CICS Resource Status records are automatically updated when you execute an MBCBATCH command, use the Online
Command Processor or Group Operation screen to change the status of a supported resource. The following sections discuss
the administration of Resource Status records.
3.9.1 Status Tracking Maintenance Screen – MBC1

Select option 6 from the Administration Menu (MBCA or MBCB) or enter fast-path tranid MBC1 to display the Status
Tracking Maintenance Screen as shown below. MBC1 and MBCB allow only read-only options. The Status Tracking
Maintenance Screen displays the current values for resources defined in the BATCSTS file.
NOTE: Current CICS status values differing from the BATCSTS value shown are displayed in Yellow. If the Resource
Status record indicates “not allocated”, the Resource Type for FI/PG/TR/IP/TD/TX is displayed in Yellow. If the Resource
DSN is flagged as RLS, the DSN value is displayed in Neutral (White). If MBC is unable to INQUIRE the Resource (not
defined to CICS), the Resource Name is displayed in Red.
MBCMSTM MacKinney Batch to CICS 07/25/20 13:35:40

Mode: UPDATE Status Tracking Maintenance Applid: DBDCICSA
BATCSTS: MACS.DBDCICSA.BATCSTS
Enter D-delete I-Info S-status or Y-sYnc selected Resource
*_ *_______ *__ *__ *_____________________________ <-Filters
S Resource Ena Ope Upd Add Del Dsn/Info
FI EMLDIR ENA OPE UPD ADD DEL MACS.EMLDIR
FI EMLDOC DIS CLO UPD ADD DEL MACS.EMLDOC
FI EMLDST ENA OPE UPD ADD DEL MACS.EMLDST
FI EMLRTE ENA OPE UPD ADD DEL MACS.EMLRTE
FI MSXGCF$ ENA CLO UPD ADD DEL MACS.T540.MSXGCF$
FI SMGFILE ENA OPE NOU NOA NOD MACS.SMGFILE
PG EMLP100 ENA
PG SMGPADM ENA
TR SMGA ENA
TD CADL ENA TYP=INT TRI=00001 TRN=LOG8
TX CSSL ENA OPE DD=MSGUSR MACS.MSGUSR
ENTER=Process PF1=Help PF3=End PF7=Bwd PF8=Fwd
Press PF8/PF20 to scroll forward, PF7/PF19 to scroll backward or PF3/PF15 to return back to the previous screen. Each entry
may be selected for Delete or additional information by entering a ‘D’ or ‘I’ in the S column before the entry.
Enter ‘D’ to delete the Resource Item status record. If the Resource Item has not been removed, a new status record is
created the next time the Resource Item is allocated by MBC.
Enter ‘I’ to display Status Tracking Maintenance Detail screen for the Resource Item.
Enter ‘D’ to delete the group.
Enter ‘S’ to display the current Resource Item CICS status values.
Enter ‘Y’ to synchronize (set) the BATCSTS file with the current CICS values.

3.9.2 Status Tracking Detail Screen
The Status Tracking Detail screen displays additional detail from the CICS Status Record.
MBCMSTD MacKinney Batch to CICS 07/25/20 13:35:40

Status Tracking Detail Applid: DBDCICSA
BATCSTS: MACS.DBDCICSA.BATCSTS
Press PF3 when done viewing
Resource Type: FI
Resource Name: SMGFILE
Resource Status
ALO Status: ALO
ENA Status: ENA
OPE Status: OPE
File Upd Attr: ADD DEL UPD
ALO w/SVC99: N (Y/N)
File Disp: S (S-Shr|O-Old)
DSN: MACS.SMGFILE
Last ALO Cmd Date: 09/21/2019 Time: 10:22:03

Last Res Cmd Date: 09/21/2019 Time: 10:22:03
Last Update Date : 09/08/2019 Time: 10:57:26 User: RJS2 Job: SMG$JCL
PF1=Help PF3=End
Press PF3/PF15 to return back to the previous screen.
Resource Type - Displays FI (File), PG (Program), TR (Tranid), IP (TCPIP Service) TD (TDQ), TX (Extrapartition TDQ),
SV (SVC99 allocated resource), DA (DSNC resource) DB (DBLC/CSDA/CDSS resource), DL (DLOC resource).
Resource Name – Displays the resource name.
ALO Status – Displays the most recent Allocation status tracked by MBC.
ENA Status – Displays the most recent Enabled status tracked by MBC.
OPE Status – Displays the most recent Open status tracked by MBC for Resource Type ‘FI’, ‘IP’ and ‘TX’ entries only.
Resource Attr – Displays the ‘File Upd Attr’ (most recent Add, Del, Upd status tracked by MBC) Type ‘FI’ entries; ‘DD=’ for
Type ‘TX’ entries or ‘Command Type’ (ALOQ disp|UNAQ) for Type ‘SV’ entries.
ALO w/SVC99 – Displays ‘Y’ if resource are allocated using SVC99 or ‘N’ it resource are not allocated using SVC99 (for
Resource Type ‘FI’, ‘TX’ and ‘SV’ entries only).
File Disp – Displays the most recent File Disposition (SHR/OLD/MOD) tracked by MBC for Resource Type ‘FI’ and ‘TX’
entries only.
DSN – Displays the most recent Dataset Name tracked by MBC for Resource Type ‘FI’ entries only.
Last ALO Cmd Date – Displays the date and time the resource was most recently Allocated or Unallocated by MBC.
Last Res Cmd Date – Displays the date and time an MBC command was executed on behalf of the resource (including
Allocation or Unallocation commands).
Last Update Date – Displays the date and time the resource status record was most updated and the optional Userid and Job
name (if updated by batch) or Program name (if updated by MBC online program) responsible for the update.

3.9.3 Status Tracking Batch Maintenance
There are two batch utility programs for assisting with Status Tracking maintenance, MBCBCSTS (BATCSTS) and
MBCBSTAT (BATSTAT). MBCBCSTS (Section 3.9.3.1) is a utility for the BATCSTS file and MBCBSTAT is a utilify for
the BATSTAT file.
3.9.3.1 MBCBCSTS
MBCBCSTS lets you list and delete records from the BATCSTS file. Deleting records requires update access to the
BATCSTS file (file must not be open for update in any CICS region). Sample JCL is in source member MBCJCSTS. The
format of the column specific control cards are listed below. Multiple cards can be input in the same job.
col 4 13 16
FFF aaaaaaaa tt rrrrrrrr

FFF aaaaaaaa AGE=999
FFF aaaaaaaa | ‘ALL’
FFF – Function is PRT to print records or DEL to delete records

aaaaaaaa – Applid for filtering begins in col 4 for max 8 bytes. Enter value ‘ALL’ to process all Applid values.
AGE=999 – Enter AGE = 999 where 999 is a value from 1-365 to indicate days before the current day. Age will filter records
whose update date is newer than the specified age.
rrrrrrrr – 8-character (FI|PG|IP) or 4-character (TR|TD|TX – blank filled) Resource Name and begins in col 16.
Example 1: Print all records and then delete all records whose update date is older than 180 days.
PRT ALL
DEL DBDCICSA AGE=180

DSN:MACS.MBC.BATCSTS BATCSTS FILE MAINTENANCE 10/25/2019
INPUT: PRT ALL
APPLID TYPE RESOURCE USERID JOB NAME DATE TIME ATTR/CMD

DBDCICSA FI EMLDIR USRA MBCBCPRE 20190819 15420697 ENA CLO UPD ADD DEL MACS.EMLDIR
FI EMLDOC USRA MBCBCPRE 20190819 15420697 DIS CLO NOU NOA NOD MACS.EMLDOC
FI EMLDST USRA MBCBCPRE 20190819 15420697 ENA OPE UPD ADD DEL MACS.EMLDST
. . .
TOTAL RECORDS PRINTED: 249
INPUT: DEL DBDCICSA AGE=180
APPLID TYPE RESOURCE USERID JOB NAME DATE TIME ATTR/CMD

DBDCICSA TD CDB2 USRA MBCJOB1 20190522 15420697 ENA
TOTAL RECORDS DELETED: 1
BATCSTS FILE MAINTENANCE ENDING MAXCC(000)

3.9.3.2 MBCBSTAT
MBCBSTAT lets you define, list and delete records from the BATSTAT file. Defining or deleting records requires update
access to the BATSTAT file (file must not be open for update in any CICS region). Sample JCL is in source member
MBCJSTAT. The format of the column specific control cards are listed below. Multiple cards can be input in the same job.
column 8 13 17 20 29 38 47 56
DEFSTS aaaaaaaa tt rrrrrrrr mmddyyyy hhmmsstt jjjjjjjj uuuuuuuu

DEFCMD ccccccccccccc ... ccccccccccccc
DELSTS aaaaaaaa | ‘ALL’
DELRES aaaaaaaa tt rrrrrrrr
LSTSTS aaaaaaaa | ‘ALL’
LSTRES aaaaaaaa tt rrrrrrrr
USEPCH
DEFSTS – define a status resource. A DEFSTS card must come before a paired DEFCMD card
DEFCMD – specifies MBCBATCH command for resource and must follow a DEFSTS card
DELSTS – delete resources for a specific Applid or ‘All’ Applids
DELRES – delete a status resource record for a specific Resource Item
LSTSTS – list all groups for a specific Applid or ‘All’ Applids
LSTRES – list record for a specific resource for a specific Applid
USEPCH - creates DEF* cards from LSTSTS and LSTRES options in SYSPCH DD or DLBL (see TIP! Below)
aaaaaaaa – Applid aaaaaaaa for the group. Begins in col 8 for max 8 bytes.
Ccc...ccc – MBCBATCH command for resource identified in DEFSTS card. Begins in col 8 for max 64 bytes
mmddyyyy – sets date portion of command timestamp for resource. Begins in col 29 for 8 bytes.
hhmmSStt – sets time portion of command timestamp for resource. Begins in col 38 for 8 bytes.
jjjjjjjj – sets job name for resource. Begins in col 47 for 8 bytes.
uuuuuuuu – sets user name for resource. Begins in col 47 for 8 bytes.
tt – Resource Type (tt = FI-file|PG-program|TR-tranid|TD-TDQ|TX-Ext TDQ|IP-TCPIP Service). Begins in col 13.
rrrrrrrr – 8-char (FI|PG|IP) or 4-char (TR|TD|TX – blank filled) Resource Name and begins in col 16.
TIP! You can use the LSTSTS and LSTRES functions to create a batch backup. Copy and paste the LSTSTS and LSTRES
lines created on the report output, perform a “change all LST prefix to DEF prefix” or use USEPCH option. Then use the
altered cards or SYSPCH file as input for DEFSTS and DEFCMD entries.
Example 1: Delete existing resource (FI|EMLDST), define new command (CLOS EMLDST) for resource (FI|EMLDST),
then list resource (FI|EMLDST).
DELRES T540 FI EMLDST
DEFSTS T540 FI EMLDST 20190820 14364322 MBC$RUN RJS1
DEFCMD CLOS EMLSTS
LSTRES T540 FI EMLDST

DSN:MACS.MBC.BATCSTAT BATSTAT STATUS RECORD UTILITY 10/25/2019
DELRES T540 FI EMLDST <OK

*----------------------------------------------------------------------
T540 FI EMLDST ** DELETED **
*----------------------------------------------------------------------
1 RECORD(S) DELETED
DEFSTS T540 FI EMLDST 20190820 14364322 MBC$RUN RJS1 <OK

DEFCMD CLOS EMLDST <OK
*----------------------------------------------------------------------
1 RECORD(S) ADDED
LSTRES T540 FI EMLDST <OK

*----------------------------------------------------------------------
LSTSTS T540 FI EMLDST 20190820 14364322 MBC$RUN RJS1
LSTCMD CLOS EMLSTS
*----------------------------------------------------------------------
1 RECORD(S) LISTED
BATSTAT STATUS RECORD UTILITY ENDING MAXCC(000)

3.10 Domain Applids
Domain Applid records serve two purposes for MBC. For the TCP/IP version, Domain Applid records are required and are
used to provide the IP address and Port of target CICS regions. For both TCP/IP and EXCI versions, Domain Applid records
can work alongside the new option DOMSEC to allow securing access to critical regions. To make use of this feature, you
must define two or more BATCNTL files with the least granular definition including one BATCNTL file for production
regions and one BATCNTL file for test regions. You can define as many BATCNTL files as you need. EXCI users not using
DOMSEC, do not need to define Domain Applids.
If DOMSEC=Y is specified and you define your production Applids in your production BATCNTL file and test Applids in
your test BATCNTL file, then a batch jobs with the test BATCNTL file in the JCL cannot target a production CICS region.
The default action for DOMSEC=N is to not require the target Applid be defined to any BATCNTL file.
You can update Domain Applids via the Administration Menu Option 7, using the batch utility MBCBDOM (Section 3.10.3)
or by entering fast-path transaction (MBCD). The following sections discuss the creation and modification of Domain
Applids.
3.10.1 Domain Directory Screen – MBCD

Enter transaction MBCD or select option 7 from the Administration Menu to display the Domain Directory as shown below.
MBCMDMD MacKinney Batch to CICS 07/25/20 10:09:07

Mode: UPDATE Domain Directory Applid: DBDCICSA
Enter E-edit C-copy D-del or V-view selected Applid
*_______ <-Filter
S Applid Description
DBDCICSA Production Applid TS 5.2.0
DBDCCICB Production Applid TS 5.2.0
DBDCCICT Test Applid TS 5.2.0
VSE users running IP version see the above screen with the Port column added:
The Port column contains the Listener Port defined in the Domain Applid record. A value of ‘?????’ in the Port column indicates
the Port value and IP address are unknown and should be added before attempting to target the corresponding Applid.
MBCMDMD MacKinney Batch to CICS 07/25/20 10:09:39

Mode: UPDATE Domain Directory Applid: DBDCICSA
Enter E-edit C-copy D-del or V-view selected Applid
*_______ <-Filter
S Applid Description Port Exec User
DBDCICSA Production Applid TS 5.2.0 05200 DBDCICSA
DBDCCICB Production Applid TS 5.2.0 05220 DFHCICCB
DBDCCICT Test Applid TS 5.2.0 ?????
Press PF6/PF18 to add a new Applid PF8/PF20 to scroll forward, PF7/PF19 to scroll backward, or PF3/PF15 to return back to
the previous screen. Each entry may be selected for Update, Copy, Delete or View by entering an ‘E’, ‘C’, ‘D’ or ‘V’ in the S
column before the entry.
To add a new Applid, press PF6 and the Domain Update screen shown in Section 3.10.2 is presented. Enter the Applid and
Description. For the VSE users running the IP version, also enter the Listener Port and IP Address.

3.10.2 Domain Update Screen
The Domain Update Screen lets you define the Applid and Applid Description to the Domain Applid Record. Users running
the IP version, also define the Port, IP Address and optional IP Exec Userid for the Applid as well.
MBCMDME MacKinney Batch to CICS 07/25/20 14:20:22

Mode: UPDATE Domain Update Applid: DBDCICSA
Overtype fields. Press PF3 to save or PF12 to cancel changes.
Applid : DBDCICSA Applid to be included in the domain of above BATCNTL
Applid Desc : PRODUCTION APPLID FOR TS 5.2.0 Applid Description
Last Update User: CICSUSER Date: 09/11/2019 Time: 14:20:38
PF1=Help PF3=Save PF12=Cancel
Users running IP version see the above screen with additional fields IP Port and IPV4 Address:
MBCMDME MacKinney Batch to CICS 07/25/20 14:20:22

Mode: UPDATE Domain Update Applid: DBDCICSA
Overtype fields. Press PF3 to save or PF12 to cancel changes.
Applid : DBDCICSA Applid to be included in the domain of above BATCNTL
Applid Desc : PRODUCTION APPLID FOR TS 5.2.0 Applid Description
Options for MBC TCP/IP version

IP Exec User: DBDCICSA Force Execution Userid on all commands to this Applid
IP Port : 05200 PORT Number of CICS Listener for Applid
Read Sel T/O: 030 Specify seconds to wait before timing out socket (030-999)
Stack is IPV: 4 Specify (4-IPV4 |6-IPV6)
Applid Address Specify target address below

IPV4 Address: 192 . 168 . 001 . 001
IPV6 Address: 0000 : 0000 : 0000 : 0000 : 0000 : 0000 : 0000 : 0001
Last Update User: CICSUSER Date: 09/11/2019 Time: 14:20:38
PF1=Help PF3=Save PF12=Cancel
Enter below fields then press PF3 to save changes or PF12 to cancel.
APPLID - Enter the Applid to include in the Domain Applid Record for the BATCNTL file listed (no wildcards).
APPLID DESC - Specify a description (up to 42 chars) to help identify the Applid.
IP EXEC USER – Specify a Userid to use as the IP Execution Userid for all commands to the Applid. Leave blank (default) to
use the MBCBATCH job submitter as the IP Execution Userid. If installation option EXTSEC=N, the Listener Userid is used
as the IP Execution Userid. The Userid is any valid Userid including the CICS Region Userid. NOTE: If surrogate checking
is active, the Listener Userid must have surrogate authority to start the IP Execution Userid.
IP PORT - Specify the PORT number defined for the CICS Listener for Applid (use CICS transaction EZAC to help
determine this value).
READ SEL T/O - Specify number of seconds (030-999) to wait before timing out socket. Default value is 30 seconds.
STACK IS IPV – Specify 4 (IPV4) or 6 (IPV6). You must be running a TCPIP stack supporting IPV6 if you specify 6.
IPV4|IPV6 ADDRESS - Specify the IP address (either IPV4 or IPV6) defined for the host stack. The loopback address can be
used if commands are not sent to a target CICS outside of the local stack.

3.10.3 Domain Applids via Batch (MBCBDOM)
Batch utility MBCBDOM allows you to list, delete and define Domain Applid group records in the BATNCTL file.
Sample JCL is in source member MBCJDOM. The format of the column specific control cards are listed below. Multiple
cards can be input in the same job.
column 8 17 23
DELDOM aaaaaaaa|ALL
DEFDOM aaaaaaaa description___________up_to_36_bytes uuuuuuuu ttt
DEFTCP aaaaaaaa ppppp nnn.nnn.nnn.nnn {IPV4}
DEFTCP aaaaaaaa ppppp nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn {IPV6}
LSTDOM aaaaaaaa|ALL
USEPCH
DELDOM – delete individual or all Domain Applid(s) information including optional TCPIP parameters
DEFDOM – define Domain Applid, description and optional IP Exec Userid (IPVERS=Y)
DEFTCP – define TCP card. A DEFTCP card must follow DEFDOM card for matching Applid (IPVERS=Y only)
LSTDOM – list individual or all Domain Applid(s) information including optional TCPIP parameters
USEPCH - creates DEF* cards from LSTITM and LSTALL options in SYSPCH DD or DLBL (see TIP! Below)
aaaaaaaa – Applid aaaaaaaa for the Domain record to define (DEFDOM) or delete (DELDOM). Begins in col 8 for max 8 bytes.
description – Applid domain description. Begins in col 17 for max 36 bytes.
uuuuuuuu – Optional IP Exec Userid to use for all Commands passed to Applid. Leave blank to default to use MBCBATCH job
submitter as the IP Exec Userid. If EXTSEC=N, then the IP Listener Userid is the Execution Userid.
ttt – Optional IP Read Select timeout value in seconds (030-999). Leave blank to default to 030 seconds. Parameter ignored if
IPVERS=N.
ppppp – Listener port number for Applid (use transaction EZAC to determine value). All 5 positions must be filled. Fill with
leading zeroes if necessary. Value must not be zero. Begins in col 17.
nnn.nnn.nnn.nnn – TCP/IPV4 address for host stack. Fill each octet with leading zeroes if necessary. Begins in col 23
nnnn:...:nnnn – TCP/IPV6 address for host stack. Fill each octet with leading zeroes if necessary. Begins in col 23.
TIP! You can use the LSTDOM function to create a batch backup. Copy and paste the LSTDOM and ---TCP lines created
on the report output, perform a “change all LST and --- prefix to DEF prefix” or use USEPCH option. Then use the altered
cards or SYSPCH file as input for DEFDOM and DEFTECP entries.
Example 1: Delete Domain Applid DBDCICSA, define Domains Applids DBDCICSA (IPV4) and DFHCICSB (IPV6)
with TCP/IP data for each Applid, and list all domains.
DELDOM DBDCICSA
DEFDOM DBDCICSA PRODUCTION APPLID ‘A’ TS 5.2.0
DEFTCP DBDCICSA 05210 192.168.000.001
DEFDOM DFHCICSB PRODUCTION APPLID ‘B’ TS 5.2.0
DEFTCP DFHCICSB 05220 0000:0000:0000:0000:0000:0000:0000:0001
LSTDOM ALL
MACKINNEY BATCH TO CICS - RELEASE x.x PAGE 1

BATCNTL DOMAIN APPLID UTILITY 10/25/2019
DELDOM DBDCICSA
1 DOMAIN REC(S) DELETED
DEFDOM DBDCICSA PRODUCTION APPLID ‘A’ TS 5.2.0 <OK

DEFTCP DBDCICSA 05200 192.168.000.001 <OK
1 DOMAIN REC(S) ADDED
DEFDOM DFHCICSB PRODUCTION APPLID ‘B’ TS 5.2.0 <OK

DEFTCP DBDCICSA 05220 0000:0000:0000:0000:0000:0000:0000:0001 <OK
1 DOMAIN REC(S) ADDED
LSTDOM ALL <OK

LSTDOM DBDCICSA PRODUCTION APPLID ‘A’ TS 5.2.0
---TCP DBDCICSA 05200 192.168.000.001
LSTDOM DFHCICSB PRODUCTION APPLID ‘B’ TS 5.2.0
---TCP DFHCICSB 05220 0000:0000:0000:0000:0000:0000:0000:0001
2 DOMAIN REC(S) LISTED
BATCNTL DOMAIN APPLID UTILITY ENDING MAXCC(000)

Section IV
Batch Programs and Procedures
4.1 Batch Client (MBCBATCH) Overview
MacKinney Batch to CICS uses EXCI (z/OS) or TCP/IP (VSE) to communicate commands between the batch client
(MBCBATCH) and the CICS server (MBCPXCI). When the batch job step begins, a pipe connection must be opened
with the CICS Applid(s) identified on the CICS card. IRC must be enabled on the target CICS before the pipe can be
successfully opened. A sample batch job log of an EXCI client session is shown in Section 4.1.3.
Before running MBCBATCH the first time, the Installation Options Batch Options should be updated online (see
Administration, Installation Options). These options control the flow of commands and responses to MBCBATCH.
MBCBATCH has an internal Enqueue mechanism which is designed to single-thread commands to each CICS system.
Therefore, multiple MBCBATCH steps can run simultaneously, but can only send commands to the same CICS system
one at a time. If you need to Enqueue across systems, set option ENQSX to ‘Y’ (Section 1.6.2).
There are six options allowing you to control the condition code set when errors occur: ERRWARN – a warning error
occurs; ERRDOWN – CICS is down; ERRDRLS – all CICS regions targeted by RLS1GRP are down; ERRCMD – a
command error occurs; ERRSEC – a security error occurs; ERRCNCL – step is canceled and ERRSTS – an error
during BATSTAT processing. See Section 4.1.2 and Section 3.4 for further details.
There are three options allowing you to automate actions when there are failures: DOWNNON – non-specific CICS
header Applid is down including ALL, @APPLGRP and @RLS1GRP; DOWNSPC – specific CICS header Applid is
down; FAILACT – command error. DOWNSPC and DOWNNON allow you to provide a different action for requests
to a specific header (i.e. CICS DBDCCICS) verses requests to a non-specific header (i.e. CICS @APPLGRP
MYAPPLGRP which might contain a mix of CICS Applid’s both up and down). See Section 3.4 for further details.
Specify ‘N’ for the CEDACMD to disallow the CEDA and CDAL commands. Set option SHUTCMD to ‘Y’ to allow
the SHUT command (which initiates a CICS shutdown). Specify ‘N’ for the SHUTCMD to disallow the SHUT
command. You can also restrict users from initiating other CEMT PERFORM commands with the CEMTPERF
option. See Section 3.4 for further details.
Sample JCL is provided in member MBCJBAT (Section 1.8.1). The recommended way to target commands to a
specific CICS system is to use a CICS header card (see CICS command description in Section 5.2). Below is an
example CICS header card:
CICS DBDCCICS => send following commands to the system where DBDCCICS is the defined Applid
All commands following the header card are targeted to the CICS associated with the preceding header card until a new
header card is detected. Valid commands are documented in Section 5 of this manual. If you have a set of commands
to send to multiple CICS Applids, you can use ApplGrps (Section 3.6). An example CICS header card for an ApplGrp
is:
CICS @APPLGRP MYAPPLIDGRP => send following commands to all the Applids defined in ‘MYAPPLIDGRP’
Section IV – Batch Programs and Procedures 103

4.1.1 Linking to MBCBATCH from your Application
There are two sample programs, SAMPLNK and SAMPLNK2, which demonstrate how to dynamically link to
MBCBATCH from your application. You can use this method if you have a very long running batch job not needing
the files closed until late in the process. See the source code for additional information on using this method. You can
also use the Online Command Processor API link interface to process commands from your CICS application programs
(see Section 6.2.1).
4.1.2 MBCBATCH Return Codes

MBCBATCH uses two return code variables, LASTCC and MAXCC. Most MBC commands set a LASTCC value
depending on if the command encountered an error (<ERR) or not (<OK). When the command is complete, the
LASTCC value is compared to the MAXCC value and if the new LASTCC value is greater, then MAXCC is updated.
When all commands are executed, the MBCBATCH step ends with the MAXCC return code value. If no errors are
present then MAXCC is set to zero. The command flow can be altered using IF/ELSE/ENDIF logic to interrogate the
LASTCC and MAXCC values. The MAXCC value is overridden with the SET command using IF/ELSE/ENDIF logic.
Installation Options ERRWARN(0), ERRDOWN (4), ERRDRLS (6), ERRCMD (8), ERRSEC (12), ERRCNCL (16)
and ERRSTS (0) determine the LASTCC values by error type. The LASTCC value for each of the options can be
modified to fit the requirements of your JCL. ERRSTS (0) is only applicable for users with Status Tracking enabled
(Section 7.1). Installation option variables are explained below:
• ERRWARN (0) – Set if MBC detects a warning condition executing certain inquiry commands (QRYL, QRYS,
CEMT INQ, CEDA, CDAL) when resources are not found or if errors occur processing generic commands.
• ERRDOWN (4) – Set if MBC is unable to connect to any target CICS. ERRDOWN can be ignored by setting
DOWNSPC to ‘B’ (bypass) for a down error occurring for a specific header or DOWNNON to ‘B’ (bypass) for a
down error occurring for a non-specific header (CICS ALL or APLGRP).
• ERRDRLS (6) – Set when a pipe cannot be opened for any of the target CICS APPLIDS identified by an
@RLS1GRP APLGRP. ERRDRLS will be ignored by setting DOWNNON to ‘B’ (bypass).
• ERRCMD(8) – SET if MBC encounters an error processing a batch command.
• ERRSEC (12) – Set if MBC detects a security error either while tring to connect or while executing a command.
• ERRCNCL (16) – Set if MBC cannot continue. This is usually because of operator action, but several installation
options have cancel as a possible action (FAILACT, DOWNNON and DOWNSPC). A missing DD statement also
results in this error.
• ERRSTS (0) – Set if MBC encounters an error during Status Tracking.
WARNING! Changing ERRSTS to a non-zero value may prevent your batch jobs from executing even when
there may be no errors in the execution phase (i.e. all files were successfully closed).
See sample return code exit MBCBCRCX (Section 4.3.6), for information on altering return code values.
104 Section IV – Batch Programs and Procedures

4.1.3 Sample Batch Job Log
Below is a sample MBCBATCH job log of an EXCI session. Any messages created by an executing command should
follow the actual command. Each command has an indicator such as <OK, <WARN or <ERR indicating the success or
failure of the command.
MACKINNEY BATCH TO CICS RELEASE 2.1 LEVEL SET(00)

{Options portion of log displays the current installation options}
OPTS: PREFIX (MBC) CMDEXIT (N) CLOSDIS (Y) CLOSRQST(N) TDMESGQ (CSMT)
OPTS: ERRDOWN(004) DOWNNON (F) DOWNSPC(F) APPLSTS (N) CLOSRTRY (002)
OPTS: ERRDRLS (006) FAILACT (G) LOGXDD (Y) EMTMSGS (A) CEMTRTRY (001)
OPTS: ERRCMD (008) EXTSEC (N) DOMSEC (N) CEMTPERF (N) STATRTRY (002)
OPTS: ERRSEC (012) STATFLAG (Y) SHUTCMD(N) STRTUPMG(Y) TRKNONFI (Y)
OPTS: ERRCNCL (016) CEDACMD (Y) ENQXS (N) RLUPDIS (N) IPVERS (N)
OPTS: ERRSTS (000)
{Job step starting displays job name and userid}
MBCB001-MBCBATCH 2.1 STARTING JOB(JOB12345:MBC$RUN) USER(RJS1) 07/25/20 14:12:21 MBCRXCI x.x RJS1
{Pre-processing phase reads cards and displays format errors}
MBCB003-COMMAND PRE-PROCESSING STARTING 07/25/20 14:12:21 MBCRXCI x.x RJS1
{Execution phase processes cards using EXCI}
MBCB004-COMMAND EXECUTION PHASE STARTING USING EXCI 07/25/20 14:12:21 MBCRXCI x.x RJS1
{Sample header card followed by connection complete message with Execution User}
CICS T540 <HDR 07/25/20 14:12:21 MBCZAPL x.x RJS1
MBCB020-CONNECTION COMPLETE TO APPL(T540 ) XUSR(RJS1 )
{Sample command was ok. No extra explanation message was available}
CLOS EML* <OK 07/25/20 14:12:21 MBCRXDPL x.x RJS1
{Sample command was ok. Explanation message follows the command}
MESG T05B CLOS WAS GOOD <OK 07/25/20 14:12:22 MBCRXDPL x.x RJS1
MBCE122-MESG ROUTED TO: T05B 07/25/20 14:12:22 MBCRXDPL x.x RJS1
{Sample command message indicating a completion with a warning. Explanation message follows the command}
CLOS EML*Z <WARN 07/25/20 14:12:23 MBCRXDPL x.x RJS1
MBCE110-NO FILES MATCHING EML*Z WERE FOUND 07/25/20 14:12:23 MBCRXDPL x.x RJS1
{Sample command failed. Explanation message follows the command}
CLOS EMLZZZ <ERR 07/25/20 14:12:23 MBCRXDPL x.x RJS1
MBCE111-FILE EMLZZZ NOT FOUND IN TABLES 07/25/20 14:12:23 MBCRXDPL x.x RJS1
{Sample MBC message indicating Close Pipe is complete}
MBCB022-CLOSE CONNECTION COMPLETE FOR APPL(T540) 07/25/20 14:12:23 MBCRXCL x.x RJS1
{Sample Status Tracking messages}
MBCB010-BATSTAT PROCESSING STARTING 07/25/20 14:12:24 MBCRXCI x.x RJS1
MBCB011-BATSTAT RESOURCE UPDATES COMPLETED FOR FOLLOWING COMMANDS 07/25/20 14:12:24 MBCRSTS x.x RJS1
MBCB012-UPDATED RESOURCE APPL:T540 TYPE:FI NAME:EML* 07/25/20 14:12:24 MBCRSTS x.x RJS1
MBCB013-CMD:CLOS EML* 07/25/20 14:12:24 MBCRSTS x.x RJS1
{Job step ending message displays the highest MAXCC value}
MBCB002-MACKINNEY BATCH TO CICS 2.1 ENDING MAXCC(008) 07/25/20 14:12:24 MBCRXCI x.x RJS1

Below is a sample MBCBATCH job log of a TCP/IP session. Any messages created by an executing command should
follow the actual command. Each command has an indicator such as <OK, <WARN or <ERR indicating the success or
failure of the command.

OPTS: ERRCNCL (016) CEDACMD (Y) ENQXS (N) RLUPDIS (N) IPVERS (Y)
OPTS: ERRSTS (000)
MBCB001- MBCBATCH 2.1 STARTING JOB(JOB12345:MBC$RUN ) USER(RJS1) 07/25/20 14:12:21 MBCRXCI x.x RJS1
MBCB003-COMMAND PRE-PROCESSING STARTING 07/25/20 14:12:21 MBCRXCI x.x RJS1
{Execution phase processes cards using TCP/IP}
MBCB004-COMMAND EXECUTION PHASE STARTING USING TCPIP 07/25/20 14:12:21 MBCRXCI x.x RJS1
{Sample header card followed by connection complete message}
CICS DBDCICSA <HDR 07/25/20 14:12:21 MBCRZAPL x.x RJS1
MBCB170-IP CONNECTION COMPLETE TO APPL(T540) PORT(1295) XUSR(RJS1 ) 07/25/20 14:12:21 MBCRXDPL x.x RJS1
{Sample command was ok. No extra explanation message was available}
CLOS EML* <OK 07/25/20 14:12:21 MBCRXDPL x.x RJS1
{Sample command was ok. Explanation message follows the command}
MESG T05B CLOS WAS GOOD <OK 07/25/20 14:12:22 MBCRXDPL x.x RJS1
MBCE122-MESG ROUTED TO: T05B 07/25/20 14:12:22 MBCRXDPL x.x RJS1
{Sample command message indicating a completion with a warning. Explanation message follows the command}
CLOS EML*Z <WARN 07/25/20 14:12:23 MBCRXDPL x.x RJS1
MBCE110-NO FILES MATCHING EML*Z WERE FOUND 07/25/20 14:12:23 MBCRXDPL x.x RJS1
{Sample command failed. Explanation message follows the command}
CLOS EMLZZZ <ERR 07/25/20 14:12:23 MBCRXDPL x.x RJS1
MBCE111-FILE EMLZZZ NOT FOUND IN TABLES 07/25/20 14:12:23 MBCRXDPL x.x RJS1
{Sample MBC message indicating Close Pipe is complete}
MBCB172-CLOSE SOCKET COMPLETE FOR APPL(T540 ) 07/25/20 14:12:23 MBCRXCL x.x RJS1
MBCB010-BATSTAT PROCESSING STARTING 07/25/20 14:12:24 MBCRXCI x.x RJS1
MBCB011-BATSTAT RESOURCE UPDATES COMPLETED FOR FOLLOWING COMMANDS 07/25/20 14:12:24 MBCRSTS x.x RJS1
MBCB012-UPDATED RESOURCE APPL:T540 TYPE:FI NAME:EML* 07/25/20 14:12:24 MBCRSTS x.x RJS1
MBCB013-CMD:CLOS EML* 07/25/20 14:12:24 MBCRSTS x.x RJS1
MBCB002-MACKINNEY BATCH TO CICS 2.1 ENDING MAXCC(008) 07/25/20 14:12:24 MBCRXCI x.x RJS1

4.2 Batch Utilities
There are several batch utilities provided to assist in supporting MacKinney Batch to CICS including BATCNTL
utilities MBCBCUTL (Section 4.2.1) and MBCBCPRT (Section 4.2.6), Applid Group utility MBCBAGRP (Section
3.6.5), Resource Item utility MBCBRITM (Section 3.7.4), Resource Group utility MBCBRGRP (Section 3.8.8),
Domain Applid Record utility MBCBDOM (Section 3.10.3), BATCNTL conversion utility MBCBCNV (Section 1.7.2
and Section 4.2.2), BATSTAT conversion utility MBCBCNVS (Section 1.9.1 and Section 4.2.3), and Resource Group
Item conversion utility MBCBCNVR (Section 4.2.4).
The optional Status Tracking function also has two batch utilities including BATSTAT Maintenance Utility
MBCBSUTL (Section 7.3.1) and Pre-CICS Startup Utility MBCBCPRE (Section 7.3.2).
All MBC batch utilities allow you to specify a comment by placing an ‘*’ in column 1
4.2.1 MBCBCUTL
MBCBCUTL is a batch utility for administering options and passwords on the BATNCTL file. Functions INIT, PASS
and DPWD each require exclusive access to the BATCNTL file (file must not be open for update in any CICS region).
Sample JCL is in source member MBCJCUTL. The format of supported control cards are listed below. Multiple cards
can be input in the same job
LIST OPTS|PWDS List options or passwords in the report.

PASS n pppppppppppppppp Add or update a password in specified password slot (see NOTE 1 below).
DPWD n Delete a password in specified password slot.
INIT OPTS Can be used to initialize options if Option record does not already exists
INIT {option}({value}) See Section 3.4 for option names and acceptable values (see NOTE 2 below)
n - identifies password slot (1-6) used to add or modify (PASS) or delete (DPWD)
pppppppppppppppp – identifies password value to add or modify (PASS) or delete (DPWD)
NOTE 1: MBCBCUTL performs an implicit INIT OPTS if the options record does not exist when processing a PASS card
NOTE 2: Because of security concerns the following options are restricted: EXTSEC | DOMSEC can only be
initialized to 'Y'; CEMTPERF | SHUTCMD | CEDACMD can only be initialized to 'N'.
Example cards
PASS 1 1234567890123456
INIT ERRWARN(000)
INIT STATRTRY(001)
INIT EXTSEC(Y)
LIST OPTS
LIST PWDS
Example MVS JCL

//STEP1 EXEC PGM=MBCBCUTL
//STEPLIB DD DSN=your.MBCxx.LOADLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//BATCNTL DD DSN=your.BATCNTL,DISP=SHR
//SYSIN DD *
PASS 1 1234567890123456
LIST PWDS
/*
Example VSE JCL

// JOB MBC$CPRT BATCH UTILITY
// LIBDEF PHASE,SEARCH=your.MBCxx.LOADLIB
// DLBL BATCNTL,'your.BATCNTL',,VSAM,CAT=yourCAT
// EXEC MBCBCUTL
PASS 1 1234567890123456
LIST PWDS
/*

Example 1 Output: List the Installation Options.
LIST OPTS
USR:MYUSERID MACKINNEY BATCH TO CICS - RELEASE x.x PAGE 1

DSN:MACS.MBC.BATCNTL BATCNTL ADMIN UTILITY 07/25/2020
LIST OPTS <OK

OPTS: ERRDRLS(006) FAILACT (G) LOGXDD (Y) EMTMSGS (A) CEMTRTRY(001)
OPTS: ERRCMD (008) EXTSEC (N) DOMSEC (N) CEMTPERF(N) STATRTRY(002)
OPTS: ERRSTS (000)
INPUT CARDS PROCESSED: 1
BATCNTL ADMIN UTILITY ENDING MAXCC(000)
Example 2 Output: Modify BATCNTL password in slot 3 to 1234567890123456 and delete password in slot 4.
PASS 3 1234567890123456
DPWD 4
USR:MYUSERID MACKINNEY BATCH TO CICS - RELEASE x.x PAGE 1

DSN:MACS.MBC.BATCNTL BATCNTL ADMIN UTILITY 07/25/2020
MBCB042-UPDATE FOR PASSWORD(3) VALUE(1234567890123456) SUCCESSFUL

MBCB042-DELETE FOR PASSWORD(4) VALUE( ) SUCCESSFUL
INPUT CARDS PROCESSED: 2
BATCNTL ADMIN UTILITY ENDING MAXCC(000)

4.2.2 MBCBCNV
MBCBCNV is a batch utility for converting the BATCNTL file used in the CEMT from Batch product to a format
compatible with MacKinney Batch to CICS. The utility is one step of a two-step job, MBCJCNV. Sample JCL is in
source member MBCJCNV. For more information on MBCJCNV, refer to Section 1.7.2. There are no parameters for
this utility. Verify and update your old installation options before running the conversion utility MBCBCNV.
Below is sample output of the MBCBCNV step:

BATCNTL FILE CONVERSION 10/25/2019
OLDBAT OPEN RC(0)

DSN FOR OLDBAT: YOUR.CEMT.BATCNTL
NEWBAT OPEN RC(0)
DSN FOR NEWBAT: YOUR.MBC.BATCNTL
READ OLDBAT OPTIONS RC(0)
WRITE NEWBAT OPTIONS RC(0)
CONVERTED OPTIONS
OPTS: ERRDRSL(006) FAILACT (G) LOGXDD (Y) EMTMSGS (A) CEMTRTRY(001)
OPTS: ERRCMD (008) EXTSEC (N) DOMSEC (N) CEMTPERF(N) STATRTRY(002)
OPTS: ERRSTS (000)
WRITE NEWBAT APPLIDS RC(0)

BATCNTL CONVERSION SUCCESSFUL
BE SURE TO REVIEW CONVERTED OPTIONS CAREFULLY - SEE MANUAL
4.2.3 MBCBCNVS
MBCBCNVS is a batch utility for converting the BATSTAT file used in the CEMT from Batch product to a format
compatible with MacKinney Batch to CICS. Sample JCL is in source member MBCJCNVS. For more information on
MBCJCNVS, refer to Section 1.9.1.
WARNING! All converted records assume the authority of the Userid submitting the utility. The Userid is overridden
by supplying PARM=’userid’ in the MBCBCNVS JCL.
Below is sample output of the MBCBCNVS step:

BATSTAT FILE CONVERSION 10/25/2019
OLDSTS OPEN RC(0)

DSN FOR OLDSTS: YOUR.CEMT.BATSTAT
NEWSTS OPEN RC(0)
DSN FOR NEWSTS: YOUR.MBC.BATSTAT
USERID FOR CONVERSION RECORDS: YOURUSER {job submitter or PARM= value on EXEC card}
TOTAL RECORDS CONVERTED: 4
BATSTAT FILE CONVERSION ENDING MAXCC(000)

4.2.4 MBCBCNVR
MBCBCNVR is a batch utility for converting Resource Group Items from pre-MBC 2.0 BATCNTL file to Resource
Items valid with MBC 2.0 and after. You can also use batch utility MBCBRITM for defining Resource Items. This
utility should only be run one-time per BATCNTL file. Sample JCL is in source member MBCJCNVR.
Below is sample output of the MBCBCNVR step:

DSN:MACS.MBC.BATCNTL MBC RESOURCE CONVERSION 10/25/2019
CONVERTING RECORD(S) FOR APPL(T420 ) GROUP(BAT )

FI SMGFILE 0010 ADDED
TR SMGA 0020 ADDED
TR SMGB 0030 ADDED
PG SMGPADM 0040 ADDED
4 RECORD(S) ADDED TO APPL(T420 ) GROUP(SMGGRP )
MBC RESOURCE CONVERSION ENDING MAXCC(000)
4.2.5 MBCBCNV2
MBCBCNV2 is a batch utility for converting BATSTAT records from pre-MBC 2.0 to BATSTAT records valid with
MBC 2.0 and after. This utility should only be run one-time per BATSTAT file. Sample JCL is in source member
MBCJCNV2.
Below is sample output of the MBCBCNV2 step:

DSN:MACS.MBC.BATCNTL MBC RESOURCE CONVERSION 10/25/2019
CONVERTING RECORD(S) FOR APPL(T420 ) GROUP(BAT )

FI SMGFILE 0010 ADDED
TR SMGA 0020 ADDED
TR SMGB 0030 ADDED
PG SMGPADM 0040 ADDED
4 RECORD(S) ADDED TO APPL(T420 ) GROUP(SMGGRP )
MBC RESOURCE CONVERSION ENDING MAXCC(000)

4.2.6 MBCBCPRT
MBCBCPRT is a batch utility for printing reports based on the BATNCTL file. There are cross reference reports for
Applids within ApplGrp BATCNTL records and resources within Resource Group BATCNTL records. Sample JCL is
in source member MBCJCPRT. The format of the column specific control card are listed below. Multiple cards can be
input in the same job
XREF AGRP aaaaaaaa Cross reference ApplGrp report

XREF RGRP tt rrrrrrrr Cross reference Resource Group report for Applid by Group
aaaaaaaa – Applid for ApplGrp or Resource Group

tt rrrrrrrr – identifies resource type (tt = FI-file|PG-program|TR-tranid|TD-TDQ|TX-Ext TDQ|IP-TCPIP service) and 8-
character (FI|PG|IP) or 4-character (TR|TD|TX – blank filled) resource name to print for the Resource Group report. One
blank separates the two parameters.
Example 1: Find all Resource Groups containing resource file SNTFIL$ in the BATCNTL file.
XREF RGRP FI SNTFIL$

DSN:MACS.MBC.BATCNTL BATCNTL PRINT UTILITY 07/25/2020
INPUT: XREF RGRP FI SNTFIL$
APPLID GROUP NAME GROUP DESCRIPTION SEQ TYPE NAME

DBDCCICS TESTGROUP TEST GROUP 0020 FI SNTFIL$
DBDCICS2 TESTGROUPALT ALTERNATE TEST GROUP 0120 FI SNTFIL$
DBDCICS3 CICS3GROUP GROUP FOR CICS3 0040 FI SNTFIL$
Example 2: Find all ApplGrps containing Applid DBDCCICS in the BATCNTL file.
XREF AGRP DBDCCICS

DSN:MACS.MBC.BATCNTL BATCNTL PRINT UTILITY 07/25/2020
INPUT: XREF AGRP DBDCCICS
APPLGRP DESCRIPTION APPLID CHG USER CHG DATE

AGRPCICSTST TEST APPLID GROUP DBDCCICS CICSUSER 08/12/2019
AGRPCICSTS2 TEST TS 5.* APPLGROUP DBDCCICS CICSUSER 06/24/2019
AGRPCICS3 GROUP FOR CICS3 DBDCCICS CICSUSER 03/11/2019

4.3 Batch User Exits
There are several batch user exit provided to help in customizing MacKinney Batch to CICS to better suit
your environment. The CICS header exit MBCBHDRX (Section 4.3.1), the command exit MBCBCMDX
(Section 4.3.2), the pre-execution exit MBCBPREX (Section 4.3.3), the batch job log exit MBCBLOGX
(Section 4.3.4), the command return-code exit MBCBCRCX (Section 4.3.6) the z/OS-only BATSTAT open
exit MBCBOPSX (Section 4.3.7), and the pre-WTO exit MBCBWTOX (Section 4.3.8). These exits must be
present in your MBC loadlib at execution.
4.3.1 Header Exit MBCBHDRX

The CICS header exit allows you to modify the target CICS header value or deny access from the current
USERID. The exit is passed the USERID plus the 8-byte CICS header value: a specific Applid,
‘@APPLGRP’ identifying an ApplGrp or ‘ALL’. If the Applid value is ‘@APPLGRP’, a third parameter
identifying the 12-byte ApplGrp name is also passed. See the sample source MBCBHDRX for additional
details on using this exit. Assemble and link changes into the MBC loadlib.
4.3.2 Command Exit MBCBCMDX

The command exit allows you deny or alter the command or allow your own command (bypassing the
normal edits). The exit is passed the 80-byte command card, the 8-byte Applid and optional ApplGrp name,
plus the 8-byte USERID. See the sample source MBCBCMDX for additional details on using this exit.
Assemble and link changes into the MBC loadlib.
4.3.3 Pre-Execution Exit MBCBPREX

The pre-execution exit is similar to the CICS header exit, but is called after the specific target Applid is
determined. The exit is passed the USERID plus the 8-byte target Applid and allows you to deny the
command, alter the command or allows your own command (bypassing the normal edits). The exit is
passed the 80-byte command card, the 8-byte Applid and optional ApplGrp name, plus the 8-byte USERID.
See the sample source MBCBPREX for additional details on using this exit. Assemble and link changes
into the MBC loadlib.
4.3.4 Job Log Exit MBCBLOGX

The MBCBATCH job log exit is called before a message is written to SYSLST. You can copy the message
to your own file, route it to the operator or suppress the message. The exit is passed a 2-byte message
binary length and an 80-byte message text. See sample source MBCBLOGX for additional details on using
this exit. Assemble and link changes into the MBC loadlib.
4.3.5 Extended Data Log Exit MBCBLXGX

The extended data log exit is called before extended data lines (Section 2.1.5) are written to SYSLSTX.
You can copy the line to your own file, route it to the operator or suppress the line. The exit is passed a 2-
byte message binary length and an 80-byte message text. See the sample source MBCBLXGX for
additional details on using this exit. Assemble and link changes into the MBC loadlib.

4.3.6 Command Return-code Exit MBCBCRCX
The exit is called when a non-zero return-code (LASTCC) is passed back from CICS after processing a
command. The exit is passed the 2-byte binary return code, 80-byte error message, 80-byte command and
8-byte APPLID. By setting the exit return code (R15), you can alter the default action which is to process
the message and initial return code value.
R15 = 8: LASTCC value for MBCBATCH is set to 0. The returned error message text is displayed,
including any modifications if the returned message is non-blank. Or you can space out the
passed message text to suppress logging the error.
R15 = 0: No changes are made to the LASTCC value or the message text returned from CICS.
See the sample source MBCBCRCX for additional details on using this exit. Assemble and link changes
into the MBC loadlib.
4.3.7 Open BATSTAT Exit MBCBOPSX (z/OS only)

The exit is called (z/OS only) before the BATSTAT file is opened to allow for dynamic allocation. The
BATSTAT file is only opened if you specify option STATFLAG=Y or APPLSTS is set to ‘Y’ or ‘F’. You
must specify the BATSTAT dataset name in the exit. See the sample source MBCBOPSX for additional
details on using this exit. Assemble and link changes into the MBC loadlib.
4.3.8 WTO Exit MBCBWTOX

The MBCBATCH WTO exit is called before a WTO message is written. You can copy the message to your
own file, alter the message text or suppress the message. The exit is passed a 2-byte message binary length
and an 80-byte message text. See sample source MBCBWTOX for additional details on using this exit.
Assemble and link changes into the MBC loadlib. The default exit returns without making any changes.

Section V
Command Descriptions and Syntax
MacKinney Batch to CICS allows commands to pass from a batch job stream to CICS and a response from CICS to pass back to
the batch job. This section lists the MBC commands and their syntax.
NOTE: All commands can have leading blanks. Most commands must be preceded by a CICS header card so the batch client,
MBCBATCH, knows where to send the command for processing. See the CICS command syntax in Section 5.2.
TIP! Use the OPEN and CLOS commands (rather than CEMT SET) to verify the file opens or closes successfully.
5.1 Command Summary

* Comment card
ALOC/ALOQ Allocate file(s)
ALOG/ALSG Allocate a Group of Resource Items
ALOR/ALSR Allocate Resource Item
APPL Update the APPLID table in the BATCNTL file
CDAL Send multi-line CEDA messages to CICS
CEDA Any valid CEDA command to CICS
CEMT PERFORM Any valid CEMT PERFORM command (except SHUT)
CEMT SET Any valid CEMT SET command
CEMT DISCARD Any valid CEMT DISCARD command
CEMT INQUIRE Any valid CEMT INQUIRE command
CICS Command header card
CLOS/CLOG Close file(s)
CLOV/CLVG Close and verify file(s)
CSDA Starts DL/I MPS (VSE only)
CSDD Stops DL/I MPS (VSE only)
DBLC Open or close Datacom/DB databases
DLOC Open or close DL/I databases (VSE only)
DOWNSTS Force status tracking processing On or Off
DSNC Start or stop the CICS-DB2 interface (z/OS only)
ENAB/ENAG Set file(s) enabled
GLSQ/GSSQ QUIESCE Primary or Secondary RLS dataset(s) (z/OS only)
GLSU/GSSU UNQUIESCE Primary or Secondary RLS dataset(s) (z/OS only)
IF/ELSE/ENDIF Allows conditional command processing
INQY/INQG Change file(s) to read-only
LINK/LNKL Link to a CICS program
MESG Send a message to a CICS terminal
MSGL Send a multi-line message to a CICS terminal
NEWC NEWCOPY a program
OPEN/OPEG Open file(s)
OPTR Override MBC Installation option
PHAS PHASEIN a new copy of a program
QRYL/QRYS Perform inquiry of CICS resources and return to batch
RLSQ QUIESCE RLS dataset(s) (z/OS only)
RPSQ/RSSQ QUEISCE Resource Item Primary or Secondary RLS dataset (z/OS only)
RLSU UNQUIESCE RLS dataset(s) (z/OS only)
RPSU/RSSU UNQUEISCE Resource Item Primary or Secondary RLS dataset (z/OS only)
RLQY/GLQY Change RLS file/dataset(s) to read-only (z/OS only)
RLUP/GLUP Change RLS file/dataset(s) from read-only to update (z/OS only)
RPQY/GPQY Change Primary RLS file/dataset(s) to read-only (z/OS only)
RPUP/GPUP Change RLS file using Primary dataset(s) from read-only to update (z/OS only)
RSQY/GSQY Change RLS file using Secondary dataset(s) to read-only (z/OS only)
RSUP/GSUP Change RLS file using Secondary dataset(s) from read-only to update (z/OS only)
SAPL Set Applid status (UP|DOWN) to override DOWNSPC or DOWNNON action
114 Section V – Command Descriptions and Syntax
SET Allows override of MAXCC and setting of user variables
SHUT Initiate CICS shutdown
STAR/STRL Start a CICS transaction
STAR DBOC Start a Datacom/DB DBOC transaction
STSG Synchronize BATCSTS status for all Resource Items in a group
STSR Synchronize BATCSTS status for a Resource Item
UNAG Unallocate a Group of Resource Items
UNAR Unallocate Resource Item
UNAL/UNAQ Unallocate file(s)
UPDT/UPDG Change file(s) from read-only to update
WAIT Delay between MBCBATCH commands
5.1.1 Related Commands
File Commands
ALOC/ALOQ Allocate file(s)

CLOS Close file(s)
CLOV Close and verify file(s)
ENAB Set file(s) enabled
INQY Change file(s) to read-only
OPEN Open file(s)
UNAL/UNAQ Unallocate file(s)
UPDT Change file(s) from read-only to update
Program/Transaction Commands
NEWC NEWCOPY a program

LINK/LNKL Link to a CICS program
PHAS PHASEIN a new copy of a program
STAR/STRL Start a CICS transaction
Resource Item Commands
ALOG/ALSG Allocate a Group of Resource Items

ALOR/ALSR Allocate Resource Item
CLOG Close the files in a Resource Group
CLOG Close and verify the files in a Resource Group
ENAG Enable a Group of Resource Items
INQG Change files in a Resource Group to read-only
OPEG Open files in a Resource Group
STSG Synchronize BATCSTS status for all Resource Items in a group
STSR Synchronize BATCSTS status for a Resource Item
UPDG Change files in a Resource Group from read-only to update
UNAG Unallocate a Group of Resource Items
UNAR Unallocate Resource Item
Utility Commands
CEMT PERFORM Any valid CEMT PERFORM command (except SHUT)

CEMT SET Any valid CEMT SET command
CEMT DISCARD Any valid CEMT DISCARD command
CEMT INQUIRE Any valid CEMT INQUIRE command
QRYL/QRYS Perform inquiry of CICS resources and return to batch
SHUT Initiate CICS shutdown
Section V – Command Descriptions and Syntax 115

RLS Commands (z/OS only)
GLSQ/GSSQ QUIESCE Primary or Secondary RLS dataset(s)

GLSU/GSSU UNQUIESCE Primary or Secondary RLS dataset(s)
RLSQ QUIESCE RLS dataset(s)
RPSQ/RSSQ QUEISCE Resource Item Primary or Secondary RLS dataset
RLSU UNQUIESCE RLS dataset(s)
RPSQ/RSSQ UNQUEISCE Resource Item Primary or Secondary RLS dataset
RLQY/GLQY Change RLS file/dataset(s) to read-only
RLUP/GLUP Change RLS file/dataset(s) from read-only to update
RPQY/GPQY Change Primary RLS file/dataset(s) to read-only
RPUP/GPUP Change RLS file using Primary dataset(s) from read-only to update
RSQY/GSQY Change RLS file using Secondary dataset(s) to read-only
RSUP/GSUP Change RLS file using Secondary dataset(s) from read-only to update
Database Commands
CSDA Starts DL/I MPS (VSE only)

CSDD Stops DL/I MPS (VSE only)
DBLC Open or close Datacom/DB databases
DLOC Open or close DL/I databases (VSE only)
DSNC Start or stop the CICS-DB2 interface (z/OS only)
STAR DBOC Start a Datacom/DB DBOC transaction
Miscelaneous Commands
* Comment card
APPL Update the APPLID table in the BATCNTL file
CICS Command header card
DOWNSTS Force status tracking processing On or Off
IF/ELSE/ENDIF Allows conditional command processing
MESG Send a message to a CICS terminal
MSGL Send a multi-line message to a CICS terminal
OPTR Override MBC Installation option
SAPL Set Applid status (UP|DOWN) to override DOWNSPC or DOWNNON action
SET Allows override of MAXCC and setting of user variables
WAIT Delay between MBCBATCH commands
5.2 Command Syntax
* (Comment)
* Any input with an asterisk in the first non-blank column is treated as a comment.
↑
Example 1: The second command in the below example illustrates a comment.
CICS DBDCCICS
* The following command targets the production payroll files
ALOG PRODPAYROLL

ALOC / ALOQ
ALOC ddd ffffffff nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
ALOQ ddd ffffffff nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn (z/OS only–uses SVC99)
(or)
ALOC ddd @lllllll
ALOQ ddd @lllllll (z/OS only–uses SVC 99)
The ALOC command allocates a file or a file list to CICS. File(s) will be enabled and opened.
The ALOQ command (z/OS only) allocates an Extrapartition TDQ file or file list to CICS using SVC99. The UNAQ command
must be used to unallocate a TDQ file allocated with ALOQ.
ddd - is the file disposition (SHR or OLD). This parameter is currently supported only for z/OS. VSE users should
specify SHR or OLD as a placeholder value. When used with a file list, the disposition applies to all files in the list.
ffffffff - is the CICS defined file name for ALOC or DCT for ALOQ.
nnn...nnn - is the dataset name (up to 44 chars). Do NOT enclose in quotes.
@lllllll – is a file list name defined in MBCFLIST (compatibility only).
NOTE: A TDQ is not automatically opened after an ALOQ command. See Section 2.1.7 Transient Data Queue Handling for
further details on TDQ handling. ALOC/UNAL commands are not required if using Dynamic File Allocation (non-blank
DSNAME specified for the RDO file definition, and no DD statement defined for the file in the CICS startup JCL).
ALOC SHR PAYMST PAY.MASTER.VS {allocate PAYMST file DISP=SHR with DSN=PAY.MASTER.VS }
ALOG / ALSG
ALOG gggggggggggg [aaaaaaaa]
ALSG gggggggggggg [aaaaaaaa]
The ALOG and ALSG commands allocate a group of MBC Resource Items (files, programs, transactions, TCPIP services
and/or TDQs) to CICS. ALOG and ALSG operate the same for all resource types except for files. For files (TYPE=FI), ALOG
allocates the file using Primary DSN1 and ALSG allocates the file using Secondary DSN2. For ALSG, DSN1 is used if DSN2
value is blank. For either command, files are enabled and opened depending on the Resource Option ‘Open on Aloc’ setting; all
programs, transactions, and TDQs are enabled; TCPIP services and Extrapartition TDQs are opened. See Section 3.8 for more
information on using Resource Groups. It is recommended to pair the ALOG or ALSG commands with a UNAG command.
gggggggggggg - is the MBC Resource Group name (up to 12 chars).

aaaaaaaa – Applid value (up to 8 chars) to use in the key for reading a Shared Resource Group. If not specified,
Applid defaults to the local connected region unless an @ApplGrp is present in the CICS command
header in which case use of the @ApplGrp is attempted first and if not found, then the local
connected region is used.
ALOG ACCTGRP {allocate ACCTGROUP resources; for files use primary DSN1 values}
ALSG PAYGRP {allocate PAYGROUP resources; for files use secondary DSN2 values}

ALOR / ALSR
ALOR tt nnnnnnnn [aaaaaaaa]
ALSR tt nnnnnnnn [aaaaaaaa]
The ALOR and ALSR commands allocate a single MBC defined Resource Item (file/program/transaction/TDQ) to CICS.
ALOR and ALSR operate the same for all resource types except for files. For a file (TYPE=FI), ALOR allocates the file using
Primary DSN1 and ALSR allocates the file using Secondary DSN2. For ALSR, DSN1 is used if the DSN2 is blank. Files are
enabled and opened depending on the Resource Option ‘Open on Aloc’ setting. For non-file commands, the resource is enabled.
For TCPIP Service and Extrapartition TDQ Resource Items, the resource is opened See Section 3.7 for more information on
using Resource Items. It is recommended to pair the ALOR/ALSR commands with an UNAR command.
tt – Resource Type (FI-File|PG-Pgm|TR-Tran|TD-TDQ|TX-Ext TDQ|IP-TCPIP Service)

nnnnnnnn – MBC Resource Item name (up to 12 chars).
aaaaaaaa – Applid value (up to 8 chars) to use in the key for reading a Shared Resource Item. If not specified, Applid
defaults to the local connected region unless an @ApplGrp is present in the CICS command header in
which case use of the @ApplGrp is attempted first and if not found, then the local connected region is used.
ALOR FI ACCTMST {allocate ACCTMST using primary DSN1 Resource Item value}
ALSR FI PAYMST {allocate PAYMST using secondary DSN2 Resource Item value}
APPL
APPL nn aaaaaaaa
Update the APPLID table in the BATCNTL file. This command is for compatibility purposes for CEMT from Batch users
requiring use of the APPLID table. Its use is not recommended for new MBC users. See Appendix E for additional explanation
of the APPLID table.
nn - the number of the CICS system; must be 2 digits (01 - 99).

aaaaaaaa - CICS Applid associated with CICS ‘nn’; 1-8 characters.
WARNING! This command requires exclusive control of the BATCNTL file, so the BATCNTL file cannot be open in any
CICS regions. Either verify the file is closed in all regions or use the following commands:
CICS DBDCCICS {specify region(s) where file is open}

CLOS BATCNTL
APPL 09 DBDCICS9
OPEN BATCNTL

CDAL
CDAL LINES=n
CEDA command line 1 (up to 80 characters)
CEDA command continuation line 2 (up to 80 characters)
Send a multi-line CEDA command to CICS to execute. See the discussion on the MBC CEDA command for details on
controlling where up to 400 lines of additional output is written.
LINES=n - tells how many 80-character lines immediately follow the CDAL command. ‘n’ must be 1-4
NOTE: For CEDA and CDAL commands, up to 400 lines are returned to the batch job log. Where the output is returned is
dependent on installation option, LOGXDD. See Section 2.1.5 for additional information on usage of the LOGXDD option
value. If 400 lines is not enough to contain the response data, use the CEDA command for a more specific resource (i.e. “A*”
instead of “*”).
Example 1: Define a new transaction MBCV pointing to program MBCPADM.
CDAL LINES=2
DEFINE TRANSACTION(MBCV) PROGRAM(MBCPADM)
GROUP(MACKMBC)
MBCB060-START OF CEDA MESSAGES

DEFINE TRANSACTION(MBCV) PROGRAM(MBCPADM)
GROUP(MACKMBC)
MBCX DEFINE TRANSACTION( MBCV )
TRANSACTION : MBCV
GROUP : MACKMBC
DESCRIPTION ==>
PROGRAM ==> MBCPADM
TWASIZE ==> 00000 0-32767
. . .
RSL : 00 0-24 | PUBLIC
DEFINITION SIGNATURE
DEFINETIME : 07/25/20 14:51:50
CHANGETIME : 07/25/20 14:51:50
CHANGEUSRID : RJS1
CHANGEAGENT : CSDAPI CSDAPI | CSDBATCH
CHANGEAGREL : 0690
MBCB061-END OF CEDA MESSAGES: LINES(0000065)
CDAL LINES=3 <OK

CEDA
CEDA {ADD
APPEND
DEFINE
DELETE
DISPLAY
EXPAND
INSTALL}
Use any valid CEDA command as specified in the CICS Supplied Transactions manual.
NOTE: For CEDA and CDAL commands, up to 400 lines are returned to the batch job log. Where the output is returned is
dependent on installation option, LOGXDD. See Section 2.1.5 for additional information on usage of the LOGXDD option
value. If 400 lines is not enough to contain the response data, use the CEDA command for a more specific resource (i.e. “A*”
instead of “*”).
Example 1: Install group MACKBTS.
CEDA IN GR(MACKBTS)
MBCB060-START OF CEDA MESSAGES

IN GR(MACKBTS)
MBCX INSTALL
ALL
ATOMSERVICE ==>
BUNDLE ==>
CONNECTION ==>
CORBASERVER ==>
DB2CONN ==>
DB2ENTRY ==>
DJAR ==>
DOCTEMPLATE ==>
ENQMODEL ==>
FILE ==>
IPCONN ==>
. . .
PIPELINE ==>
PROCESSTYPE ==>
PROFILE ==>
PROGRAM ==>
REQUESTMODEL ==>
SESSIONS ==>
TCPIPSERVICE ==>
TDQUEUE ==>
TERMINAL ==>
TRANCLASS ==>
TRANSACTION ==>
TSMODEL ==>
TYPETERM ==>
URIMAP ==>
WEBSERVICE ==>
GROUP ==> MACKBTS
LIST ==>
MBCB061-END OF CEDA MESSAGES: LINES(0000040)
CEDA IN GR(MACKBTS) <OK

CEMT PERFORM
CEMT PERFORM -
RESET
DUMP
SNAP
etc.}
Whether the PERFORM option is allowed is dependent on the CEMTPERF installation parameter. If CEMTPERF is set to ‘N’,
the CEMT PERFORM command is not allowed. Otherwise, specify any valid CEMT PERFORM command supported by the
target CICS except for CEMT PERFORM SHUT. To perform CICS shutdown, use the SHUT command (SHUT).
CEMT PERFORM RESET {sync up time with TOD clock}

CEMT PERFORM DUMP DUMPCODE(BTD0001) {perform a system dump}
CEMT SET / DISCARD / INQUIRE

CEMT SET|DISCARD|INQUIRE{ TRANSACTION
PROGRAM
DATASET
TERMINAL
etc.}
Use any valid SET, DISCARD or INQUIRE command as specified in the CICS Supplied Transactions manual.
NOTE: The amount of output and where output is returned is dependent on installation options, LOGXDD and EMTMSGS. If
EMTMSGS=A, additional output from ALL CEMT commands is returned to the batch job log. If EMTMSGS=Q, only additional
output from CEMT INQUIRE commands is returned to the batch job log. See Section 2.1.5 for additional information on the
LOGXDD option value. The additional output is limited to 400 lines. If 400 lines is not enough to contain the response data, useg
the CEMT command for a more specific resource (i.e. “A*” instead of “*”) or use the QRYL/ QRYS command for INQUIRE
commands supported by QRYL/QRYS. If neither option is viable, please contact MacKinney Systems to discuss your
requirements.
NOTES FOR CEMT SET: We recommend using the MBC OPEN and CLOS commands over CEMT SET for opening or
closing files (you still need to use CEMT SET for TDQs). We also recommend using PHAS or NEWC commands rather than
using CEMT SET to NEWCOPY or PHASEIN a program. The MBC internal commands have additional error handling and
messages you do not get with CEMT SET commands. For NEWCOPY or PHASEIN also see Section 2.1.2 for considerations
when AUTOINSTALLING programs.
Example 1: NEWCOPY program MBCPADM
MBCB060-START OF CEMT MESSAGES

CEMT SET PROG(MBCPADM) NEW
PROG(MBCPADM ) LEN(0000008784) ASS PRO ENA PRI CED RES(0000) USE(000000
0039) ANY UEX FUL QUA CIC NORMAL
LIB(DFHRPL ) LIB(MACS.MBC16.LOADLIB )
MBCB061-END OF CEMT MESSAGES: LINES(0000005)
CEMT SET PROG(MBCPADM) NEW <OK
Example 2: List all files for CICS Applid DBDCICSA beginning with DT* in long format
MBCB060-START OF CEMT MESSAGES

CEMT I FIL(BAT*)
FIL(BATCNTL ) VSA OPE ENA REA BRO SHA DSN( MACS.MBC.BAT
CNTL ) LOC MAX( 00000000 ) KEY( 044 ) REC( 08192 )
NSTALLT(07/25/20 09:15:33) INSTALLU(T540 ) GRP DEFINES(MACKMBC )
FIL(BATSTAT ) VSA OPE ENA REA UPD ADD BRO DEL SHA DSN( MACS.MBC.BAT
STAT ) LOC MAX( 00000000 ) KEY( 034 ) REC( 00138 )
NSTALLT(07/25/20 09:15:33) INSTALLU(T540 ) GRP DEFINES(MACKMBC )
MBCB061-END OF CEMT MESSAGES: LINES(0000009) RESOURCES(0000002)
CEMT I FIL(BAT*) <OK

CICS / CSCQ
CICS aaaaaaaa
CSCQ aaaaaaaa
(or)
CICS @APPLGRP gggggggggggg
CSCQ @APPLGRP gggggggggggg
(or)
CICS @RLS1GRP gggggggggggg
aaaaaaaa - specifies the CICS Applid of the CICS system where the commands are sent.
gggggggggggg - specifies an ApplGrp defined via the Administrative ApplGrp Directory screen (Section 3.6). This
parameter must be preceded by ‘@APPLGRP’ or ‘@RLS1GRP’.
If ‘@APPLGRP’ is specified, commands following the header card are sent to all Applids in the ApplGrp.
If ‘@RLS1GRP’ is specified, commands following the header card are sent to the first Applid to successfully connect in the
ApplGrp. Use only for RLS commands. If used for non-RLS or RLQY/GLQY/RLUP/GLUP commands, commands are only
sent to the first applid to successfully connect and not all applids in the ApplGrp.
CICS and CSCQ header cards designate the target CICS region(s) for commands that follow until the next header card or EOD.
CICS
Commands following the CICS header card are sent to target CICS regions for execution. You can intersperse multiple CICS
header cards amongst input cards to send commands to different CICS regions during one MBCBATCH execution.
CSCQ
Commands following the CSCQ header card are sent to target CICS regions for storing CICS Startup Commands in the
Startup Command Queue (Section 8.1). Startup Commands are stored in the region BATCSTS file. Do not use @RLS1GRP
with the CSCQ header. NOTE: Each MBCBATCH execution with a CSCQ card replaces all Startup Commands in the
target region(s), so we recommend all Startup Commands be kept in a common member to assist in their administration. To
remove all Startup Commands without adding a new command use special ‘STSD SQ *DEL’ command.
Example 1:
CICS DBDCICS {Send commands to Applid DBDCICS }
. . . other command cards sent to DBDCICS
CICS @APPLGRP PRODAPPL {Send commands to all Applids in PRODAPPL ApplGrp }
. . . other command cards sent to all Applids in PRODAPPL ApplGrp
Example 2: Send RLS QUIESCE and UNQUIECES commands to the first Applid with a successful connection for propagation
by SMSVSAM.
CICS @RLS1GRP PRDRAPPL
Example 3: Send Startup Commands to all Applids in PRODAPPL ApplGrp.

CSCQ @APPLGRP PRODAPPL
STAR PAY1
MESG ALL THE PAYROLL SYSTEM HAS BEEN ACTIVATED
CEMT SET PRT1 OUT
Following are additional header card options maintained for compatibility purposes, but not recommended:
CICS ALL
ALL - used to send the commands to all CICS systems defined in the CICS Applid Number/Name table on the BATCNTL
file. We recommend using ApplGrp (Section 3.6) instead of ALL.
CICS nn
nn - specifies the numeric value (1 through 99) of the CICS system number customized on the Applid Number/Name
screen where the commands are sent.

Another method for supplying a header for compatibility purposes (but not recommended), is using column 80 (or 72) to supply
a one-byte CICS number. This number corresponds to a system number in the Applid Number/Name Table (Appendix E). If a
CICS header card is omitted or HDROVER is set to ‘Y’, then commands are sent to the CICS system designated by the number
in column 80 (or 72) in each individual command card (see Table below). If no number is found in column 80 (or 72) and no
CICS header card was provided, the default action is to send the command to CICS system number 1. The command must begin
in column 1 if using an override in column 80 (or 72). The default position of the override is column 80 and is set by specifying
‘Y’ as the value for the COLUMN80 parameter. Set COLUMN80 to ‘N’ checks column 72 for overrides.
CICS card present HDROVER Number in col 80 (or 72) Action

Y N Y Number is ignored; CICS card determines target
Y Y Y Number is used as override target
Y Y N CICS card determines target
N * Y Number is used as override target
N * N Applid in slot 1 of Applid table is target
CLOS / CLOG / CLOD / CLDG / CLOV / CLVG

CLOS ffffffff
CLOD ffffffff
CLOV ffffffff
(or)
CLOS @lllllll
CLOD @lllllll
CLOV @lllllll
(or)
CLOG gggggggggggg [aaaaaaaa]
CLDG gggggggggggg [aaaaaaaa]
CLVG gggggggggggg [aaaaaaaa]
All commands close the indicated file(s). If the close fails, the program waits 5 seconds and retries. Option CLOSRTRY sets
the number of attempts before treating an unsuccessful close as a command failure. CLOV and CLVG commands open the
file(s) first forcing VSAM to VERIFY the file(s) before issuing the close. If option CLOSDIS is set to ‘Y’, files are set
CLOSED and DISABLED or if ‘N’, CLOSED and UNENABLED. CLOD and CLDG commands force files to be CLOSED
and DISABLED regardless of the CLODIS setting. If a file is in-use by a CICS task, (close requested) is returned. To accept
this response as a successful command, set option CLOSRQST to 'Y'.
ffffffff - CICS file name. Value can be a generic file name as in a CEMT SET command (i.e. EMS* closes all
files beginning with EMS).
@lllllll – MBCFLIST name for closing a list of files defined in MBCFLIST (compatibility only).
gggggggggggg – Resource Group name (up to 12 chars) for closing files in the resource group name (non-file Group
entries are ignored). See Section 3.8 for information on using Resource Groups.
WARNING! Do not close files used by conversational tasks. This causes unpredictable results within your CICS. This is true
whether the command is issued through MBCBATCH or using the IBM CICS CEMT facility.
CLOS PAYMST {Close PAYMST file}

CLOG PAYGRP {Close file resources in group PAYGRP}
CLOV PAYMST {Close and verify PAYMST file}

CLVG PAYGRP {Close and verify file resources in group PAYGRP}
CLOD PAYMST {Close and Disable PAYMST file, regardless of CLODIS setting}
CLDG PAYGRP {Close and Disable file resources in group PAYGRP, regardless of CLODIS setting}

CSDA
CSDA
VSE DL/I only: Starts DL/I MPS (Multiple Partition Support). No parameters are required.
CSDD
CSDD
VSE DL/I only: Stops DL/I MPS (Multiple Partition Support). No parameters are required.
DBLC
DBLC OPEN=nnnn
(or)
DBLC CLOSE=nnnn
Used to initiate DBOC commands to open or close CA Datacom/DB databases via a link to DCCOCPR. A return code is given
when the command completes. Refer to CA Datacom/DB documentation for possible return codes and their meanings.
nnnn - is a single URT to open or close. It must be four digits (i.e., 0001). Generic wildcards (?'s) are not allowed.
To use this feature you must have CA Datacom/DB CICS Service Facility 2.4 or higher.
DBLC CLOSE=0001
DBLC OPEN=0001
DLOC
DLOC xxxx yyyyyyyy
VSE DL/I only: Open or close VSE DL/I databases. z/OS DL/I users should see Section 2.1.8.
xxxx - is the function code: STRT to start a database

STOP to stop a database.
yyyyyyyy - is the database name. It must be 8 positions long with a 'D' in the 8th position and '@' filling all unused
positions, i.e. DBD@@@@D. If the database name is 8 positions the ending 'D' is not required. The
database name 'ALL' stops or starts all the databases defined in the table in program MBCPDLOC. A
generic wildcard allows starting and stopping multiple databases with only one command. By using an
asterisk where desired, generic processing takes place for character(s) in that location.
NOTE: A DLPV abend from ASMTDLI (called from MBCPDLOC) indicates an invalid password. Check the password value
defined in MBCPDLOC.
DLOC STRT DB*****D {start all databases beginning with DB}

DLOC STOP DBDPAY@D {stop DBDPAY database}

DOWNSTS
DOWNSTS=ON
(or)
DOWNSTS=OFF
If using IF/ELSE/ENDIF logic, MBCBATCH cannot determine which commands should be processed for Status Tracking for
CICS DOWN errors. Insert DOWNSTS=ON before any commands you want processed and DOWNSTS=OFF after the last
command to process. Otherwise, all commands in the IF/ELSE/ENDIF are ignored for Status Tracking processing.
Example 1: The CLOS PAYGRP command will be processed for Status Tracking if DBDCCICS is down. If DBDCCICS is up,
then Status Tracking for CLOS PAYGRP occurs only if the CLOS PAYFILE command executes with a LASTCC EQ 000.
CICS DBDCCICS
CLOS PAYFILE
IF LASTCC GT 000
CLOS PAYALT
ELSE
DOWNSTS=ON
CLOS PAYGRP
DOWNSTS=OFF
ENDIF
DSNC
DSNC STRT
(or)
DSNC STOP
Start or stop the CICS-DB2 interface. The DSNC command is available to z/OS users only.
ENAB / ENAG
.
ENAB ffffffff
(or)
ENAB @lllllll
(or)
ENAG gggggggggggg [aaaaaaaa]
Set a file, list or group of files enabled.
NOTE: If a file is closed before the command is executed, it remains closed after the command is executed.
ffffffff - CICS file name. Value can be a generic file name as in a CEMT SET command (i.e. EMS* sets all
files beginning with EMS enabled).
@lllllll - MBCFLIST name for enabling a list of files defined in MBCFLIST (compatibility only)
gggggggggggg – Resource Group name (up to 12 chars) for enabling files in the specified resource group name (non-
file entries in Group are ignored). See Section 3.8.
ENAB PAYMST {Enable the PAYMST file}

ENAG PAYGRP {Enable the files in MBC defined Resource Group PAYGRP}

GLSQ / GSSQ (RLS only)
GLSQ gggggggggggg [aaaaaaaa]
GSSQ gggggggggggg [aaaaaaaa]
The GLSQ and GSSQ commands create RLSQ commands (z/OS only) to QUIESCE RLS datasets from MBC Resource Group
files. Only file entries in the specified Group are processed (non-file entries are ignored). The GLSQ command extracts the
Primary DSN value and the GSSQ command extracts the Secondary DSN2 value from the Resource Item record corresponding
to the Group file entry. The DSN (or DSN2) values are used to build RLSQ commands, one for each file entry in the Group.
gggggggggggg – specify Resource Group name (up to 12 chars).

See also RLSQ / RPSQ / RSSQ commands to QUIESCE an individual DSN.
GLSQ RLSGRP { Read Resource Group RLSGRP and Quiesce datasets using Primary DSN value from group files }
GSSQ RLSGRP { Read Resource Group RLSGRP and Quiesce datasets using Secondary DSN2 value from group files }
GLSU / GSSU (RLS only)

GLSU gggggggggggg [aaaaaaaa]
GSSU gggggggggggg [aaaaaaaa]
The GLSU and GSSU commands create RLSU commands (z/OS only) to UNQUIESCE RLS datasets from Resource Group
files. Only file entries in the specified Group are processed (non-file entries are ignored). The GLSU command extracts the
Primary DSN value and the GSSU command extracts the Secondary DSN2 value from the Resource Item record corresponding
to the Group file entry. The DSN (or DSN2) values are used to build RLSU commands, one for each file entry in the Group.

See also RLSU / RPSU / RSSU commands to UNQUIESCE an individual DSN.
GLSU RLSGRP { Read Resource Group RLSGRP and Unquiesce datasets using Primary DSN value from group files }
GSSU RLSGRP { Read Resource Group RLSGRP and Unquiesce datasets using Secondary DSN2 value from group files }

GLQY / GPQY / GSQY (RLS only)
GLQY gggggggggggg [aaaaaaaa]
GPQY gggggggggggg [aaaaaaaa]
GSQY gggggggggggg [aaaaaaaa]
All commands change attributes for Resource Group files from update to read-only (NOUPD, NOADD, NODEL) and set the
file RLSACCESS to NOTRLS. GLQY leaves the file DSN asis. GPQY sets the file to the Primary DSN and GSQY sets the file
to the Secondary DSN2 (GSUP) value for each of the Resource Items in the specified Group. Processed files are left in an
enabled, closed status. Use these commands after GLSQ/GSSQ (QUIESCE) commands to set files to read-only.

See also RLQY, RPQY and RSQY commands to perform this function for an individual file.
GLQY RLSGRP { Change attributes for RLSGRP files to read-only; leave DSN asis; set RLSACCESS(NOTRLS) }
GPQY RLSGRP { Change attributes for RLSGRP files to read-only; set to Item DSN; set RLSACCESS(NOTRLS) }
GSQY RLSGRP { Change attributes for RLSGRP files to read-only; set to Item DSN2; set RLSACCESS(NOTRLS) }
GLUP / GPUP / GSUP (RLS only)

GLUP gggggggggggg [aaaaaaaa]
GPUP gggggggggggg [aaaaaaaa]
GSUP gggggggggggg [aaaaaaaa]
All commands change attributes for Resource Group files from read-only to update (UPD, ADD, DEL) and set the file
RLSACCESS value to RLS. GLUP leaves the file DSN asis. GPUP sets the file to the Primary DSN and GSUP sets the file to
the Secondary DSN2 value for each of the Resource Items in the specified Group. Processed files are left in an disabled, closed
status if option RLUPDIS is Y or enabled, closed status if RLUPDIS is N. Use these commands along with GLSU/GSSU
(UNQUIESCE) to reset files from read-only (GPQY/GSQY) to update access.

See also RLUP, RPUP and RSUP commands to perform this function for an individual file..
GLUP RLSGRP { Change attributes for RLSGRP files to update; leave DSN asis; set RLSACCESS(RLS)}
GPUP RLSGRP { Change attributes for RLSGRP files to update; set to Item DSN; set RLSACCESS(RLS)}
GSUP RLSGRP { Change attributes for RLSGRP files to update; set to Item DSN2; set RLSACCESS(RLS)}

IF / ELSE / ENDIF
IF vvvvvvvv oo nnn
(other commands for TRUE action)
ELSE (optional)
(other commands for FALSE action)
ENDIF
IF/ELSE/ENDIF commands allows overriding the normal flow of non-CICS header commands. ‘IF’ commands can be nested
up to three levels deep. Specify an ENDIF card for every IF card. ELSE commands are optional and allow specifying
commands to execute if the IF statement evaluates to FALSE.
vvvvvvvv - specify ‘IF’ variable MAXCC|LASTCC or up to eight user variables to evaluate. User variables are kept in
an internal table for the current job step and are defined on the first ‘IF’ or ‘SET’ command referencing the
variable (see SET command description in this Section).
oo - specify ‘IF’ operator LE|LT|EQ|NE|GT|GE to use in comparing variable value with the constant value.
nnn - specify ‘IF’ constant value 000-256 to compare to the variable value.
WARNING for STATUS TRACKING users! If ‘IF’ logic is present and a DOWN condition occurs for an Applid,
MBCBATCH cannot determine which commands to write to the BATSTAT file. When using IF/ELSE/ENDIF logic with
embedded file commands (i.e. CLOS, OPEN, ENAB), you must use the DOWNSTS=ON and DOWNSTS=OFF commands
(see DOWNSTS description in this section) to identify which commands to process for Status Tracking.
Example 1: Execute certain commands if a CLOS command fails and other commands if it is successful.
CLOS ACCTFILE
IF LASTCC GT 000
MESG OPER CLOSE FOR ACCTFILE FAILED
ELSE
CLOS PAYFILE
ENDIF
Example 2: Use IF/ELSE/ENDIF commands to override the return code values for non-CICS header commands.
CICS TEMPAPPL
CLOS TRCKSFIL
IF LASTCC GT 000
SET MAXCC 000
ELSE
UNAG TEMPAPPLGRP
ENDIF
Example 3: To alter the condition code for a connection failure we recommend the following approach.
OPTR ERRDOWN=0 {OPTR command placed before test header to ignore DOWN condition}
CICS TSTAPPL {Even if TSTAPPL is DOWN, LASTCC is set to 0 because ERRDOWN=0}
CLOS TRCKSFIL
OPTR ERRDOWN=4 {resets ERRDOWN to normal default value before a production header}
CICS PRDAPPL
CLOS TRCKSFIL

Example 4: Use IF/ELSE/ENDIF commands with your own user variables.
CICS TEMPAPPL
CLOS TRCKSFIL
IF LASTCC GT 000 {If there is an error on CLOS TRCKSFIL . . .
SET MYVAR1 001 . . . then set MYVAR1=001}
ENDIF
(other commands)
IF MYVAR1 EQ 001 {If MYVAR1=001 because of error on CLOS TRCKSFIL . . .
CICS TEMPAPL2 . . . then do this}
UNAG TEMPAPL2GRP
ENDIF
Example 5: Set MAXCC=0 if PHASEIN for program ACCTMSTR is successful on any Applid in APPLGRP ACCTGRP.
CICS @APPLGRP ACCTGRP

PHAS ACCTMSTR
IF LASTCC EQ 000
SET MYVAR1 001
ENDIF
(other commands)
IF MYVAR1 EQ 001
SET MAXCC EQ 000
ENDIF
INQY / INQG
.
INQY ffffffff
(or)
INQY @lllllll
(or)
INQG gggggggggggg [aaaaaaaa]
Change CICS file(s) from open for update to inquiry access. This allows updating from batch programs while open for read-
only requests in CICS. The command closes and disables the file(s), disables the ADD, UPD, and DEL attributes, and then
enables the file(s).
ffffffff - CICS file name. Value can be a generic file name as in a CEMT SET command (i.e. EMS* would
change all files beginning with EMS to read-only.
@lllllll - MBCFLIST name for changing a list of files defined in MBCFLIST to read-only.
gggggggggggg – Resource Group name (up to 12 chars) for opening group files (non-file entries in group are ignored)
for read-only access. See Section 3.8 for more information on using Resource Groups.
INQY PAYMSTR {Change attributes on PAYMSTR file to read-only}

INQG FINANCE {Change attributes on files in FINANCE Group to read-only}

IPTR
IPTR ON | OFF
MBC can produce additional trace information to batch and CICS logs by using the IPTR command to turn on or off the trace.
This command is only applicable if you are running the TCP/IP version of MBC. See Appendix C.
ON – turn the trace on. Specify before the first CICS header card.
OFF – turn the trace off. It is usually not required to add this command to a job as OFF is assumed at the end of the step.
IPTR ON
CICS PRDCICSA
CLOS SMGFILE
IPTR OFF
LINK / LNKL
LINK[$]pppppppp [ll x...x]
LNKL[$]pppppppp LINES=n LEN=lll

... xxx variable data up to 4 lines with len up to 320 bytes xxx ...
Link to a program and pass an optional COMMAREA. The link program must RETURN and should handle all error conditions
properly to avoid hanging the MBC client transaction (MBCX) and preventing other MBCBATCH jobs from running. The
linked program must make provision for handling the optional COMMAREA if included. The first 5-bytes of the COMMAREA
is used by the linked program to indicate a command error by overwriting with a value of ‘ERROR’. Otherwise, the command is
treated as successful.
$ - specify ‘$’ in column 5 to save the LINK/LNKL command for Status Tracking if CICS is down and
STATFLAG=Y. If ‘$’ is not specified, the LINK and LNKL commands are not saved for Status Tracking.
pppppppp – program to link to
ll - is the two-byte length of the optional commarea data x...x to pass for the LINK command. Maximum
length is 52 bytes. Specify leading zero (0) for length values less than 10.
n - is the number of additional lines (1-4) of data to include in the commarea in addition to the current LNKL card
lll - is the three-byte length of the optional commarea data x...x to pass for the LNKL command. Maximum
length is 320 bytes. Specify leading zero (0) for length values less than 100.
x...x - optional COMMAREA to pass
WARNING! The default TASKDATALOC for the batch processor transaction (MBCX) is ANY. If you attempt a LINK
command to a 24-bit program, an AEZC ABEND occurs. Either re-link the user program to 31-bit or change
TASKDATALOC for transaction MBCX to BELOW.
EXCI users: The EXCI version runs under DPL which prohibits certain CICS API commands such as RECEIVE,
CONVERSE, SEND, plus others from running in the target LINK program. Contact MacKinney Systems support to discuss
options if you experience this issue.
LINK MYPROG 09 DATA2PASS

LINK PAYPGM01 05 START
LNKL MYPROG LINES=3 LEN=240

COMMAREA DATA CAN OCCUPY THIS ENTIRE CARD THROUGH COLUMN 80
... AND ALSO THIS ENTIRE CARD THROUGH COLUMN 80

MESG
MESG tttt x...x
Send a message to a CICS terminal. If MacKinney Systems’ CICS/Message is not installed, the message appears on the top line
of the target screen beginning in column 12, the screen is not erased and the COMMAREA is not saved.
tttt - is the terminal-ID where the message is sent.

x...x - is the message text with a maximum length of 60 bytes.
If MacKinney Systems’ CICS/Message is installed, the terminal screen contents are saved and the screen erased before the
message is sent, then the screen restored after the message is cleared.
The following MESG command format can be used only if Message 4.2 or above and MBC 1.1 or above are installed (see
CICS/Message manual). NOTE: Use of MESG ALL, requires you have the latest release of CICS/Message and an ‘=MBC’
entry is defined in the CICS/Message ALL Authorization Table (see CICS/Message manual).
MESG ddddddddd x...x
ddddddddd is the message destination and may be any of the following:
1. tttt - a 4 character TERMID (* allowed).

2. ALL - all CICS terminals.
3. OPER - the System Operator.
4. =ooo - = equal sign followed by a one to three character OPID (* allowed).
5. @gggggggg - a group list of terminal ids, user ids, operator ids, and/or netnames.
6. %uuuuuuuu - a per cent sign followed by a one to eight character user id (* allowed).
7. #nnnnnnnn - a pound sign followed by a one to eight character Netname (* allowed).
x...x - is the message. It can only be 56 positions when @gggggggg, %uuuuuuuu, or #nnnnnnnn are used. Leave
only one blank between the destination and message.
MESG ALL CICS WILL BE SHUTTING DOWN IN 3 MINUTES {if CICS/Message installed}
MESG T001 PAYMST BEING CLOSED IN 1 MINUTE
MSGL
MSGL ddddddddd LINES=n[ NEWS=x]
message line 1 (up to 80 characters)
Send a multi-line message to a CICS terminal. MacKinney Systems CICS/Message must be installed before using this command.
ddddddddd - is the message destination as described in the 'MESG' command.
LINES=n - tells how many 80-character message lines immediately follow the MSGL command. ‘n’ must be 1, 2, 3
or 4. 4 is the maximum number of message lines available.
NEWS=x - indicates whether the message should also be routed to MacKinney Systems CICS/MORNING NEWS. Use
NEWS=Y to route it to CICS/MORNING NEWS. Use NEWS=N or omit the parameter to not route to NEWS.
MSGL ALL LINES=2

THE PRODA AND PRODB CPUS WILL NOT BE AVAILABLE FROM 0700 TO 0900 THIS SUNDAY
FOR SCHEDULED MAINTENANCE

NEWC
NEWC[?]pppppppp
NEWCOPY the indicated program or group of programs. See also PHAS command in this section.
pppppppp - CICS program name. Generic program names are allowed as in a CEMT SET command (i.e. PAY* new
copies all programs beginning with PAY).
? - Entering a ‘?’ in column 5 of the command treats any errors as return code 0. Errors are flagged with ?IGN
in column 75. This allows you to NEWCOPY a program in all regions even if the program is not defined in
some of the regions.
TIP! AUTOINSTALL users see Section 2.1.2 for consideration with NEWC commands if you AUTOINSTALL programs.
NEWC?ACCTPGM {ignore NOTFND error}

NEWC PAYPGM {treat NOTFND condition as an error}
OPEN / OPEG
OPEN ffffffff
(or)
OPEN @lllllll
(or)
OPEG gggggggggggg [aaaaaaaa]
Open the indicated file, list or group of files. The OPEN and OPEG commands also set the file(s) ENABLED.
ffffffff - CICS file name. Generic file names are allowed as in a CEMT SET command (i.e. EMS* opens all
files beginning with EMS).
@lllllll - MBCFLIST name for opening a list of files defined in MBCFLIST.
gggggggggggg – Resource Group name (up to 12 chars) for opening all files defined in the group (non-file entries in
group are ignored). See Section 3.8 for more information on using Resource Groups.
OPEN PAYMST {Open PAYMST file}

OPEG PAYGRP {Open file resources in group PAYGRP}

OPTR
OPTR pppppppp=vvvv
Use OPTR to override the specified option with a new value for this job step. The following options cannot be overridden:
EXTSEC, DOMSEC, CEMTPERF, ERRCMD, ERRSEC, ERRCNCL, HDROVER and SHUTCMD.
pppppppp - is the option label to override

vvvv - is the new value (i.e. DOWNSPC=F).
Example 1: Override option LOGXDD value to N prior to a CEMT SET PROG(YOURPGM) NEW then reset value back to
Y after the command.
OPTR LOGXDD=N
CEMT SET PROG(YOURPGM) NEW
OPTR LOGXDD=Y
...
PHAS
PHAS[?]pppppppp
PHASEIN the indicated program or group of programs. See also the NEWC command in this section.
pppppppp - CICS program name. Generic program names are allowed as in a CEMT SET command (i.e., PAY* issues
PHASEIN for all programs beginning with PAY).
? - Entering a ‘?’ in column 5 of the command treats any errors as return code 0. Errors are flagged with ?IGN
in column 75. This allows you to PHASEIN a program in all regions even if the program is not defined in
some of the regions.
TIP! AUTOINSTALL users see Section 2.1.2 for consideration with PHAS commands if you AUTOINSTALL programs.
PHAS?ACCTPGM {ignore NOTFND error}

PHAS PAYPGM {treat NOTFND condition as an error}

QRYL / QRYS
QRYL rrrr(vvvvvvvvvvvvvvvvvv)
QRYS rrrr(vvvvvvvvvvvvvvvvvv)
The QRYL and QYRS commands return results from EXEC CICS INQUIRE commands to the batch job log. QRYL returns an
expanded format with multiple lines of information per resource and QRYS returns an abbreviated format with a single line of
information per resource. The output format is similar to the corresponding CEMT INQ commands except for TCP where the
information returned from z/OS and VSE differ. Where the command output is written is dependent on installation option,
LOGXDD. See Section 2.1.5 for additional information on usage of the LOGXDD option value.
rrrr - resource type. Accepted values: DOC | FIL | NET | PROG | TCP | TDQ | TER | TRA |
TSQ | URI
vvvvvvvvvvvvvvvv – is an optional value for the resource, the max length which varies per type. The value can
include generic wildcard (*) in any position (except NET for VSE). An ending ‘*’ is used to
match all remaining characters.
FIL | NET | PROG | DOC | TCP max length is 8

URI (z/OS only) max length is 8
TDQ | TER | TRA max length is 4
TSQ max length is 16
NOTE: VSE does not support URI option nor a generic value for NET.
Example 1: List all terminals for CICS Applid DBDCICSA in abbreviated format (1 line per resource)
CICS DBDCICSA
QRYS TER(*)
MBCB060-START OF QRY MESSAGES

QRYS TER(*)
TER(T001) TRA(CEMT) PRI( 000 ) PAG INS ATI TTI LOC NET(PMVST001) ACQ
TER(T002) PRI( 000 ) PAG INS ATI TTI LOC NET(PMVST002) ACQ
TER(T003) PRI( 000 ) PAG INS ATI TTI LOC NET(PMVST003) ACQ
TER(<AAA) TRA(MBCX) PRI( 000 ) AUT INS ATI TTI SES NET(MBCRXCI )
. . .
MBCB061-END OF QRY MESSAGES: LINES(0000064) RESOURCES(000063)
QRYS TER(*) <OK
Example 2: List all files for CICS Applid DBDCICSA beginning with DT* in long format
CICS DBDCICSA
QRYL FIL(DT*)
MBCB060-START OF QRY MESSAGES

QRYL FIL(DT*)
Fil(DTECDFL ) Vsa Clo Ena Rea Upd Add Bro Del Shr
Dsn( MACS.DTEC.RRDS.DUMP.FILE )
Fil(DTECHFL ) Vsa Clo Ena Rea Bro Shr
Dsn( MACS.DTEC.DTECHFL )
Fil(DTECSFL ) Vsa Clo Ena Rea Upd Bro Shr
Dsn( MACS.TRACK.TRCKSFL )
MBCB061-END OF QRY MESSAGES: LINES(0000007) RESOURCES(000003)
QRYL FIL(DT*) <OK

RLQY / RPQY / RSQY (RLS only)
RLQY ffffffff
RPQY nnnnnnnn [aaaaaaaa]
RSQY nnnnnnnn [aaaaaaaa]
These commands change CICS file attributes to read-only (NOUPD, NOADD, NODEL) and set the file RLSACCESS to
NOTRLS. RLQY leaves the file DSN asis. RPQY sets the file to the Resource Item Primary DSN and RSQY sets the file to the
Resource Item Secondary DSN2 value. The files are left in an enabled, closed status. Use these commands after QUIESCE
commands (RLSQ/RPSQ/RSSQ or GLSQ/GSSQ) to set files to read-only access.
ffffffff - CICS file name.

nnnnnnnn – MBC Resource Item file name.
See also GLQY, GPQY and GSQY commands to perform this function with groups of files.
RLQY RLSMSTR { Set RLSMSTR file attributes to read-only; leave DSN asis; set RLSACCESS(NOTRLS) }
RPQY RLSMSTR { Set RLSMSTR file attributes to read-only; set to Primary DSN; set RLSACCESS(NOTRLS) }
RSQY RLSMSTR { Set RLSMSTR file attributes to read-only; set to Secondary DSN2; set RLSACCESS(NOTRLS) }
RLSQ / RPSQ / RSSQ (RLS only)

RLSQ dddddddddddddddddddddddddddddddddddddddddddd
RPSQ nnnnnnnn [aaaaaaaa]
RSSQ nnnnnnnn [aaaaaaaa]
The RLSQ, RPSQ and RSSQ commands QUIESCE an RLS dataset. Upon completion, the dataset is closed in all CICS regions
and the quiesced flag is set in the ICF catalog preventing any files being opened in RLS mode for the dataset.
NOTE: Commands RLQY and GLQY can be used after RLSQ, RPSQ and RSSQ (QUIESCE) to set a file for the dataset to
read-only mode.
ddd...ddd - is the dataset name (up to 44 chars), it MUST begin in column 6 and NOT be enclosed in quotes.
See also GLSQ and GSSQ commands to QUEISCE groups of datasets.
RLSQ PAY.MASTER.VS
RPSQ RLSMSTR { Read RLSMSTR resource item for primary DSN value and QUIESCE the DSN }
RSSQ RLSMSTR { Read RLSMSTR resource item for secondary DSN2 value and QUIESCE the DSN2 }
Example 1: QUIESCE Resource Item RLSMSTR primary DSN and set associated FILE to read-only.
CICS DBDCICSA
RPSQ RLSMSTR {Read RLSMSTR resource item for primary DSN value and QUIESCE the DSN }
RPQY RLSMSTR {Set RLSMSTR file attributes to read-only; set to Primary DSN; set RLSACCESS(NOTRLS)}

RLSU / RPSU / RSSU (RLS only)
RLSU dddddddddddddddddddddddddddddddddddddddddddd
RPSU nnnnnnnn [aaaaaaaa]
RSSU nnnnnnnn [aaaaaaaa]
The RLSU, RPSU and RSSU commands UNQUIESCE an RLS dataset – the reverse of the QUIESCE(see RLSQ).
NOTE: Commands RLUP, RPUP, RSUP, GLUP, GPUP and GSUP can be used after UNQUIESCE commands (RLSU,
RPSU, RSSU, GLSU or GSSU) to reset a file for the unquiesced dataset back to update mode.
ddd...ddd - CICS dataset name (up to 44 chars); MUST begin in col 6 and NOT be enclosed in quotes.
Nnnnnnnn – MBC Resource Item file name.
which case use of the @ApplGrp is attempted first and if not found, then the local connected region is
used.
See also GLSU and GSSU commands to UNQUIESCE groups of datasets.
RLSU ACCT.MASTER.VS
RPSU RLSMSTR { Read RLSMSTR Resource Item for primary DSN value and UNQUIESCE the DSN }
RSSU RLSMSTR { Read RLSMSTR Resource Item for secondary DSN2 value and UNQUIESCE the DSN2 }
RLUP / RPUP / RSUP (RLS only)

RLUP ffffffff
RPUP nnnnnnnn [aaaaaaaa]
RSUP nnnnnnnn [aaaaaaaa]
These commands change CICS file attributes to update (UPD, ADD, DEL) and set the file RLSACCESS to RLS. RLUP leaves
the file DSN asis. RPUP sets the file to the Resource Item Primary DSN and RSUP sets the file to the Resource Item Secondary
DSN2 value. The file is left in an disabled, closed status if option RLUPDIS is Y or enabled, closed status if RLUPDIS is N.
Use these commands along with UNQUIESCE commands (RLSU, RPSU, RSSU, GLSU or GSSU) to reverse RLQY, RPQY,
RSQY, GLQY, GPQY or GSQY commands and set files back to update access.
ffffffff - CICS file name.

See also GLUP, GPUP and GSUP commands to perform the function with groups of files.
RLUP RLSMSTR { Set RLSMSTR file attributes to update; leave DSN asis; set RLSACCESS(RLS) }
RPUP RLSMSTR { Set RLSMSTR file attributes to update; set to Primary DSN; set RLSACCESS(RLS) }
RSUP RLSMSTR { Set RLSMSTR file attributes to update; set to Secondary DSN2; set RLSACCESS(RLS) }
Example 1: UNQUIESCE Resource Item RLSMSTR primary DSN and set associated FILE to update.
CICS DBDCICSA
RPSU RLSMSTR {Read RLSMSTR Resource Item for primary DSN value and QUIESCE the DSN }
RPUP RLSMSTR {Set RLSMSTR file attributes to read-only; set to Primary DSN; set RLSACCESS(NOTRLS)}

SAPL
SAPL DN|UP aaaaaaaa|@APPLGRP gggggggggggg
SAPL DN adds an Applid Status DOWN record in the BATSTAT file, one for each Applid. SAPL UP deletes the Applid Status
record(s) for a specific Applid or a group of Applids using the @APPLGRP parm.
If Applid Status DOWN record is present in the BATSTAT file, then any errors MBCBATCH has trying to open the pipe are
treated like DOWNSPC=B (bypassed) for APPLSTS=Y or DOWNSPC=F (flushed) for APPLSTS=F.
The Applid Status DOWN record is deleted by a new SAPL UP command, by invoking the MBCPRSTX BATSTAT clean-up
exit (Section 6.5) or automatically when a successful connect to the Applid is complete.
NOTE: Installation option APPLSTS must be set to ‘Y’ or ‘F’ to allow this command to process.
aaaaaaaa - CICS Applid 1-8 characters.

gggggggggggg - specifies an ApplGrp defined via the Administrative ApplGrp Directory screen (see Section 3.6). This
parameter must be preceded by ‘@APPLGRP’.
SAPL DN @APPLGRP PRDAPPL {set down status for all Applids in PRDAPPL ApplGrp}
SAPL DN DBDCICSA {set down status for Applid DBDCICSA}
SET
SET vvvvvvvv nnn
The SET updates the value of the specified MAXCC or user variable in combination with IF/ELSE/ENDIF processing.
vvvvvvvv - specify ‘MAXCC’ or up to eight user variables. User variables are kept in an internal table for the current job
step and are defined on the first ‘IF’ (see IF command) or ‘SET’ command referencing the variable.
nnn - specify constant value nnn (0-255) to assign to the variable vvvvvvvv.
NOTE: If MAXCC is the SET variable, assigning a value of 4, 8, 12 and 16. It overrides the final MAXCC value by the
values set for ERRDOWN, ERRCMD, ERRSEC and ERRCNCL respectively.
Example 1: Ignore error if opening test file TESTFIL.
CLOS TESTFIL
IF LASTCC GT 000
SET MAXCC 000
ENDIF
Example 2: Use of user variable to test for launch of tranid. MYVAR is set to 002 if OPEN for TESTMST is good. MYVAR is
later tested for 002 and if it matches, tranid TMST is started.
OPEN TESTFIL
IF LASTCC EQ 000
OPEN TESTMST
IF LAST CC EQ 000
SET MYVAR 002
ENDIF
ENDIF
IF MYVAR EQ 002
STAR TMST
ENDIF
For additional examples see IF / ELSE / ENDIF command.

SHUT
SHUT [IMM {NOSDTRAN | SDTRAN(tttt)}]
[NOSDTRAN | SDTRAN(tttt)]
This command initiates a CICS shutdown. Installation option SHUTCMD must be set to ‘Y’ to allow this command. If
EXTSEC=Y, transaction MBCQ is started with the Execution Userid. If EXTSEC=N, transaction MBCQ is started on terminal
SHUTTERM, which must be defined to CICS. The SHUTTERM terminal must be defined with ATI=YES and the USERID
associated with the SHUTTERM must be authorized to run transaction MBCQ.
IMM – Optionally specified in column 6, indicates an immediate shutdown. If this option is not specified a normal
shutdown is performed.
NOSDTRAN – Optionally specified in column 6 or 10 (depending on the use of the IMM option). Value indicates no
shutdown assist transaction is run at CICS shutdown.
SDTRAN - Optionally specified in column 6 or 10 (depending on the use of the IMM option). Value is mutually
exclusive with NOSDTRAN and specifies the 4-character name of the shutdown assist transaction tttt. The
shutdown assist transaction, if specified, is run at CICS warm and immediate shutdowns. It ensures CICS
shuts down in a controlled way within a reasonable time (for example, by purging long-running tasks). For
details of the default shutdown assist transaction, CESD, see the CICS Operations and Utilities Guide.
SHUT
SHUT NOSDTRAN
SHUT SDTRAN(MSHU)
SHUT IMM SDTRAN(MSHU)
STAR DBOC
STAR DBOC {term} ll {DBOC|DBLC} x...x
STAR DBOC starts CA Datacom/DB tranid DBOC and passes a DBOC or DBLC command. Refer to CA Datacom/DB
documentation for details on command formats and output destinations. The default Message Log destination is DBOCPRT.
term - is the optional terminal id where the DBOC tranid is started.
ll - is the two-byte length of the command, including ‘DBOC’ or ‘DBLC’. Specify leading zero (0) for length values
less than 10.
x...x - is the continuation of the DBOC/DBLC command.
STAR DBOC 20 DBLC CLOSE 0001,0002

STAR DBOC 19 DBLC OPEN 0001,0002

STAR / STRL
STAR[$]tran|MBCP [term] [ll x...x]
STRL[$]tran|MBCP LINES=n LEN=lll [TERM=term|USER=userid]

... xxx variable data up to 4 80-byte lines with len up to 320 bytes xxx ...
The STAR and STRL commands start a CICS transaction. Options include starting with or without data, starting on a specific
terminal or starting with a specific userid. When you start a transaction and pass data, the started program must normally issue a
RETRIEVE command to extract the data. If you want to start a program that issues a RECEIVE command, MBC provides tranid
MBCP to pass data to a second tranid via a RETURN IMMEDIATE. The started program must issue a RECEIVE command to
pick up the data from the RETURN IMMEDIATE.
If you need to know when the started transaction completes, see 6.3 Task Delay Utility.
WARNING! When using USER parm, the Execution User for this command must have surrogate authority or surrogate
checking must be turned off or else the START will fail. Also userid must be authorized to execute tran. QUERY SECURITY
is NOT performed when a userid is specified.
WARNING! The MBC return code is set based on whether the tran is successfully started, NOT if the transaction (program)
completes successfully. For example, if the start is successful and the program abends, the MBC return code is set to ‘0’. Use
LINK command if it is critical to know about an error in the target program (program must return error code in commarea).
WARNING! If installation option EXTSEC=Y, MBC performs a QUERY SECURITY (unless USER parm is specified) to
verify the Execution User is allowed to execute the tranid before the start is issued. If the user is not authorized, the tranid will
not be started and the command will be failed with a security error.
WARNING! Data cannot be passed to a tranid associated with a macro-level program.
$ - specify ‘$’ in column 5 to cause MBC to save the STAR/STRL command for Status Tracking if CICS is down and
STATFLAG=Y. If ‘$’ is not specified, the STAR and STRL commands are not saved for Status Tracking.
tran - is tranid to start.
or
MBCP - is a special tranid used to pass data to a program via a second tranid whose target program
needs to RECEIVE data rather than RETRIEVE data. When MBCP is used, you must specify a term
value and the target termid must be defined with ATI=YES. See examples below.
term - optional termid where tran is started. Termid must be defined with ATI=YES. The term is required
for MBCP option. The USER parm cannot be specified when TERM parm is present.
ll - two-byte length of the optional data x...x to pass (STAR command only). Maximum length is 52 bytes.
Specify leading zero (0) for length values less than 10.
userid - optional userid to be associated with tran when started. Userid must be defined to CICS. Specify LINES=0 and
LEN=000 to specify userid without data.
n - number of additional lines from 0-4 of data to include for the commarea (not including the STRL card)
lll - three-byte length of the optional data x...x to pass for the STRL command. Maximum length is
320 bytes. Specify leading zero (0) for length values less than 100.
STAR ATRN {Starts ATRN in background}

STAR$ATRN T001 {Starts ATRN on term T001 and saves for Status Tracking if CICS down}
STAR ATRN 08 PASSDATA {Starts ATRN in background and passes ‘PASSDATA’}
STAR ATRN T001 08 PASSDATA {Starts ATRN on term T001 and passes ‘PASSDATA’}
STRL ATRN LINES=0 LEN=000 USER=SYSUSER {Starts ATRN in background with USERID SYSUSER}
STRL ATRN LINES=2 LEN=160 TERM=T001 {Starts ATRN on term T001 and passes …}
PASS DATA CAN OCCUPY THIS ENTIRE CARD THROUGH COLUMN 80 {… the next 2 cards}
STRL ATRN LINES=1 LEN=080 USER=SYSA {Starts ATRN in background with USERID SYSA …}
PASS DATA CAN OCCUPY THIS ENTIRE CARD THROUGH COLUMN 80 {…and passes this card}

STAR MBCP Examples: Below are sample STAR MBCP commands. Tranid programs launched must perform a RECEIVE
instead of a RETRIEVE.
STRL MBCP CNSL LINES=3 LEN=240 {launches MacKinney Systems CICS/Message product (required for MESG …
MESG T05A DATA CAN OCCUPY THIS ENTIRE CARD THROUGH COLUMN 80 {… command) to send a }
... AND ALSO THIS ENTIRE CARD THROUGH COLUMN 80 {… 3-line message to CNSL}
STAR MBCP CNSL 32 MESG T05A THIS IS A TEST MESSAGE {length of data includes second tran MESG}
STAR MBCP T001 18 DTRN DATE=07/25/20 {DTRN is launched on term T001 with ‘DATE=07/25/20}
STSD
STSD tt nnnnnnnn
The STSD command deletes the MBC Status Tracking record for a single Resource Item. The STSD command can be used if
you need a batch method to remove a Resource Item from MBC. Resource Items can also be removed using the Status Tracking
Maintenance option from the Administration Menu (see Section 3.9). If a resource is removed from CICS and the Resource
Item is not removed from BATCSTS, errors will occur during CICS startup which will increase the startup time.
tt - is the Resource type (FI-File|PG-Pgm|TR-Tran|TD-TDQ|TX-Ext TDQ|IP-TCPIP Service)

nnnnnnnn - is the Resource name (up to 12 chars).
NOTE: Special command ‘STSD SQ *DEL’ is used along with header CSCQ to remove all Startup Commands without adding
any new commands.
STSD FI MYFILE {Delete file MYFILE from BATCSTS}

STSD PG MYPROG {Delete program MYPROG from BATCSTS}
STSR / STSG
STSR tt nnnnnnnn [aaaaaaaa]
(or)
STSG gggggggggggg [aaaaaaaa]
The command synchronizes the CICS Status Tracking records for a single MBC Resource Item (STSR) or a group of MBC
Resource Items (STSG) with the current CICS status for the resource. MBC processes the commands by performing an
INQUIRE for the Resource Item(s) and updating the status in the BATCSTS file. Use of these commands is only needed if
Resource Item(s) are updated outside of MBC (i.e. CEMT operator commands or EXEC CICS SET FILE from a program).
STSR and STSG are used to ensure Resource Item status value are current.

nnnnnnnn - is the Resource Item name (up to 8 chars)
gggggggggggg – Resource Group name (up to 12 chars) for opening files defined in the Resource Group (non-file
entries in Group are ignored) for update access. See Section 3.8 for more information on using
Resource Groups.
STSR FI MYFILE {Update the status for file MYFILE}

STSR PG MYPROG {Update the status for program MYPROG}
STSG FINANCE {Update the status for FINANCE Resource Group members}
STSG FINANCE2 {Update the status for FINANCE2 Resource Group members}

UNAL / UNAQ
UNAL ffffffff
UNAQ ffffffff (z/OS only – uses SVC 99)
(or)
UNAL @lllllll
UNAQ @lllllll (z/OS only – uses SVC 99)
The UNAL command is used to deallocate a file or a file list from CICS. The UNAQ command (z/OS only) is used to
deallocate an individual or group of extrapartition TDQ files or BDAM files CICS. Files are left closed and disabled. It is
recommended that you pair UNAL/UNAQ commands with ALOC/ALOQ commands. See UNAR command for a
recommended alternative to using UNAL or UNAQ.
ffffffff - is the CICS file name for UNAL or DCT for UNAQ.
@lllllll - represents a file list name defined in MBCFLIST.
NOTES: TDQs must be closed before using the UNAQ command (Section 2.1.7 Transient Data Queue Handling).
ALOC/UNAL commands are not required if using Dynamic File Allocation (dataset name specified for the RDO definition
DSNAME parm, and no DD statement for the file in the CICS startup JCL).
UNAL PAYMSTR {Unallocate the PAYMSTR file}

CEMT SET TDQ(PAYQ) CLO {Close the PAYQ TDQ . . .
UNAQ PAYQ . . . and unallocate the PAYQ TDQ}
UNAR / UNAG
UNAR tt nnnnnnnn [aaaaaaaa]
(or)
UNAG gggggggggggg [aaaaaaaa]
These commands are used to unallocate a defined Resource Item(s) (file/program/transaction/TDQ) from CICS. UNAR
unallocates a single Resource Item and UNAG unallocates a group of Resource Items (See Section 3.8 for more information on
using Resource Groups). Files are closed and disabled. A program, transaction or TDQ is disabled. An Extrapartition TDQ is
also closed. See Section 3.7 for more information on using Resource Items. It is recommended to pair the UNAR command with
an ALOR/ALSR and UNAG with ALOG/ALSG commands.

nnnnnnnn - is the Resource Item name (up to 8 chars)
gggggggggggg - is the Resource Group name (up to 12 chars).
UNAR FI PAYMSTR {Close and disable the Resource Item PAYMSTR file}
UNAR TR PAYM {Disable the Resource Item PAYM tranid}
UNAG FINANCE {Unallocate the FINANCE Resource Group}

UNAG FINANCE2 {Unallocate the FINANCE2 Resource Group}

UPDT / UPDG
UPDT ffffffff [xxxxx yyyyy zzzzz]
(or)
UPDT @lllllll [xxxxx yyyyy zzzzz]
(or)
UPDG gggggggggggg [xxxxx yyyyy zzzzz]
Change CICS file(s) attributes from read-only to update (UPD, ADD, DEL). The command first closes and disables the file(s),
changes the attributes, and then enables the file(s).
ffffffff - CICS file name. Generic file names as in a CEMT SET command (i.e. EMS* changes all files
beginning with EMS to available for update.
@lllllll - MBCFLIST name for changing a list of files defined in MBCFLIST to update.
gggggggggggg – Resource Group name (up to 12 chars) for opening files in the Resource Group (non-file entries in
Group are ignored) for update access. See Section 3.8 for more information on using Resource
Groups.
xxxxx, yyyyy, and zzzzz represent optional update override options ‘NOADD’, ‘NODEL’, or ‘NOUPD’. The default
action if omitted is to allow adds, deletes, and updates. Specify 1 to 3 options to override the default
action.
UPDT PAYMSTR {Change attributes on PAYMSTR file to allow update}

UNDG FINANCE {Change attributes on files in FINANCE Group to allow update}
WAIT
WAIT mss
This command causes MBCBATCH to wait the amount of time indicated before processing the next command. This is usually
done after sending a MESG to tell the users their file(s) will close in a few minutes or seconds.
m – number of minutes (0-9) to wait
ss – number of seconds (01-59) to wait. Specify leading zero for seconds less than 10.
WAIT 030 {Wait 30 seconds before the next command}

WAIT 200 {Wait 2 minutes before the next command}

Section VI
Online Programs and Procedures
6.1 Online Overview
The online portion of MacKinney Batch to CICS consist of three main components, the Online Administration, Online
Command Processor, and the background EXCI (z/OS) or TCP/IP (VSE) server. The Online Administration component is
discussed in detail in Section 3. The Online Command Processor (Section 6.2) lets you process many of the MBC commands
directly from a CICS screen or by linking from an Application program. The background EXCI (z/OS) or TCP/IP (VSE) server
is for the most part, transparent to the user. Once installed, online server programs are automatically invoked when commands
are sent from the batch client side. Sample CICS logs of EXCI and TCP/IP server sessions are shown in Section 6.6.
Special online program (MBCPSCN) can be used in conjunction with the MBC LINK command to force a delay in the batch
job until a passed list of long running transaction(s) are complete. See Section 6.3.
6.3 Task Delay Utility (MBCPSCN)
Sample user exit MBCPCMDX (Section 6.4) can be used to add support for your own commands to pass from the batch client.
Use sample user exit MBCPRSTX (Section 6.5) to submit JCL to clean up the BATSTAT after MBCPRSET processing.
6.2 Online Command Processor
The Online Command Processor allows executing MacKinney Batch to CICS commands from a CICS screen or by linking
from an application program (see Section 6.2.1). You can launch the Online Command Processor screen by entering ‘MBCC’:
MBCMOCP MacKinney Batch to CICS 01/10/20 13:50:16

Online Command Processor Applid: DBDCCICS
Enter one of the MBC commands below on the input line beginning in column 1
--------------------------------------------------------------------------------
---+----1-----+----2----+----3----+----4----+----5----+----6----+----7----+----8
OPEN|CLOS ffffffff|@llllllll
ENAB|INQY|UPDT ffffffff|@llllllll
NEWC|PHAS pppppppp
ALOR|ALSR|STSR|UNAR tt rrrrrrrr (See Help for additional commands)
ALOC ddd ffffffff|@llllllll <-dsn->
ALOG|ALSG|STSG|UNAG gggggggggggg (See Help for additional commands)
UNAL ffffffff|@llllllll
CEMT INQUIRE|SET|DISCARD(|PERFORM)
LINK pppppppp (ll) (x..x)
STAR tttt (term) (ll) (x..x)
DBLC OPEN=nnnn|CLOSE=nnnn
RLSQ|RLSU <-dsn->
Enter-Process the command PF1-Help PF3-End
Commands must begin in column 1. After keying in the command on the command line, press ENTER to process the
command. Command responses are displayed back to the screen as well as being written to the TDMESGQ. For a current list
of commands supported with the Online Command Processor, see the Help screen. See Section 5.1 for further information about
each command. Use of this facility requires read access to the BATCNTL file. Press PF1/13 for Help information. Press
PF3/15 to exit the Online Command Processor.
NOTES: RLS commands are not supported in VSE. CEMT PERFORM commands (except for SHUT option) are allowed only
if CEMTPERF=Y. CEMT PERFORM SHUT is not allowed via the Online Command Processor regardless of the SHUTCMD
installation option setting.
Section VI – Online Programs and Procedures 143
6.2.1 API to the Online Command Processor
You can use the Online Command Processor API to process supported commands from your application program (see Section
6.2). To use the API, Applications will LINK to program MBCPOCP passing a command to be processed in the commarea. If
running with Installation Option EXTSEC=Y, then the userid active at the time of the LINK must be authorized for read access
for tranid MBCC, otherwise a security error is returned. The format of the required API commarea is listed below:
ASSEMBLER
LNKCA DS 0CL82
LNKRC DS XL2 RC is returned; x’0000’- successful / x’0008’- error
LNKCMD DS CL80 Command to be passed (blank filled) starting in column 1
LNKMSG ORG LNKCMD An 80-byte message is returned in place of the passed command
COBOL
01 LinkCA.
05 LinkRC COMP PIC S9(4).
88 LinkOK COMP PIC S9(4) Value 0.
88 LinkErr COMP PIC S9(4) Value 8.
05 LinkCMD PIC X(80).
05 LinkMSG REDEFINES LinkCMD.
6.3 Task Delay Utility (MBCPSCN)
MBCPSCN is a special command-level CICS program to which to pass a list of tranids via a LINK command from
MBCBATCH. MBCPSCN inquires on active CICS tasks and delays until none of the tranids in the passed list are active. Up to
10 tranids may be included in a list. The format of the LINK command input to MBCBATCH is:
LINK MBCPSCN LL TRN1,TRN2,TRN3...
LL - is the length of the data passed starting with TRN1.
NOTE: Use of this command could contribute to a TIMEOUT situation. See Section 2.1.1.
6.4 Command User Exit (MBCPCMDX)
A sample command user exit, MBCPCMDX, is provided for optional use with the CICS sever side of command processing. If
installation option CMDEXIT=Y (Section 3.4) then the exit is called before any normal processing is done with a passed
command. You can add support for new commands, alter the command card or force the command to fail with an error return
code. If you are adding a new command, you must also modify MBCBCMDX and add support for the command to allow it to
pass on the batch client side. Review the sample source in member MBCPCMDX for additional information. Sample JCL for
assembling changes are found in member MBCJASMC.
If you do not need the exit, setting CMDEXIT=N results in improved performance.
6.5 BATSTAT Reset Clean-up Exit (MBCPRSTX)
If you use Status Tracking and run MBCBATCH when CICS is down, then command records from MBCBATCH are saved to
the BATSTAT file. During the next CICS startup, the saved BATSTAT records are processed by MBCPRSET and after
processing are no longer needed. To facilitate clean-up of these records, sample user exit MBCPRSTX is provided in your
MBC source. MBCPRSTX submits a job to remove the previously processed records from the BATSTAT file.
Before MBCPRSTX will work, you must first customize the JCL found in MBCPRSTX to match your environment (loadlib,
BATSTAT dataset name, etc.). See the additional instructions in the source code. You then need to assemble and link
MBCPRSTX using sample JCL. MBCJASMC, and make the program available to MBCPRSET in a DFHRPL load library
If you choose not to use MBCPRSTX, simply do not make it available in the DFHRPL and/or remove the RDO definition for
program MBCPRSTX. If MBCPRSTX is not used, you need to manually maintain the BATSTAT file (see Section 7.2.7).
144 Section VI – Online Programs and Procedures

6.6 Sample CICS Log
Below is a sample CICS log showing an EXCI session including comments enclosed within braces {}. Any messages created
by an executing command should precede the actual command. Each command has an indicator such as <OK, <WARN or
<ERR indicating the success or failure of the command. In the case below, messages written to the CSMT queue were written
by MBC, the remaining messages were written by CICS.
{CSCS Message written by CICS indicating EXCI session starting and USERID submitting the job}
CSCS DFHSN1400 T540 Session signon for session RS1 by user RJS1 is complete.
MBCE175-CONNECTED FROM BATCH(JOB0020:MBC$RUN) USER(RJS1) XUSR(RJS1) 07/25/20 14:12:21 MBCPXCI x.x RJS1
{Multiple MBC CSMT messages preceding the command which in this case is generic}
MBCE120-CLOS SUCCESSFUL FOR FILE EMLDIR 07/25/20 14:12:21 MBCPCMFI x.x RJS1
MBCE120-CLOS SUCCESSFUL FOR FILE EMLDOC 07/25/20 14:12:21 MBCPCMFI x.x RJS1
MBCE120-CLOS SUCCESSFUL FOR FILE EMLDST 07/25/20 14:12:21 MBCPCMFI x.x RJS1
MBCE120-CLOS SUCCESSFUL FOR FILE EMLRTE 07/25/20 14:12:21 MBCPCMFI x.x RJS1
MBCE120-CLOS SUCCESSFUL FOR FILE EMLSTS 07/25/20 14:12:21 MBCPCMFI x.x RJS1
{Sample CSMT command message indicating a successful completion}
CLOS EML* <OK 07/25/20 14:12:21 MBCPCMFI x.x RJS1
{Sample MBC CSMT message preceding a successful command}
MBCE122-MESG ROUTED TO: T05B 07/25/20 14:12:22 MBCPCMNF x.x RJS1
MESG T05B CLOS WAS GOOD <OK 07/25/20 14:12:22 MBCPCMNF x.x RJS1
{Sample MBC CSMT warning message preceding a generic command}
MBCE110-NO FILES MATCHING EML*Z WERE FOUND 07/25/20 14:12:23 MBCPCMFI x.x RJS1
{Sample CSMT command message indicating a completion with a warning}
CLOS EML*Z <WARN 07/25/20 14:12:23 MBCPCMFI x.x RJS1
{Sample CICS CSFL message preceding a successful CSMT command completion}
DFHFC0204 09/11/2019 14:12:23 T540 MBCRXCI RJS1 MBCX FCT entry for EMLSTS has been updated.
INQY EMLSTS <OK 07/25/20 14:12:24 MBCPCMFI x.x RJS1
{Sample MBC error message preceding a failing command}
MBCE111-FILE EMLZZZ NOT FOUND IN TABLES 07/25/20 14:12:24 MBCPCMFI x.x RJS1
CLOS EMLZZZ <ERR 07/25/20 14:12:24 MBCPCMFI x.x RJS1
{CSCS Message written by CICS indicating EXCI session completed}
DFHSN1500 T540 Session signoff for session RS1 is complete. 6 transactions entered with 0 errors.
A sample CICS log of a TCP/IP session is shown on the following page.
Below is a sample CICS log of a TCP/IP session including comments enclosed within braces {}.
{CICS CSMT Message indicating Listener is ready}

EZY1258I 07/25/20 11:36:28 EZACIC01 ENTRY POINT IS 19D3CAD0
EZY1261I 07/25/20 11:36:28 EZACIC03 ATTACH SUCCESSFUL, TCB ADDRESS=007A3E88 TRAN=CSKL TASK=0000345
EZY1291I 07/25/20 11:36:28 LISTENER TRANSACTION= CSKL ACCEPTING REQUESTS VIA PORT 3100
{CICS CSMT Message indicating Listener has picked up Connect Socket from batch and has started MBCZ}
EZY1325I 07/25/20 11:39.32 START SUCCESSFUL TRANID= MBCZ PARTNER INET ADDR=27.0.0.1 PORT=1295
{CSMT Message written by MBC server program MBCPTCI indicating Connection is complete and USERID submitting the job}
MBCE170-IP CONNECTION COMPLETE TO APPL(T540) PORT(01295) XUSR(RJS1) 07/25/20 11:39:43 MBCPTCI x.x RJS1
MBCE170-JOB(JOB00020:MBC$RUN) FAMILY(INET) IP(127.000.000.001) 07/25/20 11:39:43 MBCPTCI x.x RJS1
MBCE175-CONNECTED FROM BATCH(PJB00020:MBC$RUN) USER(RJS1) XUSR(RJS1) 07/25/20 11:39:43 MBCPTCI x.x RJS1
CLOS EMLSTS <OK 07/25/20 11:39:43 MBCPCMFI x.x MBC$RUN
CLOS EMLDST <OK 07/25/20 11:39:43 MBCPCMFI x.x MBC$RUN
{Sample MBC CSMT error message preceding a failing command}
MBCE111-FILE EMLZZZ NOT FOUND IN TABLES 07/25/20 11:39:43 MBCPCMFI x.x MBC$RUN
CLOS EMLZZZ <ERR 07/25/20 11:39:43 MBCPCMFI x.x MBC$RUN
{CSMT Message written by MBC server indicating TCP/IP session has completed}
MBCE172-CLOSE SOCKET COMPLETE FOR APPL(T540) 07/25/20 11:39:43 MBCPTCI x.x MBC$RUN
Section VI – Online Programs and Procedures 145

Section VII
Status Tracking
7.1 Status Tracking Overview
The Status Tracking facility built-in to MacKinney Batch to CICS can assist you in managing the status (open, closed,
allocated, enabled, dataset name, etc.) of supported CICS resources by tracking changes as they are made. Supported
resources for Status Tracking include files, transactions, programs, TCPIP services, TDQs and DL/I databases.
WARNING! CEMT commands and MBC File commands using MBCFLIST with generic qualifiers and can result in
resources ending in an incorrect state after CICS startup.
The ultimate purpose for Status Tracking is warm-start emulation – which preserves the status of resources while a batch
job is running over a CICS recycle. If CICS is down or a CICS shutdown or ABEND occurs while a long-running batch job
is active and resources are in a modified state due to MBCBATCH processing, Status Tracking ensures the status of each
resource is reset to the proper state at the next CICS startup during a process called Reset Processing (MBCPRSET).
For example, if an early job step uses MBCBATCH to set a file closed and while the batch job is running CICS is restarted,
then during Reset Processing, the status of the file is set to closed and the long-running jobs are not adversely affected.
7.1.1 New Broadened Status Tracking Scope
If you were using Status Tracking prior to MBC 2.0, the scope of Status Tracking was limited to MBCBATCH usage.
Commands processed through MBCBATCH were written to the BATSTAT file whether CICS was up or down. The
commands from the BATSTAT file were then processed during CICS startup to emulate a warm start. A big limitation to
this process, was that operations performed in CICS through MBC Administration screen or the Online Command
Processor were not tracked, so any online changes were not reflected during the CICS startup..
Starting with MBC 2.0, Status Tracking has been pushed to CICS, so all MBC related operations, are now tracked.
Commands sent from MBCBATCH to an active CICS are tracked within CICS in a new file, BATCSTS. Operations
performed in CICS through MBC Administration screen or the Online Command Processor are also tracked in the new
BATCSTS file. The BATSTAT file is only written to by MBCBATCH when CICS is down. During CICS startup, MBC
reads both the BATSTAT file and the BATCSTS file to determine the proper status.
TIP! Status changes made to resources outside the scope of MBC (such as changes made through application programs or by
native CEMT commands) are not automatically tracked by Status Tracking. You can dynamically add these resources to
Status Tracking by issuing the MBC commands STSR and STSG via MBCBATCH or by using the Online Command
Processor. As an alternative to issuing the STSR and STSG commands, we recommend modifying the resources with a
method that is tracked, the Online Command Processor (OCP). You can use the OCP from an online screen in place of a
CEMT command or by passing OCP a command from your application program via a LINK (Section 6.2.1).
7.1.2 Startup Manager
New with MBC 2.0, the optional Startup Manager was added to the Status Tracking facility to give users more control of
resource allocation at startup. The Startup Manager allows you to manage whether a resource is allocated/unallocated,
opened/closed, enabled/disabled and also allows specifying the dataset name. Being able to specify a unique dataset name
(files and Extrapartition TDQs only) in the Resource Item record allows you to share CSD files with multiple CICS regions.
When running with Startup Manager enabled, you specify additional Startup Manager preferences for each Resource Item
record depending on the startup type. For example, you specify whether or not you want a file allocated on a COLD start.
And if the file is allocated, whether or not you want the file opened along with a DSN value to use for the file.
The Startup Manager preferences from the Resource Item records takes precedence over the status information saved in
the BATCSTS file by the Status Tracking facility.
146 Section VII –Status Tracking
7.2 Status Tracking Operation
There are two distinct paths for using Status Tracking. The path you choose will depend on how you manage your
resources; particularly your file dataset names. If you define your dataset names in the CSD and want Status Tracking to
only preserve the status to prevent issues due to a CICS startup during a long-running batch job, then use Status Tracking
without the help of the Startup Manager (Section 7.2.1). If you share your CSD file across multiple regions and need unique
dataset names for each region, do not define your dataset names in the CSD, or simply want more control at startup, then
use the Startup Manager path (Section 7.2.2).
7.2.1 Using Status Tracking without Startup Manager
To use Status Tracking without the Startup Manager, set Installation Option STATFLAG=Y and STRTUPMG=N (Section
3.4). With this configuration, you are treating each resource like a warm-start each time CICS is started.
There are two VSAM files used by Status Tracking, BATCSTS and BATSTAT. The BATCSTS file is written to by CICS
command processors when supported resources are updated. Define a unique BATCSTS file (Section 1.2.3) for each target
CICS region (see member MBCJRDOS for BATCSTS sample RDO definition).
The BATSTAT file is updated by MBCBATCH jobs only when you run jobs during a time when a target CICS is down.
Define the BATSTAT file (Section 1.2.2), make the file available to all target CICS regions (see member MBCJRDOF for
BATSTAT sample RDO definition) and add the BATSTAT file to your MBCBATCH JCL (Section 7.2.5).
You must launch the online Reset Processing (MBCPRSET) to process the BATSTAT and BATCSTS files. This is done
by adding MBCPPLT in your startup PLT (Section 7.2.5).
If CICS is up, there are several ways a resource status is modified by MBC. These include executing a command with an
MBCBATCH job or with the MBC Online Command Processor, or entering an MBC Resource Group or Resource Item
administrative operation. MBC command processors take a snapshot of the resource status after processing the command
and store this information in file BATCSTS (one per region).
If CICS is down when an MBCBATCH job runs, Status Tracking saves the command to a separate file (BATSTAT). This
feature is important if you have long-running batch jobs extending past the duration of a CICS shutdown and startup cycle.
The following commands are written in the BATSTAT file: ALO*, CLO*, ENAB, INQY, OPE*, UNA*, UPDT, RLQY,
RLUP and DLOC (VSE). Most CEMT commands referencing resources are also written to BATSTAT (NEWCOPY and
PHASEIN are not). Extreme care must be taken if mixing CEMT commands using generic and non-generic qualifiers, or if
using FLIST. LINK, LNKL, STAR and STRL can optionally be written to the BATSTAT file by entering a ‘$’ after the
command.
STARTUP OVERVIEW WITH STATUS TRACKING AND NO STARTUP MANAGER
During CICS Startup, MBCPPLT launches Reset Processing program MBCPRSET, which is responsible for resetting or
setting monitored resources to the proper state. MBCPRSET runs in two phases after CICS Initialization is complete
1. In Phase 1, MBCPRSET processes commands from the BATSTAT file (if any) written when CICS was down.
2. In Phase 2, MBCPRSET processes resource status values from the BATCSTS file and applies those status values to
the resource (ignoring resources processed in Phase 1).
3. At the end of Phase 2, MBCPRSET checks to see if optional user exit MBCPRSTX has been made available in the
DFHRPL and if so, links to this program to submit a job to remove the previously processed commands from the
BATSTAT file.
NOTE: A message log audit trail is created in the TDMESGQ destination (default is CSMT) for the resources processed
by MBCPRSET.
Section VII –Status Tracking 147

7.2.2 Using Status Tracking with the Startup Manager
To use Status Tracking with the Startup Manager you must set Installation Option STATFLAG=Y and STRTUPMG=Y
(Section 3.4). With this configuration, the Startup Manager preferences for each Resource Item is taken into account and
used to override the last status for the resource as well as the RDO dataset name.
There are three VSAM files used by Status Tracking with the Startup Manager, BATCNTL, BATCSTS and BATSTAT.
The BATCNTL file is used to store Resource Item records defined via Online or Batch Administration (Section 3.7). The
BATCSTS file is updated by CICS command processors when supported resources are updated and by MBCBCPRE during
pre-CICS startup. The BATSTAT file is updated by MBCBATCH jobs when you run jobs during a time when CICS is
down and by MBCBCPRE to add override cards read during pre-CICS startup.
Define the BATCNTL file (Section 1.2.1) (see member MBCJRDOF for sample BATCNTL RDO definition). Define a
unique BATCSTS file (Section 1.2.3) for each target CICS region (see member MBCJRDOS for sample BATCSTS RDO
definition). Define the BATSTAT file (Section 1.2.2), make the file available to all target CICS regions (see member
MBCJRDOF for sample BATSTAT RDO definition), and add the BATSTAT file to your MBCBATCH JCL (Section
7.2.5). Make all three files available to your MBCBCPRE JCL.
For maintaining status values, MBC tracks the status as described in Section 7.2.1 with respect to CICS being up or down.
However, there is one major difference. With the Startup Manager, you must run an additional pre-CICS startup step,
MBCBCPRE, to prepare the BATCSTS file for CICS startup (Section 7.3.2). To be most effective, this utility should be
run immediately before your CICS startup. This is accomplished by adding a step to your CICS job or PROC, or as a
stand-alone job prior to your CICS submission. You must pass a ‘START=’ parm to identify the startup type (COLD,
INITIAL or AUTO). MBCBCPRE treats INITIAL the same as COLD. After determining the startup type, MBCBCPRE
reads input card(s), the first of which sets the Applid. MBCBCPRE then reads all of the Resource Item (BATCNTL)
records for the specified Applid and prepares the CICS Resource Status (BATCSTS) records for startup matching the
preferences you have selected. MBCBCPRE reads any optional ALOR, ALSR, ALOG, ALSG, UNAL and UNAG
commands to use as overrides for the current startup and writes these override commands to the BATSTAT file.
You must also launch the online Reset Processing (MBCPRSET) to process the BATSTAT and BATCSTS files by adding
MBCPPLT in your startup PLT (Section 7.2.5). And if you need to make resources available to PLT programs prior to
when MBCPRSET runs (at the end of CICS initialization), add MBCPPLA to your startup PLT before MBCPPLT and
any other PLT programs requiring resources (see Section 7.2.4).
STARTUP OVERVIEW WITH STATUS TRACKING AND STARTUP MANAGER
1. In the pre-CICS startup step, MBCBCPRE reads all of the Resource Item (BATCNTL) records for the specified
Applid, prepares the CICS Resource Status (BATCSTS) records for startup, and writes a log entry of proposed
changes for each resource. MBCBCPRE then reads any optional ALOR, ALSR, ALOG, ALSG, UNAL and UNAG
commands to use as overrides for the current startup and writes these override commands to the BATSTAT file.
2. If you have PLT programs needing unique resources, use PLT program MBCPPLA to assist. MBCPPLA executes in
the CICS start-up PLT to allocate resources required by other PLT programs following MBCPPLA in your PLTPI.
MBCPPLA reads special Resource Group “PLT.applid” (where applid is the region Applid) to determine resources to
allocate. Each resource defined in this PLT group is processed as if you had issued an ALOR command. NOTE:
CICS normally makes resources available to PLT programs. This group is for resources specifically needing a Dataset
Name override, required if you are sharing a CSD file with multiple regions.
3. During CICS Startup, MBCPPLT launches Reset Processing program MBCPRSET, which is responsible for resetting
or setting monitored resources to the proper state. MBCPRSET is started after CICS Initialization is complete and runs
in two phases. In Phase 1, MBCPRSET processes commands from the BATSTAT file (if any). In Phase 2,
MBCPRSET processes resource status values from the BATCSTS file and applies those status values to the resource.
At the end of Phase 2, MBCPRSET checks to see if optional user exit MBCPRSTX has been made available in the
DFHRPL and if so, links to this program which submits a job to remove previously processed commands from the
BATSTAT file. A message log audit trail is created in the TDMESGQ destination (default is CSMT) for the resources
processed by MBCPRSET.

7.2.3 Status Tracking Administration
There are five options on the Installation Options menu relating to Status Tracking, the STATFLAG, STRTUPMG,
STATRTRY, ERRSTS and TRKNONFI options.
The STATFLAG option determines whether or not you intend to use Status Tracking. Specify ‘Y’ to use Status Tracking
or ‘N’ (Default) to not.
The STRTUPMG option determines whether or not you intend to use the Startup Manager to assist in managing your
resources. Specify ‘Y’ to use Startup Manager or ‘N’ (Default) to not. If you intend to specify ‘Y’ for STRTUPMG, then
STATFLAG must also be ‘Y’.
The STATRTRY option determines the number of times to retry opening file BATSTAT if the open fails due to the file
being in use by another job. There is a 5-second delay between each attempt to open the file. Default value is 2 (10
seconds total wait time). The BATSTAT file is only written to when you run an MBCBATCH job while CICS is down.
The ERRSTS option determines the MAXCC value returned for the MBCBATCH step when an error occurs in Status
Tracking processing. The default is 0. This parm only applies to Status Tracking errors occurring when an MBCBATCH
job runs while CICS is down.
WARNING! Changing ERRSTS (MAXCC) to a non-zero value may prevent steps following MBCBATCH in your batch
jobs from executing.
The TRKNONFI option determines whether or not the status of non-file resources (programs, transactions, TCPIP
services, TDQs) are kept by Status Tracking. Specify ‘Y’ to save non-file resource status values or ‘N’ (default) to not.
7.2.4 Starting PLT Resource Allocation

If you have PLT programs requiring unique resources (i.e. Dataset Names) and are using a shared CSD, then you can
define these unique Resource Items and use PLT program MBCPPLA to assist. MBCPPLA executes in the CICS start-up
PLT to allocate resources required by other PLT programs following MBCPPLA in the PLTPI. MBCPPLA reads special
Resource Group “PLT.applid” (where applid is the Applid value for the region) to determine resources to allocate. Each
Resource Item defined in this PLT group is processed as if you had issued an ALOR command. NOTE: CICS normally
makes resources available to PLT programs. This group is for resources specifically needing a Dataset Name override
(required if sharing the CSD file with multiple regions). See Section 1.9.7 for details on adding MBCPPLA in your startup
PLT. See Section 7.4 for a sample CICS log created during Reset Processing.
7.2.5 Starting Reset Processing from PLT

MBCPPLT executes in the CICS start-up PLT to START transaction MBCR (program MBCPRSET) for Status Tracking
Reset Processing. MBCPRSET runs in two phases after CICS Initialization is complete. MBCPRSET processes commands
from the BATSTAT file (if any) during the first phase of processing. During the second phase, MBCPRSET processes
resource status values from the BATCSTS file and applies those status values to the resource. NOTE: The status values
for a Resource are altered in MBCBCPRE if you are using the Startup Manager. See Section 1.9.7 for details on adding
MBCPPLT in your startup PLT. See Section 7.5 for a sample CICS log created during Reset Processing.

7.2.6 Modifying MBCBATCH JCL for Status Tracking
The MBCBATCH client has logic to update the BATSTAT file with batch commands if option STATFLAG is set to ‘Y’.
This requires the BATSTAT file be defined in the MBCBATCH execution JCL.
Following are sample DD/DLBL statements which must be added to the execution JCL for MBCBATCH when using
Status Tracking:
z/OS
//BATSTAT DD DSN=MBC.BATSTAT,DISP=SHR
VSE
* The following DLBL is necessary only if not in Standard Labels

// DLBL BATSTAT,'MBC.BATSTAT',,VSAM,CAT=xxxxxx
7.2.7 Periodic Maintenance of the BATSTAT File

BATSTAT records are only written by MBC when the target CICS is down. If you are a 24 x 7 shop and never shut down
CICS, ignore this section.
If MBC is writing records to a BATSTAT file, then the records for a particular CICS Applid are only needed until they are
processed by Reset Processing (MBCPRSET) during CICS startup. After Reset Processing, the BATSTAT records for the
startup Applid can be deleted. An optional user exit, MBCPRSTX, is supplied to automatically submit a batch job to delete
previously processed commands from the BATSTAT file. See Section 6.5 for instructions on customizing the exit.
MBCPRSTX needs to be assembled and linked into a DFHRPL load library using sample JCL MBCJCASM if you intend
to use this automated function.
If MBCPRSTX is not made available, you can use using sample job MBCJSUTL (Section 7.3.1). MBCJSUTL can be run
with the following input card:
DEL aaaaaaaa (where aaaaaaaa is the CICS Applid)
(or with an optional AGE days parameter to delete records older than the number of days specified)
DEL aaaaaaaa AGE=nnn (aaaaaaaa is the CICS Applid and nnn is the number of days after which to delete records)
MBCJSUTL could be added as a step after the CICS step in your CICS startup JCL, or manually submitted as a separate job.
It is also recommended to periodically delete and redefine the BATSTAT file prior to a scheduled COLD START of your
CICS systems. See member MBCJFILS for sample JCL to delete and redefine the BATSTAT file.
In between the redefine method recommended above, we suggest using MBCBSUTL to delete unnecessary entries. See
Section 7.3 for details.
7.2.8 Periodic Maintenance of the BATCSTS File

The BATCSTS file can build up with excess records over time if invalid resources are specified or resources are targeted
for Applids that no longer exist. It is recommended to periodically delete and redefine the BATCSTS file prior to a
scheduled COLD START of your CICS systems. See member MBCJFILC for sample JCL to delete and redefine the
BATCSTS file.
In between the redefine method recommended above, we suggest using the Status Tracking Maintenance Online
Administration Option 6 to review and delete unnecessary entries. See Section 3.9 for details.

7.3 Status Tracking Batch Utilities
There are two utility programs to support Status Tracking besides the maintenance utilizes MBCBCSTS and MBCBSTAT.
MBCBSUTL (Section 7.3.1) is provided for BATSTAT file support and MBCBCPRE (Section 7.3.2) is utilizied by the
Startup Manager.
7.3.1 BATSTAT Utility (MBCBSUTL)

Utility program MBCBSUTL helps you maintain the Status Tracking BATSTAT file. Sample JCL is provided in source
member MBCJSUTL. The utility provides two functions PRT and DEL. The PRT function prints selected records from the
BATSTAT file and the DEL function deletes selected records from the BATSTAT file. You can select an individual
Applid or ALL Applids. You can additionally narrow the scope by selecting either by AGE or specifying an individual
resource. The format of the input card is as follows:
fff {ALL|aaaaaaaa} {AGE=nnn|tt rrrrrrrr}
The first parameter must begin in column 1 and must be ‘DEL’ or ‘PRT’
The second parameter must begin in column 5 and must be ‘ALL’ or aaaaaaaa where:
ALL – read records for all Applids for this action.

(or)
aaaaaaaa – read only records for Applid aaaaaaaa for this action
The third parameter (optional) must being in column 14 and must be AGE=999 or ‘tt rrrrrrrr’ where:
AGE=nnn – print or delete resources older than age (nnn=001-365 days) for the selected Applids.
(or)
tt rrrrrrrr – identifies the resource type (tt = FI-file | PG-program | TR-transaction | TD-TDQ | TX-
Extrapartition TDQ | IP-TCPIP service) and up to 8-character resource name to print. One blank separates the
two parameters. The resource name can include an ending ‘*’ to include generic resource name values.
Example 1: Print file ACCTFILE resource record from the BATSTAT file for Applid CICSA2.
PRT CICSA2 FI ACCTFILE

DSN:MACS.MBC.BATSTAT BATSTAT FILE MAINTENANCE 07/25/2020
INPUT: PRT CICSA2 FI ACCTFILE
APPLID TYPE RESOURCE USERID JOB NAME DATE TIME COMMAND
CICSA2 FI ACCTFILE RJS2 MBCJRUN2 07/25/10 11:48:58 INQY ACCTFILE
Example 2: Print all resources on the file 31 days for all Applids.
PRT ALL AGE=031
Example 3: Print all resources on the file 8 days for Applid TESTCICS.
PRT TESTCICS AGE=008
Example 4: Delete file ACCTFILE resource record and transaction ACTR resource record from the BATSTAT file for
Applid CICSA2.
DEL CICSA2 FI ACCTFILE
DEL CICSA2 TR ACTR
Example 5: Delete all resources on the file older than 31 days for all Applids.
DEL ALL AGE=031

Example 6: Delete all program resources for Applid TESTCICS and all programs starting with BAK* in CICSA1.
DEL TESTCICS PG *
DEL CICSA1 PG BAK*
Example 7: Delete all resources for Applid CICSA2.

DEL CICSA2

DSN:MACS.MBC.BATSTAT BATSTAT FILE MAINTENANCE 07/25/2020
INPUT: DEL CICSA2
APPLID TYPE RESOURCE USERID JOB NAME DATE TIME COMMAND
CICSA1 FI EMLDIR RJS2 MBCJRUN2 07/25/10 11:48:58 INQY EMLDIR <DEL
CICSA1 FI EMLDST RJS1 MBCJRUN1 07/25/10 13:48:01 CLOS EMLDST <DEL
CICSA1 FI EMLRTE RJS2 MBCJRUN2 07/25/10 11:48:58 INQY EMLRTE <DEL
CICSA1 FI EMLSTS RJS1 MBCJRUN1 07/25/10 13:48:01 CLOS EMLSTS <DEL
TOTAL RECORDS DELETED: 4
7.3.2 Pre-CICS Startup Utility (MBCBCPRE)

The Pre-CICS Startup Utility MBCBCPRE is part of the optional Startup Manager and serves the function to preset the
status for defined Resource Items in preparation for CICS startup Reset Processing. MBCBCPRE should be run
immediately before each CICS startup. Sample JCL is in source member MBCJCPRE. The format of the control cards are
listed below. Multiple cards can be input in the same job. Processing for both shared and non-shared resources is
supported by specifying multiple groups of cards beginning with a CSTS card to identify from where to read the Resource
Items and including optional override cards following each of the CSTS cards.
col 5
CSTS aaaaaaaa
ALOR tt rrrrrrrr
ALSR tt rrrrrrrr
ALOG gggggggggggg
ALSG gggggggggggg
UNAR tt rrrrrrrr
UNAG gggggggggggg
CSTS – Required first card defines the Applid from where to read Resource Item records for BATCSTS startup processing and
for the optional override cards that follow until EOD or next CSTS card. If only using non-shared resources, then specify the
startup region for the Applid value.
ALOR – Optional override card to allocate a Resource Item using the Primary DSN1 value if Type=FI
ALSR – Optional override card to allocate a Resource Item using the Secondary DSN2 value if Type=FI
ALOG – Optional override card to allocate a group of Resource Items using the Primary DSN1 value for Type=FI resources
ALSG – Optional override card to allocate a group of Resource Items using the Secondary DSN2 value for Type=FI resources
UNAR – Optional override card to unallocate a Resource Item
UNAG – Optional override card to unallocate a group of Resource Items
ssss – CICS startup type (COLD|AUTO). Begins in col 5 for 4 bytes.

aaaaaaaa – Applid aaaaaaaa. Begins in col 10 for max 8 bytes.
tt – Resource Type (tt = FI-file|PG-program|TR-tranid|TD-TDQ|TX-Ext TDQ|IP-TCPIP service ) and begins in col 5.
rrrrrrrr – 8-character (FI|PG|IP) or 4-character (TR|TD|TX – blank filled) Resource Name and begins in col 8.
gggggggggggg – Resource Group. Begins in col 5.
NOTE! The MBCBCPRE JCL EXEC parm must specify PARM= 'START=COLD|INITIAL|AUTO' to determine the
CICS startup type. A value of INITIAL is treated as a COLD start.

Example 1: Read shared Resource Items from @RLSGRP and non-shared Resource Items from DBDCICSA.
MBCBCPRE JCL EXEC Parm specifies START=AUTO.
CSTS @RLSGRP {Shared Resource Items read from @RLSGRP}

ALSR FI MYRLSFL {Override Resource Item definition from @RLSGRP to ALOC Secondary DSN for this run}
CSTS DBDCICSA {Non-shared Resource Items read from DBDCICSA}
UNAG FINANACEGRP {Override non-shared Item definitions for Resource Group FINANCEGRP to UNAL for this run}
UNAR TD MYTD {Override Resource Item definition TDQ MYTD to UNAL for this run}
APPLID : DBDCICSA MACKINNEY BATCH TO CICS - REL x.x PAGE 1

STARTUP: AUTO PRE-CICS STARTUP UTILITY 07/25/2020
USERID : RJS1
CSTS @RLSGRP <CARD INPUT

MBCB220-PRE-CICS STARTUP PROCESSING STARTING
ITEM DSN: MACS.MBC.BATCNTL
CSTS DSN: MACS.DBDCICSA.BATCSTS
CSTS DBDCICSA <CARD INPUT

MBCB220-PRE-CICS STARTUP PROCESSING STARTING
ITEM DSN: MACS.MBC.BATCNTL
CSTS DSN: MACS.DBDCICSA.BATCSTS
FILE(EMLDST ) PRESET CLO DIS FOR MACS.EMLDST

FILE(EMLRTE ) PRESET CLO DIS FOR MACS.EMLRTE
FILE(EMLSTS ) PRESET CLO DIS FOR MACS.EMLSTS
PROG(EMLP100 ) PRESET DIS
TRAN(EML ) PRESET DIS
5 RESOURCES(S) PROCESSED
MBCB221-PRE-CICS STARTUP PROCESSING COMPLETED
APPLID : DBDCICSA MACKINNEY BATCH TO CICS - REL x.x PAGE 2

STARTUP: AUTO PRE-CICS STARTUP UTILITY 07/25/2020
USERID : RJS1
BCB220-PRE-CICS OVERRIDE PROCESSING STARTING

STAT DSN: MACS.MBC.BATSTAT
UNAG FINANACEGRP <CARD ADDED

UNAR TD MYTD <CARD ADDED
2 RESOURCE OVERRIDES
MBCB223-PRE-CICS OVERRIDE PROCESSING COMPLETED
PRE-CICS STARTUP UTILITY ENDING MAXCC(000)
7.4 Sample PLT Resource Allocation CICS Log
Below is a sample CICS log showing messages produced by special PLT allocation program MBCPPLA.
{CSMT Message written by MBCPRSET indicating BATSTAT phase of Status Tracking startup processing has begun}
MBCE350-ALOG FOR GROUP(PLT.T540 ) BEGINNING 09/13/19 15:06:49 MBCPPLA x.x RJS1
MBCE133-ALOR SUCCESSFUL FOR RESOURCE(FI:EMLSTS ) 09/13/19 15:06:50 MBCPCMSV x.x RJS1
DFHFC0204 09/13/2019 15:06:50 T540 PMVST05B RJS1 MBC0 Resource definition for FILE EMLSTS has been updated.
MBCE382-FI:EMLSTS OPE ENA UAD DS:MACS.EMLSTS 09/13/19 15:06:52 MBCPPLA x.x RJS1
DFHFC0204 09/13/2019 15:06:50 T540 PMVST05B RJS1 MBC0 Resource definition for FILE EMLSTS has been updated.
MBCE382-FI:EMLDOC CLO ENA UAD DS:MACS.EMLDOC 09/13/19 15:06:52 MBCPPLA x.x RJS1
MBCE380-TR:EML SET ENA 09/13/19 15:06:52 MBCPPLA x.x RJS1
MBCE390-PG:EMLP100 SET ENA 09/13/19 15:06:52 MBCPPLA x.x RJS1
MBCE133-ALOR SUCCESSFUL FOR RESOURCE(TX:CSSL ) 09/13/19 15:06:52 MBCPPLA x.x RJS1
MBCE384-TX:CSSL OPE ENA FOR DS:SEC1.MSGUSR 09/13/19 15:06:52 MBCPPLA x.x RJS1
MBCE386-TD:CADL SET ENA 09/13/19 15:06:52 MBCPPLA x.x RJS1
MBCE351-ALOG FOR GROUP(PLT.T540 ) SUCCESSFUL 09/13/19 15:06:52 MBCPPLA x.x RJS1

7.5 Sample Status Tracking Reset Processing CICS Log
Below is a sample CICS log showing messages produced by MBCPRSET during Status Tracking CICS startup
including comments enclosed within braces {}. MBCPRSET only runs if MBCPPLT is present in the CICS startup PLT
and STATFLAG=Y. There are two phases for Reset Processing, one for BATSTAT commands and a second for
BATCSTS resources. Any messages created on behalf of executing a command or processing a resource should
precede the actual message created by MBCPRSET including CICS commands denoted by DFH prefix.
For BATSTAT processing, each processed command has an indicator such as <OK, <WARN or <ERR indicating the
success or failure of the command.
For BATCSTS processing, MBCPRSET displays a message for each processed resource indicating the success or
failure of the reset status.
{CSMT Message written by MBCPRSET indicating BATSTAT phase of Status Tracking startup processing has begun}
MBCE100-BATSTAT STATUS RESET PROCESSING STARTING 07/25/20 14:12:21 MBCPCMFI x.x RJS1
{Multiple MBC CSMT messages precede a generic command}
MBCE120-CLOS SUCCESSFUL FOR FILE EMLDIR 07/25/20 14:12:21 MBCPCMFI x.x RJS1
MBCE120-CLOS SUCCESSFUL FOR FILE EMLDOC 07/25/20 14:12:21 MBCPCMFI x.x RJS1
MBCE120-CLOS SUCCESSFUL FOR FILE EMLDST 07/25/20 14:12:21 MBCPCMFI x.x RJS1
MBCE120-CLOS SUCCESSFUL FOR FILE EMLRTE 07/25/20 14:12:21 MBCPCMFI x.x RJS1
MBCE120-CLOS SUCCESSFUL FOR FILE EMLSTS 07/25/20 14:12:21 MBCPCMFI x.x RJS1
CLOS EML* <OK 07/25/20 14:12:21 MBCPRSET x.x RJS1
{Sample MBC CSMT warning message preceding a generic command}
MBCE110-NO FILES MATCHING EML*Z WERE FOUND 07/25/20 14:12:23 MBCPCMFI x.x RJS1
{Sample CSMT command message indicating a completion with a warning}
CLOS EML*Z <WARN 07/25/20 14:12:23 MBCPRSET x.x RJS1
{Sample CICS CSFL message preceding a successful CSMT command completion}
DFHFC0204 09/11/2019 14:12:23 T540 MBCRXCI RJS1 MBCX FCT entry for EMLSTS has been updated.
INQY EMLSTS <OK 07/25/20 14:12:24 MBCPRSET x.x RJS1
{Sample MBC error message preceding a failing command}
MBCE111-FILE EMLZZZ NOT FOUND IN TABLES 07/25/20 14:12:24 MBCPCMFI x.x RJS1
CLOS EMLZZZ <ERR 07/25/20 14:12:24 MBCPRSET x.x RJS1
{CSMT Message written by MBCPRSET indicating BATSTAT phase of Status Tracking startup processing has completed}
MBCE101-BATSTAT STATUS RESET PROCESSING COMPLETED 07/25/20 14:12:24 MBCPCMFI x.x RJS1
{CSMT Message written by MBCPRSET indicating BATCSTS phase of Status Tracking startup processing has begun}
MBCE100-BATCSTS STATUS RESET PROCESSING STARTING 07/25/20 14:12:24 MBCPCMFI x.x RJS1
DFHFC0201 10/25/2019 14:12:24 T540 Non-RLS file EMLDST has been deallocated. Module DFHFCN.
DFHFC0204 10/25/2019 14:12:24 T540 PMVST05B CICSUSER MBCR Resource definition for FILE EMLDST has been updated.
DFHFC0200 10/25/2019 14:12:24 T540 Non-RLS file EMLDST has been allocated to data set MACS.EMLDST. Module DFHFCN.
MBCE382-FI:EMLDST OPE ENA UDA DS:MACS.EMLDST 07/25/20 14:12:26 MBCPCMFI x.x RJS1
DFHFC0201 10/25/2019 14:12:26 T540 Non-RLS file EMLRTE has been deallocated. Module DFHFCN.
DFHFC0204 10/25/2019 14:12:26 T540 PMVST05B CICSUSER MBCR Resource definition for FILE EMLRTE has been updated.
DFHFC0200 10/25/2019 14:12:26 T540 Non-RLS file EMLRTE has been allocated to data set MACS.EMLRTE. Module DFHFCN.
MBCE382-FI:EMLRTE OPE ENA UAD DS:MACS.EMLRTE 07/25/20 14:12:29 MBCPCMFI x.x RJS1
MBCE382-FI:FRSAALTX CLO DIS FOR DESIRED STATE: UNALLOCATED 07/25/20 14:12:29 MBCPCMFI x.x RJS1
MBCE382-FI:FRSABASE CLO DIS FOR DESIRED STATE: UNALLOCATED 07/25/20 14:12:29 MBCPCMFI x.x RJS1
MBCE382-FI:FRSESDS CLO DIS FOR DESIRED STATE: UNALLOCATED 07/25/20 14:12:29 MBCPCMFI x.x RJS1
MBCE382-FI:FRSKSDS CLO DIS FOR DESIRED STATE: UNALLOCATED 07/25/20 14:12:29 MBCPCMFI x.x RJS1
MBCE390-PG:EMLP100 SET DIS 07/25/20 14:12:29 MBCPCMFI x.x RJS1
MBCE386-TD:CDB2 SET ENA 07/25/20 14:12:29 MBCPCMFI x.x RJS1
MBCE386-TD:CEJL SET ENA 07/25/20 14:12:29 MBCPCMFI x.x RJS1
MBCE380-TR:EML SET DIS 07/25/20 14:12:29 MBCPCMFI x.x RJS1
{CSMT Message written by MBCPRSET indicating BATSTS phase of Status Tracking startup processing has completed}
MBCE101-BATCSTS STATUS RESET PROCESSING COMPLETED 07/25/20 14:12:29 MBCPCMFI x.x RJS1

Section VIII
Startup Commands
8.1 Startup Commands Overview
Startup Commands allow you to store MBC commands in the BATCSTS file for processing during CICS startup. MBC
PLT program MBCPPLQ processes stored commands exactly as if you processed them using the Online Command
Processor except they are persistant and processed each time the PLT program is run during startup. You can store
commands to start transactions, manipulate files, send messages, etc. using standard MBC commands.
8.1.1 Storing Startup Commands

Commands are stored using the MBCBATCH program with special header CSCQ. The CSCQ header card replaces the
standard CICS header and instead of executing commands that follow, the commands are sent to the target region(s)
where they are stored in the region BATCSTS file. NOTE: Each MBCBATCH execution with a CSCQ card replaces all
Startup Commands in the target region(s), so we recommend all Startup Commands be kept in a common member to
assist in their administration.
Sample MBCBATCH Input cards

STRL PAY1 LINES=0 LEN=000 USER=PAYMST
MESG ALL THE PAYROLL SYSTEM HAS BEEN ACTIVATED
CEMT SET TERM(PRT1) OUT
Sample MBCBATCH Job Log
MBCB001-MBCBATCH 2.1 STARTING JOB(JOB12345:MBC$RUN ) USER(RJS1)

MBCB003-COMMAND PRE-PROCESSING STARTING 05/22/20 11:12:49 MBC$RUN x.x RJS1
MBCB004-COMMAND EXECUTION PHASE STARTING USING EXCI 05/22/20 11:12:49 MBC$RUN x.x RJS1
{Sample CSCQ header card followed by connection complete message with Execution User}
CSCQ T540 <HDR 05/22/20 11:12:49 MBC$RUN x.x RJS1
MBCB020-CONNECTION COMPLETE TO APPL(T540 ) XUSR(RJS1) 05/22/20 11:12:50 MBC$RUN x.x RJS1
{Message indicating commands will be stored for Startup Command processing}
MBCE185-COMMANDS STORED FOR STARTUP COMMAND PROCESSING 05/22/20 11:12:50 MBC$RUN x.x RJS1
STRL PAY1 LINES=0 LEN=000 USER=PAYMST 05/22/20 11:12:50 MBC$RUN x.x RJS1
MSGL ALL LINES=1 NEWS=N 05/22/20 11:12:50 MBC$RUN x.x RJS1
THE PAYROLL SYSTEM HAS BEEN ACTIVATED AT CICS STARTUP
CEMT SET TERM(PRT1) OUT 05/22/20 11:12:50 MBC$RUN x.x RJS1
MBCB022-CLOSE CONNECTION COMPLETE FOR APPL(T540) 05/22/20 11:12:50 MBC$RUN x.x RJS1
MBCB002-MACKINNEY BATCH TO CICS 2.1 ENDING MAXCC(000) 05/22/20 11:12:50 MBC$RUN x.x RJS1
Sample CICS Log for Storing Startup Commands
{CICS CSMT Message indicating Connection has been completed from Batch job }
MBCE175-CONNECTED FROM BATCH(JOB14200) USER(RJS2) XUSR(RJS2) 05/22/20 11:12:50 MBCPXCI x.x RJS1
{CSMT MBC Message written to indicate following Startup Commands wont be executed but will replace any existing commands}
MBCE185-FOLLOWING CMDS WILL REPLACE MBC STARTUP CMD LIST BUT NOT BE EXECUTED
{CSMT MBC Messages written as an audit trail for old Startup Commands replaced during this run indicated by “<REPL”}
MSGL ALL LINES=1 NEWS=N <REPL 05/22/20 11:12:50 MBCPSCW x.x RJS1
CLOS EMLDOC <REPL 05/22/20 11:12:50 MBCPSCW x.x RJS1
CLOS EMLRTE <REPL 05/22/20 11:12:50 MBCPSCW x.x RJS1
{CSMT MBC Messages written as an audit trail for new Startup Commands stored during this run indicated by “<STOR”}
STRL PAY1 LINES=0 LEN=000 USER=PAYMST <STOR 05/22/20 11:12:50 MBCPXCI x.x RJS1
MSGL ALL LINES=1 NEWS=N <STOR 05/22/20 11:12:50 MBCPXCI x.x RJS1
CEMT SET TERM(PRT1) OUT <STOR 05/22/20 11:12:50 MBCPXCI x.x RJS1
Section VIII – Startup Commands 155

8.1.2 Executing Startup Commands
Startup Commands are executed by adding program MBCPPLQ to your PLTPI (see Section 1.9.7). Any Startup
Commands found in the region BATCSTS file (see Section 1.2.3) will be processed when MBCPPLQ runs. Below is a
CICS log of a sample MBCPPLQ execution.
Sample CICS Log for Startup Commands execution
{Message indicating MBC Startup Command Processing is beginning}

MBCE180-STARTUP COMMAND PROCESSING BEGINNING 05/22/20 12:54:02 MBCPPLQ x.x RJS1
{Messages for each of the MBC Startup Commands}
MBCE107-TRANID PAY1 START SUCCESSFUL: TERM:NONE USERID:PAYMST 05/22/20 12:54:02 MBCPPLQ x.x RJS1
MBCE122-MESG ROUTED TO: ALL <OK 05/22/20 12:54:05 MBCPCMNF x.x RJS1
MSGL T05A LINES=2 NEWS=N <OK 05/22/20 12:54:05 MBCPPLQ x.x RJS1
CEMT SET TERM(PRT1) OUT <OK 05/22/20 12:54:06 MBCPPLQ x.x RJS1
{Message indicating MBC Startup Command Processing has completed}
MBCE181-STARTUP COMMAND PROCESSING ENDED 05/22/20 12:54:06 MBCPPLQ x.x RJS1
8.1.3 Deleting Startup Commands

If you want o remove all Startup Commands without adding new command, you can use the following special command:
STSD SQ *DEL
Sample MBCBATCH Input cards to remove ALL Startup Commands without adding new commands
STSD SQ *DEL
Sample CICS Log for Startup Commands execution
{Message indicating MBC Startup Command Processing is beginning}

MBCE175-CONNECTED FROM BATCH(JOB34418:MBC$RUN) USER(RJS1) XUSR(RJS1) 05/22/20 12:54:02 MBCPXCI x.x RJS1
MBCE185-FOLLOWING WILL REPLACE STARTUP CMD LIST BUT NOT BE EXECUTED 05/22/20 12:54:05 MBCPCMNF x.x RJS1
{Messages for each of the MBC Startup Commands being removed}
STAR HPRA T05B <DEL 05/22/20 12:54:02 MBCPSCW x.x RJS1
MSGL T05B LINES=2 NEWS=N <DEL 05/22/20 12:54:05 MBCPSCW x.x RJS1
{Message indicating MBC Startup Command delete has completed}
STSD SQ *DEL <OK 05/22/20 12:54:06 MBCPXCI x.x RJS1
156 Section VIII – Startup Commands

Section IX
Messages and Codes
9.1 Messages
Messages are listed in numeric order. Batch messages are indicated by a ‘B’ in the fourth position. Online messages are
indicated by an ‘E’ in the fourth position. Each message is followed by a description and subsequent action taken by the
program or required of the user.
Messages MBCE000 is produced by CICS server programs.
MBCE000-ERROR rrrrrrrr (cccccccc) ON ffffffff OF ssssssss IN PGM pppppppp
Description: A condition was detected not anticipated by MBC.
rrrrrrrr is the error response detected. This is usually an error code description like NOTFND. If the description is not
available, the value contains either the EIBRCODE or EIBRESP.
cccccccc is the optional EIBRESP2 value in hex
ffffffff is the function attempted. This is usually a function description like STARTBR. Occasionally the description
may not be available and instead contains the EIBFN code value.
ssssssss is the resource the function is executed against such as a file
pppppppp is the MBC program identifier in control at the time of the error
These error codes can be found in this manual in the appendices or in your CICS Applications Programmers Reference.
Please consider the possible causes before calling MacKinney Systems.
Messages MBCB001 through MBCB099 are produced by MBCBATCH.
MBCB001-MBCBATCH rrr STARTING JOB(pppxxxxx:nnnnnnnn) USER(uuuuuuuu)
Description: Execution of client program MBCBATCH has started. RRR is the release number, UUUUUUUU is the Userid
associated with the Job, PPPXXXXX is the Job type and number and NNNNNNNN is the job name. The job type PPP can be
JOB/STC/PJB to identify z/OS JOB, z/OS Started Task or z/VSE Power, and XXXXX represents the unique job number.
This message is issued each time MBCBATCH executes and is for informational purposes only.
MBCB002-MACKINNEY BATCH TO CICS rrr ENDING MAXCC(ccc)
Description: Execution of client program MBCBATCH has ended. RRR is the release number and CCC is the return code
of the current MBCBATCH step. This message is issued each time MBCBATCH executes and is for informational
purposes only.
MBCB003-COMMAND PRE-PROCESSING STARTING
Description: The command pre-processing stage of MBCBATCH has started. This stage reads all of the card input and
does general editing of the commands. This message is issued each time MBCBATCH executes and is for informational
purposes only.
MBCB004-COMMAND EXECUTION PHASE STARTING USING xxxxx
Description: The command execution stage of MBCBATCH has started using xxxxx = EXCI or TCPIP. This stage
processes all of the commands sending them to their target CICS Applid to execute. This message is issued each time
MBCBATCH executes and is for informational purposes only.
Section IX – Messages and Codes 157
MBCB005-COMMAND FAILURE SEE PREVIOUS MESSAGE. REPLY GO, CANCEL, OR RETRY.
Description: This message indicates a command did not execute successfully and operator intervention was requested. A
previous message should be displayed giving further information. It might also be necessary to review the CICS message
log (see TDMESGQ parameter) for additional messages. The following reply options can be entered: reply ‘GO’ to
continue processing the remaining commands after setting the return code to the ERRCMD value; reply ‘CANCEL’ to
cancel the job step and set the return code to the ERRCNCL value; reply ‘RETRY’ to retry executing the command (after
you have made some intervening change to correct the cause of the error). In the case of ‘RETRY’, the message is
redisplayed if the same or other error occurs during the retry.
MBCB006-APPL(aaaaaaaa) CONNECT ERROR: BYPASSING CARDS TO NEXT HDR (rrr)
Description: The EXCI pipe (z/OS) or TCP/IP pipe (VSE) to Applid aaaaaaa would not open. If option DOWNNON or
DOWNSPC is set to ‘Bypass’, rrr is ‘OPT’. If the operator replied ‘Bypass’ to MBCB007, rrr is ‘OPR’. If CICS was
flagged as down by APPLSTS (Section 2.1.3), RRR is ‘STS’. If rrr is SEC, then a security error occurred attempting to
connect (look for additional security messages for additional information). The remaining cards are bypassed until the next
CICS header is found, no error code is set and no Status Tracking records are produced.
MBCB007-APPL(aaaaaaaa) CONNECT FAILED: ENTER RETRY|BYPASS|FLUSH|CANCEL{|DOWN}
Description: The EXCI pipe (z/OS) or TCP/IP pipe (VSE) to Applid aaaaaaaa could not be opened and operator
intervention was requested. Verify the CICS for Applid aaaaaaaa is up and IRC is Open (CEMT INQ IRC). Enter one of
the following reply options: ‘RETRY’ to retry opening the pipe (after you have corrected the cause of the error); ‘BYPASS’
to skip processing cards until the next CICS header without setting a return code or producing Status Tracking records;
‘FLUSH’ to skip processing cards until the next CICS header after setting the return code to the ERRDOWN value;
‘CANCEL’ to cancel the job step and set the return code to the ERRCNCL value. In the case of ‘RETRY’, the message is
redisplayed if the same or other error occurs during the retry. The DOWN reply option only shows if option APPLSTS is
set to ‘Y’ or ‘F’. Replying ‘DOWN’ flags the Applid as down in the BATSTAT file (Section 2.1.3).
MBCB008-APPL(aaaaaaaa) CONNECT ERROR: FLUSHING CARDS TO NEXT HDR (rrr)
Description: The EXCI pipe (z/OS) or TCP/IP pipe (VSE) to Applid aaaaaaaa would not open. If option DOWNNON or
DOWNSPC is set to ‘Flush’, rrr is ‘OPT’. If the operator replied ‘Flush’ to MBCB007, rrr is ‘OPR’. If CICS was flagged
as down by APPLSTS (Section 2.1.3), rrr is ‘STS’. The remaining cards are bypassed until the next CICS header is found
and the return code is set to the ERRDOWN value. Status Tracking records will be produced if Status Tracking is active.
MBCB009-STEP BEING CANCELED DUE TO PREVIOUS ERROR. ALL REMAINING CARDS IGNORED
Description: A previous command error or Connect failure has occurred and FAILACT (for command error), DOWNNON
or DOWNSPC (for Connect failure) is set to ‘CANCEL’ or the operator has replied ‘CANCEL’. The remaining cards are
ignored, no Status Tracking records are produced and the return code set to the ERRCNCL value.
MBCB010-BATSTAT PROCESSING STARTING
Description: The Status Tracking (BATSTAT) processing stage of MBCBATCH has started. This stage processes all
eligible commands to write to the BATSTAT file.
MBCB011-BATSTAT RESOURCE UPDATES COMPLETED FOR THE FOLLOWING COMMANDS
Description: This message precedes message pairs MBCB012 and MBCB013. Each command processed is logged using
the two messages MBC012 and MBC013.
158 Section IX – Messages and Codes

MBCB012-UPDATED RESOURCE APPL:aaaaaaaa TYPE:tt NAME:nnnnnnnn
Description: This message indicates the command identified in the following MBCB013 message was processed by Status
Tracking for Applid AAAAAAAA. TT represents the type of resource: FI-file, TR-transaction, PG-program, TD-TDQ or
TX-Extrapartition TDQ and NNNNNNN represents the resource file, transaction, program, or TDQ name.
MBCB013-CMD: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Description: This message identifies a command that has been processed by Status Tracking and saved to the BATSTAT
file. The command will be part of the Status Tracking processing by MBC during the next CICS recycle for the Applid
specified in the preceding MBCB012 message. The preceding MBCB012 message identifies the Applid, Resource Type
and Name associated with the command.
MBCB014-BATSTAT DD/DLBL MISSING
Description: Option STATFLAG=Y or APPLSTS is set to 'Y' or ‘F’, but no DD or DLBL was found in the MBCBATCH
JCL for BATSTAT file. Add the BATSTAT DD/DLBL, z/OS users see user exit MBCBOPSX for dynamic allocation, or
set STATFLAG and APPLSTS to ‘N’ and retry the job.
MBCB015-BATSTAT/BATCSTS OPEN FAILED, STATUS TRACKING BYPASSED
Description: An error occurred opening the BATSTAT or BATCSTS files. Status Tracking could not be processed. Check
BATSTAT or BATCSTS file definitions and status to help determine why the file could not be opened. Correct and retry.
MBCB016-BATSTAT DYNALOC FOR dddddddddddddddddddddddddddddddddddddddddddd
Description: Issued by user exit MBCBOPSX to indicate dynamic allocation for BATSTAT file with dataset DDD-DDD
was successful.
MBCB017-BATSTAT ALOCERR FOR dddddddddddddddddddddddddddddddddddddddddddd(rrrr)
Description: Issued by user exit MBCBOPSX to indicate dynamic allocation for BATSTAT file with dataset DDD-DDD
failed with reason code RRRR. Reason codes for either of the above error messages can be found in the MVS Authorized
Assembler Services Guide. Refer to the Requesting DYNAMIC ALLOCATION Functions chapter. See Message
MBCE132 for the most common reason codes.
MBCB018-SYSxxx LU INVALID OR ABOVE ALLOWED RANGE. LOGXDD=N FORCED
Description: This message is only for VSE users specifying LOGXDD=Y. The message is issued when the SYSxxx LU
specified in MBCRLXGO is not present in the LUB table. If SYSxxx is not SYS025 (Default), then a new value was
zapped in program MBCRLXGO. The valid range of LU’s is 000-254, but local restrictions set the actual upper range. As
the message indicates, LOGXDD=N is forced for this execution and all output is written to SYSLST.
MBCB019-PLEASE ENTER VALID MBC PASSWORD BEFORE USING MBC
Description: This message appears if MBC is unable to determine a valid password. Verify or enter a valid password.
MBCB020-CONNECTION COMPLETE TO APPL(aaaaaaaa)
Description: Indicates an EXCI pipe connection to CICS Applid AAAAAAAA successfully opened and following
commands are sent to the target Applid.
MBCB021-CONNECT FAILED: APPL(aaaaaaaa) RESP(cccccccc) REASON(rrrrrrrr-ssssssss)
Description: Indicates an error occurred trying to open an EXCI pipe connection to CICS Applid AAAAAAAA. The
response code is CCCCCCCC and RRRRRRRR-SSSSSSSS is the reason and sub-reason code. These errors are documented
in the CICS External Interfaces Guide. The most common causes are: the target CICS is down, IRC is not running, external
security is not allowing the connection (Section 2.3.1), the region name is being used rather than the APPLID name, or the
connection definitions are missing or invalid.
For RESP(8) REASON(0201):

1) Issue CEMT INQ IRC; IRC must be OPEN. Bouncing the region may be required to wake up IRC even with IRC OPEN.
2) IRCSTRT=YES is required in the SIT.
3) If there is no local CICS region in the image (LPAR) where the batch job was submitted, you must specify the SVC
parameter the external CICS interface is to use by coding a CICSSVC parm in the DFHXCOPT table. The default
DFHXCOPT table specifies an SVC of zero telling external CICS to get the SVC from MVS. If you are not running a
CICS in the image, you must provide your own DFHXCOPT that specifies the correct CICSSVC value and place it in
the MBC loadlib. DFHXCOPE is an alias for DFHXCOPT in later CICS releases and must also be updated.
4) Check CICS log for security violations or other errors.
5) Some of the subreason codes are defined in the CICSTS32.CICS.SDFHMAC(DFHIRSDS) member.
For RESP(8) REASON(203-92):

IRC is CLOSED. 203 implies "No CICS" and 92 implies "system not logged on".
IRC may show OPEN and 203-92 could still occur.
1) If issuing CEMT SET IRC CLO, IRC hangs, the problem is with IRC. Recycling may be the only way to correct.
2) Look for message DFHIR3791 in startup indicating:

Unable to start interregion communication because ISC=NO has been specified.
Add ISC=YES to successfully connect after recycling. Check for any other DFHIR* messages in startup.
3) If the failing region has DFHIR3777 message, this indicates an IRC problem.
May need to increase the sysplex MAXGROUP setting to get IRC up. Once IRC is up, you should be able to connect.
The DFHIR3777 message also implies MAXMEMBER setting might need changing.
4) Issue CEMT INQ CONN and look for MBCX. Add if missing.
For RESP(8) REASON(203-104):

CICS is not up or RDO definitions are not installed for the connection, sessions, and/or programs. Check the following:
1) CEMT I IRC (should indicate a value of OPE)
2) CEMT I CONN (should show an entry as below, Net MUST be MBCRXCI)

Con(MBCX) Net(MBCRXCI ) Ins Irc Exci
3) CEMT I TRAN(MBCX) (should show values below)

Tra(MBCX) Pri( 001 ) Pro(DFHMIRS ) Tcl( DFHTCL00 ) Ena Sta
Prf(DFHCICSA) Uda Any Iso Bac Wai
4) Verify the target CICS is specified as APPLID in SIT and is not just the region (Job) name
5) Verify SESSION prefix value (default MS) is unique. If prefix is in use, SESSION install will fail with these messages:
DFHZC5939 {applid} Install for MS1 failed. Duplicate session- or modegroup
DFHZC6216 {applid} Install for SESSION (MS1) failed and caused the backout for CONNECTION (MBCX).

MBCB022-CLOSE CONNECTION COMPLETE TO APPL(aaaaaaaa)
Description: Indicates a pipe connection to CICS Applid AAAAAAAA was successfully closed.
MBCB023-DPL REQUEST FAILED: APPL(aaaaaaaa) EXCI RESP(cccccccc) REASON(rrrrrrrr-ssssssss)
Description: Indicates an error occurred trying to send a command to the CICS Applid AAAAAAAA. The EXCI response
code is CCCCCCCC, and RRRRRRRR-SSSSSSSS is the reason and sub-reason code. These errors are documented in the
CICS External Interfaces Guide. Check the CICS or batch job log for additional messages to further explain the reason for
the failure.
MBCB024-DPL RESP(cccccccc) RESP2(rrrrrrrr) ABEND CODE(bbbb)
Description: Indicates DPL RESP, RESP2 and optional ABEND code returned with the DPL request identified previously.
See message MBCB023 also. The RESP code is CCCCCCCC, the RESP2 code is RRRRRRRR and the ABEND code is
BBBB. These errors are documented in the CICS External Interfaces Guide.
MBCB025-ENQ FOR APPLID(aaaaaaaa) FAILED RC(nnn)
Description: The attempt for obtaining the ENQ lock for Applid AAAAAAAA failed with return NNN. RC values are
documented in MVS Programming: Assembler Services Reference, Volume 1 (ABEND-HSPSERV)
MBCB026-BATCNTL DSN MISMATCH BETWEEN BATCH JOB(nnnnnnnn) AND CICS(aaaaaaaa)
Description: Batch job NNNNNNNN is using a different BATCNTL DSN value than the CICS AAAAAAAA DSN value.
This is a warning message. The return code value is not changed by this warning and MBC continues processing the
commands for this job. However, to prevent possible unwanted results, the Batch job BATCNTL DSN should match the
target CICS DSN.

Messages MBCB030 through MBCB034 are produced by batch program for VSAM errors.
MBCB030-BATCNTL DD/DLBL MISSING
Description: A VSAM operation requiring the BATCNTL file failed to complete because there is no DD or DLBL present
in the current job step. Add the BATCNTL DD/DLBL and retry the job.
MBCB031-ffffffff ERROR: RC(ccc) REASON(rrr) FUNCTION: xxxxxxxx
Description: A VSAM error has occurred while processing file FFFFFFFF. The function being attempted is indicated by
XXXXXXXX. The return code is ccc and the reason code is rrr. Refer to the DFSMS Macro Instructions for Data Sets or
VSE/VSAM Messages and Codes manual for further explanation of the return codes and reason codes associated with the
indicated function.
MBCB032-GENACB FAILED: R15(xxx) R0(yyy)
Description: An attempt to open a VSAM file has occurred while executing the GENACB macro. The return code value in
R15 (XXX) was returned. R0 value YYY may provide additional information as to the error. Check for additional messages
indicating the file failing to open and refer to the DFSMS Macro Instructions for Data Sets or VSE/VSAM Messages and
Codes manual for possible errors associated with the GENACB macro.
MBCB033-GENRPL FAILED: R15(xxx) R0(yyy)
Description: An attempt to open a VSAM file has occurred while executing the GENRPL macro. The return code value in
R15 (XXX) was returned. R0 value YYY may provide additional information for the error. Check for additional messages
indicating the file failed to open and refer to the DFSMS Macro Instructions for Data Sets or VSE/VSAM Messages and
Codes manual for possible errors associated with the GENRPL macro.

MBCB040-INVALID CICS NUMBER OR APPLID IN HEADER IN APPL CARD
Description: An APPL card was input with a number specified which is not in the range 1-99 or no matching Applid was
found on the BATCNTL file.
MBCB041-UPDATE FOR SYSTEM NUMBER(nn) APPLID(aaaaaaaa)
Description: An APPL card was processed supplying Applid AAAAAAAA for system number NN. The entry was updated in
the BATCNTL file.
MBCB042-UPDATE FOR PASSWORD(n) VALUE(pppppppppppppppp)
Description: A PASS card was processed and password value PPPPPPPPPPPPPPPP was assigned to slot N in the
BATCNTL file. This value can be displayed by selecting the Password Maintenance option from the Administration Menu
MBCB043-INVALID PASSWORD NUMBER (1-6) OR BLANK VALUE
Description: A PASS card was submitted with an incorrect password number value (must be 1-6) or the password value is
blank. Reenter valid password number or value and retry.
MBCB044-SHUTDOWN COMMAND NOT ALLOWED
Description: A SHUT command was input to MBCBATCH, but installation option SHUTCMD is set to ‘N’. Change
option SHUTCMD to ‘Y’ if CICS may be shut down by a SHUT command.
MBCB045-INVALID CEMT COMMAND FORMAT OR COMMAND NOT ALLOWED
Description: A CEMT command was input to MBCBATCH, but either the format is invalid or the type of command is not
allowed (i.e. PERFORM).
MBCB046-SHUT COMMAND REQUIRES NON-BLANK SHUTTERM VALUE
Description: The SHUT command requires a value for SHUTTERM and the current value is blank. Please specify a valid
TERMID value for SHUTTERM such as CNSL. TERMID must support ATI.
MBCB047- CEDA/CDAL COMMAND NOT ALLOWED
Description: A CEDA or CDAL command was input to MBCBATCH, but installation option CEDACMD is set to ‘N’.
Change option CEDACMD to ‘Y’ if you want to allow CEDA or CDAL command.
MBCB048-WAIT TIME INVALID: SPECIFY MSS WHERE M=0-9 MIN AND SS=01-60 SECS
Description: A WAIT command was input to MBCBATCH with an invalid format. Specify wait time in the format mss
where M=0-9 minutes and SS=01-60 seconds.
MBCB049-RESOUCE GROUP CMDS NOT SUPPORTED WITH ALL OR APPLGRP HEADER
Description: Resource Group commands (i.e. ALOG, OPEG, etc.) cannot be used with ALL or APPLGRP CICS headers.
Since Resource Groups are defined for a specific Applid, a specific Applid value must be used on the CICS header.

MBCB050-LOAD OF OPTIONS AND APPLIDS FROM BATCNTL FAILED
Description: An error occurred during the initialization stages of MBCBATCH trying to load the options and Applids from
the BATCNTL file. Check the log for any additional messages the might further explain the error. Also, verify the options
(and Applids) were initialized. You can use the online Installation Options screen to initialize and save the options and
Applids to the BATCNTL file
MBCB051-MBC OPTIONS HAVE NOT BEEN INITIALIZED {batch message}

MBCE051-MBC OPTIONS RECORD UNAVAILABLE OR NOT INITIALIZED {online message}
Description: A function requiring use of the MBC Installation Options record such as MBCBATCH, one of the utilities or
online access was requested before the options were initialized. Use batch utility MBCBCUTL or use the online Installation
Options screen to initialize and save the options to the BATCNTL file before using. NOTE: An improper file definition or
running the old CEMT from Batch program against the MBC BATCNTL file can corrupt the record (and file) requiring the
file to be deleted and redefined and the record rebuilt.
MBCB052-INVALID COMMAND {SET BY EXIT MBCBCMDX}
Description: The indicated command following this message was determined invalid either by the command pre-processor
or by exit MBCBCMDX if “SET BY EXIT MBCBCMDX” appears in the message. If “SET BY MBCBCMDX” appears in
the message, then check MBCBCMDX source code. Otherwise, verify the identified command is a valid command and the
command format is valid.
MBCB053-OVERRIDE PARM OPTION INVALID OR OPTION CANNOT BE OVERRIDDEN
Description: An OPTR card was input to MBCBATCH and the specified option is either an invalid option or the option
cannot be overridden.
MBCB054-OVERRIDE PARM VALUE INVALID, xxxxxxxxxxxxxxxxxxxxxxxxx
Description: An OPTR card was input to MBCBATCH and the specified option valid is invalid. The text XXX-XXX
specifies the valid values. Specify a valid value and retry.
MBCB055-INVALID LENGTH ON STAR OR LINK COMMAND
Description: The length parameter on the STAR or LINK command is missing or invalid. See the command description for
the proper format of the command.
MBCB056- INVALID FORMAT OR MISSING PARAMETER
Description: A command is missing a parameter or is not in the proper format. See the command description for the proper
format of the command.
MBCB057-INVALID DBLC|DLOC CARD FORMAT
Description: The DBLC or DLOC card format is invalid. See the command description for the proper format of the
command.

MBCB060-START OF {CEMT|CEDA|QRY} LOG FOR xxxxxxxx
Description: A CEMT, CEDA, CDAL, QYRL or QRYS command card was executed on APPLID XXXXXXXX and the
returned messages follow this message in the batch job log or the extended data log (see Section 2.1.5). Additional text is
amended to the message if there are errors or warnings.
MBCB061-END OF {CEMT|CEDA|QRY} LOG FOR xxxxxxxx LINES(lllllll) RESOURCES(rrrrrrr)
Description: A CEMT, CEDA, CDAL, QYRL or QRYS command card was executed on APPLID XXXXXXXX. This
message follows the last returned resource and indicates the returned number of lines (LLLLLLL) plus the total resources
returned (RRRRRRR) resources. The MBCB060 and MBCB061 messages are not included in the returned lines count.
MBCB062-DPL RETURNING QUEUED LINES
Description: A CEMT, CEDA, CDAL, QYRL or QRYS command card was executed and MBCBATCH encountered a
DPL error while returning the resultant Inquiry Temporary Storage Queue. Check the CICS message log and the
MBCBATCH job log for additional messages to further explain the DPL error.
MBCB070-MISSING PARAMETER ON FOLOWING INPUT CARD
Description: A required parameter is missing on an input card. See the following card and refer to the command format to
determine the cause of the error.
MBCB071-PARM n LENGTH INVALID ON FOLLOWING INPUT CARD
Description: The length of parameter number N is incorrect. See the following card and refer to the command format to
determine the cause of the error.
MBCB072-TOO MANY PARMS ON FOLLOWING INPUT CARD
Description: The number of parameters specified on a command is incorrect. See the following card and refer to the
command format to determine the cause of the error.

MBCB080-FOLLOWING CARDS ARE BEING FLUSHED UNTIL VALID CICS HEADER CARD
Description: MBCBATCH was unable to determine a valid CICS header card. Until a new valid CICS header card is read,
the cards following this message are flushed.
MBCB081-APPLID(xxxxxxxx) INVALID OR DISALLOWED BY EXIT MBCBHDRX
Description: The target Applid XXXXXXXX is either invalid (leading spaces or other format error) or program
MBCBHDRX (header user exit) has disallowed its use by the current user. Examine the format of XXXXXXXX and if you
feel the value should be valid, then review the source for MBCBHDRX.
MBCB082- APPLGRP gggggggggggg DISALLOWED BY EXIT MBCBHDRX
Description: Program MBCBHDRX (header user exit) has disallowed the use of ApplGrp GGGGGGGGGGGG by the
current user. Review the source for MBCBHDRX if the CICS header should be a valid target ApplGrp.
MBCB083-APPLGRP gggggggggggg WAS NOT FOUND
Description: ApplGrp GGGGGGGGGGGG was not found in the BATCNTL file. Specify a valid ApplGrp. ApplGrp
values can be checked online.
MBCB084-ERROR OCCURRED READING APPLGRP gggggggggggg
Description: An error occurred while reading ApplGrp GGGGGGGGGGGG. Check the log for previous errors to further
explain why the error occurred.
MBCB085-UNABLE TO DETERMINE VALID APPLID FOR CICS ALL HEADER
Description: An error occurred while trying to determine the next target Applid with an ALL header. Check the log for
previous errors to further explain why the error occurred.
MBCB086-UNABLE TO DETERMINE VALID APPLID FOR CICS APPLGRP gggggggggggg HEADER
Description: An error occurred while trying to determine the next target Applid with APPLGRP header
GGGGGGGGGGGG. Check the log for previous errors to further explain why the error occurred.
MBCB087-INVALID APPLID NAME OR NUMBER IN CICS HEADER
Description: A CICS header card was input or implied and either a number was specified which is not in the range 1-99 or
no matching Applid was found for the number on the BATCNTL file.
MBCB088-UNABLE TO OPEN ANY APPLID IN CICS RLS1GRP gggggggggggg
Description: An RLS1GRP CICS header card was input and no Applid(s) found in the group GGGGGGGGGGGG could
be opened. Action and return code depends on value for DOWNNON (Section 3.4).
MBCB089-RLS COMMAND NOT SUPPORTED FOR VSE
Description: A VSE user has attempted to process RLS command but RLS is not supported for VSE. Processing is ended
with a command error.

MBCB090-INVALID IF COMMAND CARD FORMAT
Description: An IF command card was input to MBCBATCH with an invalid format. Check the manual for the valid
command format.
MBCB091-INVALID IF LEVEL DEPTH (MAX IS 3)
Description: The maximum IF nesting level depth is 3. Verify each IF must be ended with an ENDIF or reduce the level of
nesting.
MBCB092-TOO MANY ELSE CARDS AT SAME IF LEVEL DEPTH
Description: Only one ELSE card can be specified per IF level.
MBCB093-UNPAIRED IF/ENDIF CARDS
Description: An IF (or ENDIF) card was encountered without a matching ENDIF (or IF).
MBCB094-INVALID SET COMMAND CARD FORMAT
Description: A SET command card was input to MBCBATCH with an invalid format. Check the manual for the valid
command format.
MBCB095-INVALID DOWNSTS COMMAND CARD FORMAT
Description: A DOWNSTS command card was input to MBCBATCH with an invalid format. Check the manual for the
valid command format.
MBCB096-NEW VALUE SET FOR vvvvvvvv(nnn)
Description: This message is displayed as a result of a SET command changing the value of variable VVVVVVVV to new
value NNN. VVVVVVV can be MAXCC or one of up to 8 user variables.
MBCB097-INVALID SET COMMAND CARD AMOUNT
Description: A SET command card was input to MBCBATCH with an invalid amount. Amount must be between 0 and
255.

Messages MBCE100 through MBCB199 are produced by online programs.
MBCE100-BATSTAT|BATCSTS RESET STARTING FOR ddd…ddd
Description: Status Tracking Reset Processing has started. Processing is performed in two phases, with phase one for the
BATSTAT file and phase two for the BATCSTS file. ddd…ddd is the BATSTAT or BATCSTS dataset name.
MBCE101-BATSTAT RESET PROCESSING COMPLETED
Description: Program MBCPRSET has completed status tracking Reset Processing. Processing is performed in two phases,
first for the BATSTAT file and secondly for the BATCSTS file.
MBCE102-NO RECORDS PROCESSED FROM BATSTAT FILE
Description: Program MBCPRSET has completed BATSTAT status tracking Reset Processing and no records were
processed for the Applid in which MBCPRSET was running.
MBCE103-INVALID COMMAND:
Description: Either the BATSTAT or BATCSTS file contains a record with a command which is not valid for status
tracking or an invalid or disallowed command is being used with the online processor.
MBCE104-NOT AUTHORIZED STATUS ASSUMED FOR BLANK USERID
Description: EXTSEC=Y was specified and no USERID was passed to online interface MBCPXCI program or MBCPTCI.
A security error is assumed for the command.
MBCE105-LINK TO PROGRAM xxxxxxxx WAS yyyyyyyyyyyy
Description: Link to program XXXXXXXX was ’Successful’ or ‘Unsuccessful’. If ‘Unsuccessful’, verify program
XXXXXXXX is defined to CICS and is located in a library accessible to CICS. Use CEMT INQ PROG (xxxxxxxx) to verify
the program is defined, then use CEMT SET PROG(xxxxxxxx) NEWCOPY to verify the program can be loaded.
MBCE106-LINK|LNKL ERROR xxxxxxxx
Description: Program XXXXXXXX, initiated by a MBC LINK or LNKL command, returned an ‘ERROR’ response in the
COMMAREA. Data returned by LINK command is appended to the end of the message. See LINK or LNKL command
description in Section 5.2.
MBCE107-TRANSACTION tttt STARTED AT TERMINAL yyyy SUCCESSFULLY
Description: Self-explanatory, for informational purposes only.
MBCE108-RESERVED FOR CICS/MESG ERRORS
Description: This message reserved for messages produced by the MacKinney Systems’ Message interface.
MBCE109-CICS SHUTDOWN INITIATED BY JOB(jjjjjjjj) USER(uuuuuuuu)
Description: CICS shutdown was initiated by a SHUT command input to MBCBATCH with jobname JJJJJJJJ submitted
by user UUUUUUUU.
MBCE110-NO FILES MATCHING ffffffff WERE FOUND
Description: A command attempt for generic file string FFFFFFFF was processed and no matching files were found.
MBCE111-FILE fffffff NOT FOUND IN TABLES
Description: Attempted access to file FFFFFFF has failed. Change FFFFFFF to a value defined in your RDO tables.
MBCE112-USER uuuuuuuu NOT AUTHORIZED FOR resource vvvvvvvv
Description: An attempt by user UUUUUUUU to start Tranid VVVV or access File VVVVVVVV has failed with a
NOTAUTH condition indicating the userid is not authorized for this action. Review and modify the security profiles for the
Tranid or File along with the User profile to determine if further action is needed.
MBCE113-FILE ffffffff IS REMOTE
Description: An attempt to perform a file action command (OPEN, CLOS, INQY, UPDT, etc.) against File FFFFFFFF
was attempted, but cannot be completed because the file is defined as REMOTE in the target CICS. File actions require the
command be sent to the CICS where the file is defined as local.
MBCE114-SVC99 SUPPORT IS NOT AVAILABLE FOR VSE
Description: An attempt to perform an action command requiring SVC99 support has been attempted. VSE does not
support SVC99. Processing ends with a command error.
MBCE115-MBC x.x IS MISSING SUPPORT FOR CICS rrrr, CONTACT VENDOR
Description: MBC x.x does not support CICS release rrrr. Please contact your vendor for possible PTFs or upgrade to an
MBC release to support CICS release rrrr.
MBCE116-NEWCOPY|PHASEIN SUCCESSFUL FOR PROGRAM pppppppp
Description: A NEWCOPY or PHASEIN for program PPPPPPPP was successful.
MBCE117-TRANID tttt NOT FOUND IN TABLES
Description: An attempt to invoke Tranid TTTT failed. Change TTTT to a valid value or add to your RDO tables.
MBCE118-TERMID ERROR IN cccc COMMAND FOR TERMID tttt
Description: An error occurred on the indicated terminal while executing a STAR or MESG command. Check for correct
terminal id in the batch command.
MBCE119-NEWCOPY|PHASEIN FAILED FOR PROGRAM pppppppp
Description: A NEWCOPY or PHASEIN for program PPPPPPPP failed.
MBCE120-yyyy SUCCESSFUL FOR FILE(ffffffff)
Description: Function YYYY for the indicated file was successfully completed.
MBCE121-yyyy FAILED FOR FILE(ffffffff)
Description: Function YYYY for the indicated file failed. The original status for the file remains unchanged. Check the
CICS log for more information about why the command failed. Try the same command using IBM’s CEMT function.
MBCE122-MESSAGE SENT TO rrrrrrrrr
Description: The message associated with a MESG command was successfully sent to the indicated destination.

MBCE123-UNABLE TO OPEN ffffffff FOR aaaaaaaa {STATUS RESET|PLT ALLOCATION} PROCESSING
Description: An error occurred opening an MBC file and the file could not be used for Status Tracking Reset (BATSTAT
or BATCSTS) or PLT Allocation (BATCNTL) Processing. If intentionally undefined, ignore this message. Otherwise,
check file definition(s) and status to help determine why the file would not open.
MBCE124-BATCSTS FILE UNAVAILABLE FOR aaaaaaaa STATUS UPDATE PROCESSING
Description: STATFLAG=Y was specified, but the BATCSTS file was not defined for the CICS region or is not available
for update processing (UPD, ADD, DEL). Status Update processing is ignored. It may be intentionally undefined. If so,
ignore this message. Otherwise, assure the BATCSTS file is defined and available for update access in the CICS region.
MBCE125-COMMAND FAILED - SEE CICS LOG
Description: This message is issued when a command failure has occurred without an accompanying explanation message.
See the CICS log for additional messages to help determine the reason for the command failure.
MBCE126-COMMAND PROCESSED WITH MIXED RESULTS – SEE CICS LOG
Description: A command involving multiple resources has completed with mixed results (some commands failed, some
were successful). Please refer to the CICS log for details on the failing commands.
MBCE127-DFHEMTA RETURNED ERRORS FOR CEMT COMMAND IN TRANSLATION PHASE
Description: A CEMT command listed prior to the DFHEMTA message has failed, mostly likely due to a syntax error. See
the following messages for additional information into the cause of the error and correct.
MBCE128-DFHEMTA RETURNED ERROR CODE xxx FOR CEMT COMMAND IN EXECUTION PHASE
Description: A CEMT command listed prior to the DFHEMTA message failed. See following messages for additional
information into the cause of the error and correct. NOTE: The DFHEMTA interface has not been documented by IBM
since CICS ESA Version 3 although its use is still supported. See Appendix G for a list of Error Codes.
MBCE129-DFHEMTA MAX LINES RETURNED. INQUIRY MAY BE INCOMPLETE
Description: A CEMT command was processed and the resultant list has filled the maximum area supported by the
DFHEMTA interface. The resultant list may be incomplete. As a work around, consider using a filter to return a fewer
number of entries (i.e. CEMT SET FIL(AB*) OPEN instead of FIL(A*) or for INQ commands use the QRYL or QRYS
commands (Section 5.2).
MBCE130-BATCH/ONLINE RELEASE MISMATCH
Description: There is a MBC release mismatch between MBCBATCH and MBCPXCI. Verify the correct matching
libraries are in place for both batch and online execution and retry.
MBCE131-LIST: xxxxxxxx WAS NOT FOUND IN SCAN OF PROGRAM MBCFLIST
Description: Program MBCFLIST does not contain an entry for the indicated file list. Check for correct spelling of the list
name on the command input. Also check for a missing quote on the end of a dataset name. This would cause all lists
following the file to not be found. You can find this problem by checking an assembly listing of MBCFLIST and scanning
the LOC column for the first address which does not end with 0 or 8. Each DC should start on a double word boundary
(address ends with 0 or 8). The DC immediately before the first bad address is in error.
MBCE132-cccc FAILED REASON(rrrr) {FOR RESOURCE(tt:nnnnnnnn)}
DDN(dddddddd) DSP(SHR|MOD|OLD) DSN:ddd…44…ddd
Description: The CCCC = ALOQ/UNAQ/ALOR/UNAR command failed in Dynamic Allocation (SVC99) for the
indicated resource with the reason code RRRR. Reason codes can be found in the MVS Authorized Assembler Services
Guide. Refer to the Requesting DYNAMIC ALLOCATION Functions chapter. The most common values are:
Dec Hex
528 210 Requested dataset is unavailable or dataset is allocated to another job and its usage attribute conflicts with this request.
860 35C DSN does not start in column 19, spelling is incorrect, or is not found.
1040 410 Specified DDNAME unavailable (DDNAME already allocated)
1056 420 Specified DDNAME or DSN associated with an OPEN dataset.
1080 438 Specified DDNAME not found (check spelling) or DDNAME already unavailable.
1088 440 Specified DSN not found.
1096 448 DSN already exists.
5896 1708 DSN does not start in column 19, spelling is incorrect, or is not found.
MBCE133-cccc SUCCESSFUL {FOR RESOURCE(tt:nnnnnnnn)}

DDN(dddddddd) DSP(SHR|MOD|OLD) DSN:ddd…44…ddd
Description: The CCCC = ALOQ/UNAQ/ALOR/UNAR command completed successfully for the indicated resource.
ALOQ and UNAQ always use SVC 99. ALOR and UNAR use SVC99 if FILE IN JCL is specified for the Resource Item.
MBCE134-WRITEQ TD ERROR ON TD QUEUE xxxx
Description: An error occurred writing a message to TD QUEUE xxxx.
MBCE135-UNABLE TO SET ffffffff TO NOTRLS STATUS
Description: An error occurred in MBCPRSET trying to reset file FFFFFFFF to NOTRLS status. Most likely, the file was
busy in RLS mode with another task and could not be reset at this time. MBCPRSET processing continues.
MBCE136-FILE ffffffff IOERR ON cccc IN aaaaaaaa
Description: CICS returned an IOERR on command cccc for file ffffffff in Applid aaaaaaaa. Refer to CICS logs for
associated DFH message to assist in determining the cause of the error.
MBCE137-COMMAND cccccccccccccc WAS xxSUCCESSFUL RC(nn)
Description: This message is associated with the DBLC command to open or close Datacom/DB databases. If the
command was successful, return code is blanks. If unsuccessful, the Datacom/DB return code is indicated. Reference your
CA-Datacom/DB manuals for an explanation of the return code if the command was unsuccessful.
MBCE138-APPL STATUS RECORD WRITTEN IN SHUTDOWN PLT
Description: During CICS Shutdown, an APPL DOWN record was successfully written to the BATSTAT file. This is
normal when APPLSTS is set to ‘Y’ or ‘F’.
MBCE139-MBCX PURGE DETECTED (xxxx)
Description: The EXCI listener transaction MBCX has intercepted a purge ABEND XXXX where XXXX is AKCS or
AEXY. This usually indicates a time out condition and the current command may or may not have fully processed. Check
the CICS log for additional messages. Also review your DTIMOUT value for MBCX or your timeout value for any external
monitoring applications you are running and increase if necessary. If the command involves a file, check the file is not in
use, does not have catalog errors or is not involved in a “deadly embrace” condition.

MBCE140-pppppppp HAS ABENDED WITH ABCODE (xxxx)
Description: Program PPPPPPPP abended with ABEND codes XXXX. Listed below are some common ABEND codes
and a brief description of the likely cause for the ABEND.
AEIM – Not found error. Most often has occurred when BATCNTL access was defined as remote and the remote
connection is not available.
AEXY – Transaction was purged. Check for security errors, file contention, or active transaction MBCR (BATSTAT
processing has not completed due to an unexpected error).
AKCS – Most common cause is MBCR transaction is still running (program MBCPRSET) while processing BATSTAT
commands during CICS startup, which ultimately causes a timeout (DTIMOUT).
ASRA – Program check. Most common cause is EXECKEY=USER specified for a program requiring EXECKEY=CICS.
MBCN – Missing commarea from batch. Most common cause is using IBM profile DFHCICST for MBCPXCI instead of
DBDCICSA. DBDCICSA is required for MBCPXCI.
MBCR – The current CICS release is not supported by this release of MBC. Contact MacKinney Systems support to
determine if a patch is available.
Messages MBCE141 through MBCE149 are reserved for IMS DL/I interface messages

MBCE150- DFHEDAP RETURNED ERRORS FOR CEDA COMMAND IN TRANSLATION PHASE
Description: A CEDA command listed prior to the DFHEDAP message has failed, mostly likely due to a syntax error. See
messages the follow for additional information into the cause of the error and correct.
MBCE151- DFHEDAP RETURNED ERRORS FOR CEDA COMMAND IN EXECUTION PHASE
Description: A CEDA command listed prior to the DFHEDAP message has failed. See messages the follow for additional
information into the cause of the error and correct.
MBCE152- DFHEDAP MAX LINES RETURNED. SEE LOG FOR ADDITIONAL MESSAGES
Description: A CEDA command was processed and the resultant list has filled the maximum area supported by the
DFHEDAP interface. The resultant list may be incomplete. As a work around, use a filter to return a fewer number of
entries (i.e. CEDA IN GROUP(AGROUP) instead of GROUP(A*)
MBCE153-QRYx NET DOES NOT SUPPORT GENERIC NETNAME VALUE FOR VSE
Description: The QRYL/QRYS NET commands do not support generic Netname values for VSE. Enter a specific
Netname value or use the QRYL/QRYS TER command.
MBCE154-MBCSQRQ POINTER CORRUPTION: ITEM(xxxxx) NUMITEMS(yyyyy) HDR(hhhh)
Description: The CICS server program has received an Item Error reading the inquiry TSQ ‘MBCSQRQ’ as the result of a
CEMT INQ or QRYL/QRYS command. XXXX is the item number the program is attempting to read, YYYYY is number of
items in the TSQ and HHHH is the item header. Check the CICS log for any additional messages and retry. If the failure
repeats, please contact MacKinney Systems support.
MBCE155-TRANID xxxx LAUNCHED WITH THE FOLLOWING nnn BYTES OF INPUTMSG
Description: TRANID XXXX was successfully launched via a RETURN IMMEDIATE with NNN bytes of INPUTMSG
using special application launch transaction MBCS.
MBCE156-QUIESCE|UNQUIESCE SUCCESSFUL FOR dsn
Description: A SET DSNAME(dsn) QUIESCE or UNQUIESCE command has been successfully executed. SMSVSAM
will propagate the QUIESCE or UNQUIESCE to all appropriate regions.
MBCE157-QUIESCE|UNQUIESCE FAILED FOR dsn
Description: A SET DSNAME(dsn) QUIESCE or UNQUIESCE command was unsuccessfully executed for dsn. See the
CICS log and system log for any additional messages.
MBCE158-RLQY|RLUP SUCCESSFUL FOR ffffffff
Description: An RLQY or RLUP command was successfully executed for file ffffffff.
MBCE159-RLQY|RLUP FAILED FOR ffffffff
Description: An RLQY or RLUP command failed while executing file ffffffff.

Messages MBCE161 through MBCE169 are produced when using the DLOC command (VSE only). The message text
indicates the result of DLOC command processing. If an error occurs, check: (1) program MBCPDLOC was updated with
your databases (2) MBCPDLOC assembled without any errors (3) CICS PCT and PPT entries were made.
MBCE161-INVALID PSB SCHEDULE
Description: Self-explanatory.
MBCE162-DL/I REQUEST COMPLETED
MBCE163-DL/I DBD NAME DOES NOT MATCH TABLE
MBCE164-DL/I REQUEST MUST BE STRT OR STOP
MBCE165-SEVERE DL/I ERROR
MBCE166-DL/I FUNCTION HAS BEEN PREVIOUSLY PERFORMED
MBCE167-DL/I DBD NAME IS UNUSABLE
MBCE168-DL/I TESTCB FAILED
MBCE169-DL/I DOES NOT RECOGNIZE DBD NAME

Messages MBCE170 through MBCE179 are produced by Batch (MBCB prefix message) and/or online programs (MBCE
prefix messages) in support Domain Applid records and for the TCP/IP version of MBC.
MBCE170-IP CONNECTION COMPLETE TO APPL(aaaaaaaa) PORT(ppppp) XUSR(uuuuuuuu)

MBCE170- JOB(pppxxxxx:nnnnnnnn) FAMILY(INET) IP(xxx.xxx.xxx.xxx) {IPV4}
MBCE170- JOB(pppxxxxx:nnnnnnnn) IP(xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxx) {IPV6)
Description: A successful TCP/IP connect socket was completed to the CICS Applid aaaaaaaa on PORT pppppp with
execution USERID uuuuuuuu. In the CICS log a second line appears disaplaying the Job number pppxxxxx and name
nnnnnnnn. The job type ppp can be JOB/STC/PJB to identify z/OS JOB, z/OS Started Task or z/VSE Power, and xxxxx
represents the unique job number.The remainder of the second line displays the and Family (INET) and IP address
xxx.xxx.xxx xxx for IPV4 and xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx for IPV6. This is a normal message (MBCB170) when
MBCBATCH processing is preparing to begin for Applid aaaaaaaa or (MBCE170) after a successful take TAKESOCKET
from the CICS listener.
MBCB171-SOCKET ERROR: APPL(aaaaaaaa) RC(rrr) ERRNO(eeeee) ffffffffffffffff

MBCE171-SOCKET ERROR: APPL(aaaaaaaa) RC(rrr) ERRNO(eeeee) ffffffffffffffff
Description: A function was unsuccessful on the CICS Applid aaaaaaaa socket. See the RETCODE rrr and the ERRNO
eeeee vales for function ffffffffffffffff in the IP Sockets Application Programming Interface Guide and Reference. The
processing of commands is likely interrupted. Also check the MBCBATCH job log and the CICS log for additional
messages.
MBCB172- CLOSE SOCKET COMPLETE FOR APPL(aaaaaaaa)

MBCE172- CLOSE SOCKET COMPLETE FOR APPL(aaaaaaaa)
Description: A successful TCP/IP close socket was completed to the CICS Applid aaaaaaaa. This is a normal message
when MBCBATCH processing was completed for Applid aaaaaaaa.
MBCB173-INITAPI ERROR: ERRNO(eeeee)
Description: The INITAPI TCP/IP function was unsuccessful. See the ERRNO eeeee for the INITAPI function in the IP
Sockets Application Programming Interface Guide and Reference.
MBCB174-DOMAIN RECORD FOR APPL(aaaaaaaa) NOT FOUND, CICS ACCESS DENIED
Description: A CICS header caused MBC to read the Domain Record for Applid aaaaaaaa and a record could not be
found. A Domain Applid Record matching the CICS header value must be present if DOMSEC=Y or if running the IP
version of MBC. The return code for a security error (option ERRSEC) is set. Add a Domain Applid Record for the Applid
and retry the MBCBATCH job (Section 3.10).
MBCE175-CONNECTED FROM BATCH(pppxxxxx:nnnnnnnn) USER(bbbbbbbb) XUSR(uuuuuuuu)
Description: Message displays after successful connection from the batch job identified by Job number pppxxxxx and Job
name nnnnnnnn to MBC’s online command server. The job type ppp can be JOB/STC/PJB to identify z/OS JOB, z/OS
Started Task or z/VSE Power, and xxxxx represents the unique job number. The USER bbbbbbbb is the batch submitter and
XUSR uuuuuuuu is the Execution Userid.

Messages MBCE180 through MBCE185 are produced in support of Startup Commands.
MBCB180-STARTUP COMMAND PROCESSING BEGINNING
Description: Informational message issued by MBCPPLQ when beginning the process Startup Commands present in the
region BATCSTS file.
MBCB181-STARTUP COMMAND PROCESSING ENDED
Description: Informational message issued by MBCPPLQ when all of the Startup Commands present in the region
BATCSTS file have been processed.
MBCE182-NO COMMANDS FOUND FOR STARTUP COMMAND PROCESSING
Description: Informational message issued when there were no Startup Commands to process in the region BATCSTS file.
MBCE183-UNABLE TO OPEN BATCSTS FOR AAAAAAAA PLT STARTUP COMMAND PROCESSING
Description: Issued when the OPEN for BATCSTS failed during Startup Command processing in Applid aaaaaaaa.
Verify file BATCSTS is defined and available for Applid aaaaaaaa.
MBCE184-ERROR CREATING STARTUP COMMAND TSQ IN PPPPPPPP
Description: Issued when there was an error trying to create the Startup Command processor TSQ in program pppppppp.
MBCE185-COMMANDS STORED FOR STARTUP COMMAND PROCESSING
Description: Issued when the CSCQ header is present in the MBCBATCH job to indicate commands that follow will be
written (stored) in the target CICS BATCSTS file.

Messages MBCB200 through MBCB219 are produced by the MBCBATCH pre-processor and other batch utility programs.
MBCB200-xxxxxxx VSAM OPEN ERROR: RC(ccc) REASON(rrr)
Description: The BATCNTL or BATSTAT file failed to open due to the indicated error return code (R15) CCC and reason
code RRR. Consult the VSE/VSAM Messages and Codes or VSAM Programmers Guide (z/OS) for an explanation.
MBCB201-xxxxxxx ACCESS ERROR: RC(ccc) REASON(rrr)
Description: A logic error occurred while accessing the BATCNTL or BATSTAT file with a VSAM request macro GET or
PUT. The return code (R15) CCC and reason code RRR indicates why the error occurred. Consult the VSE/VSAM
Messages and Codes or VSAM Programmers Guide (z/OS) for an explanation.
MBCB204-INVALID UTILITY FUNCTION
Description: An input card for MBCBSUTL or MBCBCPRT has specified an invalid function. Function must be PRT or
DEL for MBCBSUTL, or XREF for MBCBCPRT.
MBCB205-APPLID MISSING ON INPUT CARD
Description: An input card for MBCBCPRT or MBCBSUTL was specified and a required Applid value is missing.
MBCB206-RESOURCE TYPE AND RESOURCE NAME INVALID OR MISSING ON INPUT CARD
Description: An input card for MBCBCPRT or MBCBSUTL was specified and a resource type and resource name is
required.
MBCB207-AGE VALUE MUST BE NUMERIC 001-365
Description: An input card for MBCBSUTL has specified an invalid AGE value. Value must be 001-365.
MBCB208-INCORRECT VALUE SPECIFIED FOR INIT PARM, MUST BE ENQXS OR DOMSEC
Description: An input card for MBCBCUTL has specified a value for INIT card other than ‘ENQXS’ or ‘DOMSEC’.
Correct the card to one of those two values and retry.
MBCB209-VALUE MUST BE Y OR N
Description: An input card for MBCBCUTL has specified a value other than ‘Y’ or ‘N’. Correct the card to one of those
two values and retry.
MBCB210-INSUFFICIENT MEMORY, UNABLE TO INITIALIZE
Description: There is not enough storage to initialize MBCBATCH. Increase the REGION parameter on the EXEC card in
the MBCBATCH JCL.
MBCB211-UNABLE TO LOAD PGM pppppppp
Description: During the initialization phase of MBCBATCH, the loader was unable to load program PPPPPPPP. Verify
program PPPPPPPP is linked into the MBC load library.
MBCB212-128 BYTE BUFFER NOT AVAILABLE, MBCBATCH ABORTED
Description: The most common cause of this error is when preceded by a MBCB211 error. See the description for the
error. If this message occurs otherwise, contact your vendor.
MBCB213-XXX BUFFER EXPANSION FAILED
Description: The number of commands processed in this step has exhausted storage for the buffer pool indicated in the
message. An attempt to expand the storage has failed. For immediate action, reduce the commands processed in this step if
possible and increase the region size on the MBCBATCH step. If errors continue, notify your vendor.
MBCB214-xxx BUFFER EXPANSION SUCCESSFUL
Description: This informational message indicates the number of commands processed in this step has exhausted storage
for the buffer pool indicated in the message. A buffer expansion was successful. This message can be safely ignored unless
an excessively large number of the messages appear. For immediate action, reduce the commands processed in this step if
possible and increase the region size on the MBCBATCH step. If messages continue, notify your vendor.
MBCB218-MODULE xxxxxxxx INCORRECT RELEASE LEVEL
Description: An attempt was made to load module XXXXXXXX and the loader determined an incorrect release level of the
module was found. Verify the correct version of the object module XXXXXXXX is present in the MBC library.
MBCB219-MODULE xxxxxxxx CORRUPTED
Description: An attempt was made to load module XXXXXXXX and the loader determined the module is corrupt. Verify the
correct version of the object module XXXXXXXX is present in the MBC library.

Messages MBCE300 through MBCE399 are produced by online administration programs
MBCE301-PROGRAM xxxxxxxx NOT IN TABLES
Description: Program XXXXXXXX was not found in the RDO tables (PPT). Add the program definition to your tables and
retry.
MBCE302-PROGRAM xxxxxxxx DISABLED
Description: Program XXXXXXXX returned a status of DISABLED. Other installation options are not updated until the
situation is corrected. Use CEMT online to ENABLE the specified program and retry.
MBCE303-SPECIFY DESIRED OPTION
Description: ENTER or PF key was pressed without a selected option. Refer to instructions on current screen for available
options.
MBCE304-STATUS TRACKING NOT ACTIVE, OPTION IGNORED
Description: Administrative option requiring active Status Tracking was selected and Status Tracking (STATFLAG=N) is
not active. You can retry after activating Status Tracking, but please review Status Tracking before changing STATFLAG.
MBCE305-SPECIFY LANGUAGE=ASSEMBLER FOR PROGRAM xxxxxxxx
Description: Program XXXXXXXX must be defined as ASSEMBLER. Specify the LANGUAGE parameter for program
XXXXXXXX and retry.
MBCE306-SECURITY ERROR ACCESSING BATCNTL FILE
Description: A security violation was raised by CICS in accessing the BATCNTL file. Review your CICS security to see
if this error is valid.
MBCE307-TRANSID tttt SHOULD POINT TO PROGRAM xxxxxxxx
Description: TRANSID TTTT is pointing to an incorrect program and should be changed to point to PROGRAM
XXXXXXXX. Re-specify the PROGRAM parameter for TRANSID TTTT and retry.
MBCE308-TRANSID tttt NOT IN TABLES (PCT)
Description: TRANSID TTTT could not be located in the current CICS tables. Install the specified TRANSID in the
current CICS tables and retry.
MBCE309-ERROR ACCESSING BATCNTL, FILE IS xxxxxxxxx
Description: A file access to BATCNTL was unsuccessful with status XXXXXXXX. XXXXXXXX is NOT OPEN,
DISABLED, UNDEFINED or IN USE. If flagged as IN USE, then the BATCNTL dataset could not be opened for update
(Add/Update/Delete). This most likely indicates the dataset is open for update in another CICS region. Further use of
MacKinney Batch to CICS is not possible until this situation is corrected. Take the appropriate action to correct and retry.

MBCE310-INVALID TABLE DEFINITION FOR BATCNTL
Description: The CICS file definition for BATCNTL does not match the expected definition parameters. Refer to the RDO
File entry for BATCNTL and correct.
MBCE311-I/O ERROR HAS OCCURRED WITH BATCNTL FILE
Description: An I/O error was detected during access to BATCNTL file. Verify the BATCNTL file definition is correct
and check for possible hardware errors.
MBCE312-UPDATE SUCCESSFULLY COMPLETED
MBCE313-VALUE IS INVALID, MUST BE NUMERIC
Description: Non-numeric input was specified for a field requiring numeric input.
MBCE314-VALUE IS INVALID, MUST BE Y OR N
Description: A value other than Y or N was specified for a field requiring Y or N.
MBCE315-VALUE IS INVALID, MUST BE GREATER THAN ZERO
Description: A value of zero was entered in a field which requires a value greater than zero.
MBCE316-VALUE MUST BE W-WTOR|C-CANCEL|F-FLUSH|B-BYPASS
Description: A value other than W, C, F or B was specified for a field requiring one of those values.
MBCE317-STATFLAG MUST BE Y-ACTIVE OR N-INACTIVE
Description: The acceptable values for field STATFLAG are: N-Status tracking feature is inoperative, or Y-Save selected
commands only on the BATSTAT file
MBCE318-VALUE IS INVALID, XXXXXXXXXXXXXXXXXXXXXX
Description: A parm value is invalid. Correct the indicated parm value and retry.
MBCE319-APPLID xxxxxxxx NOT DEFINED ON BATCNTL FILE
Description: Applid XXXXXXXX was not found on the BATCNTL file.
MBCE320-APPLID xxxxxxxx IS DUPLICATED ON BATCNTL FILE
Description: CICS Applid XXXXXXXX is defined more than one time on the BATCNTL file. Remove Applids from the
BATCNTL file as necessary to prevent duplication. If updating Applid Table, unused entries should be changed to
‘*UNUSED*’.

MBCE321-PASSWORD NUMBER n=xxxxxxxxxxxxxxxx
Description: This message lists each of the six 16-character passwords.
MBCE322-WARNING, MACKINNEY BATCH TO CICS PASSWORD FOR CPU xxxxx EXPIRES mm/dd/yy
Description: The MacKinney Batch to CICS password(s) expire on the indicated date. This message appear when the
expiration date is within 2 weeks of the current date. Call the vendor for new passwords. If message DFHFC0987 is
present, it indicates the BATCNTL is open for update in another region. This is normal if MBC Administration is currently
active in another region. Otherwise, assure the BATCNTL RDO definition specifies read-only in all regions.
MBCE323-YOUR MACKINNEY BATCH TO CICS PASSWORD HAS EXPIRED
Description: All MacKinney Batch to CICS system passwords have reached their expiration dates. The product cannot be
used until at least one new password is loaded on the system. Update MacKinney Batch to CICS passwords on the system in
one of two ways: (1) Use option '0' (Password Maintenance) of the online Administrative Menu screen, or
(2) Use the PASS command as input to MBCBCUTL.
MBCE324-YOUR MACKINNEY BATCH TO CICS PASSWORD FOR CPU xxxxx IS INVALID
Description: The system password is invalid. Check it against the password(s) supplied by the vendor. Update MacKinney
Batch to CICS passwords on the system in one of two ways: (1) Use option ‘0’ (Password Maintenance) of the online
Administrative Menu screen, or (2) Use the PASS command as input to MBCBCUTL.
MBCE325-VALUE MUST BE xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Description: This message displays for common screen editing errors. The value for XXXXXXXXXXXXXXXXXXXX
describes the error and is for example “non-blank”. The values are self-descriptive. The cursor is positioned on the field in
error. Correct the field according to the description of XXXXXXXXXXXXXXXXXXXX and retry.
MBCE326-MACKINNEY BATCH TO CICS INSTALLATION OPTIONS UPDATED
Description: The installation options were updated on the BATCNTL file.
MBCE327-MBC APPLID TABLE UPDATED IN THE BATCNTL FILE
MBCE328-TRANSACTION MBCQ CANNOT BE INVOKED BY TERMINAL INPUT
MBCE329-COMMAND COMPLETED SUCCESSFULLY
MBCE330-MBC INSTALLATION OPTIONS RECORD UNAVAILABLE
Description: The record containing the installation options and passwords is not available. Update your installation options
and password(s) and retry.

MBCE331-APPLTBL APPLIDS POPULATED TO DOMAIN RECORDS
Description: The ApplTbl Applids were populated to the Domain Applid records. New records can be edited using
Administration Menu option 7 (Section 3.10)
MBCE332-APPLTBL APPLIDS ALREADY POPULATED IN DOMAIN RECORDS
Description: ApplTbl Applids have either previously been populated to the Domain Applid records or were manually
added. Records can be edited using Administration Menu option 7 (Section 3.10)
MBCE336-COMMAND FAILED – SEE CICS LOG
Description: A command from MBCBATCH has executed with an error. See the CICS log for possible additional
messages indicating the reason for the failure.
MBCE337-COMMAND PROCESS WITH MIXED RESULTS – SEE CICS LOG
Description: A command from MBCBATCH has executed with mixed results. This message can occur on commands to
operate on generic resources. See the CICS log for possible additional messages indicating the reason for the failure.
MBCE338-MAX ITEMS REACHED, DESELECT OLD ITEM(S) BEFORE ADDING NEW
Description: A Resource Group can have a maximum of 999 items. You currently have 999 items selected and are trying
to select more. You must deselect item(s) not needed before adding or add a new Resource Group.
MBCE340 – NO FURTHER FORWARD SCROLLING POSSIBLE
Description: A page forward was requested but the current display is already at the end of the data.
MBCE341 – NO FURTHER BACKWARD SCROLLING POSSIBLE
Description: A page backward was requested but the current display is already at the beginning of the data.
MBCE344-NO ITEMS PROCESSED FOR GROUP(gggggggggggg) APPL(aaaaaaaa)
Description: A group command (i.e. ALOG, CLOG, OPEG, etc.) was executed but no items were processed. This could
happen for example, if a group contained only TRANID items and OPEG was issued against the group.
MBCE345 – SPECIFY A VALID PF KEY
Description: A PF/PA Key you entered is not a valid key on this screen.
MBCE346 – NO GROUPS/ITEMS MEET CRITERIA
Description: A request was made to begin the display with a specific resource name and no records greater than or equal to
this name were found. This message can appear on several of the Group screens.
MBCE347 – NO ITEMS DEFINED
Description: A request was made to display Resource Items and no item records were found for the specified group. Define
Resource Items for the specified group and retry or select a different group with items.
MBCE348 – NO GROUPS DEFINED
Description: A request was made to display groups and no group records were found. This message can appear on several
of the Group screens. Groups can be added by authorized users from the Group Directory Screen (MBCG), ApplGrp
Directory Screen (MBCL) or the Administration Menu.
MBCE349 – xxxxxxxx REMOTE CONNECTION NOT AVAILABLE
Description: A request requiring action on remote CICS (Applid XXXXXXXX) was made and the connection to this CICS
is either currently not available or not defined. Use CEMT INQ CONN to check the status of your current connections. See
the CICS Intercommunication Guide for help in defining connections between your CICS regions.
MBCE350 – xxxx FOR GROUP(gggggggggggg) BEGINNING
Description: This message indicates MBC is beginning to process an ALOG (allocate group), ALSG (allocate secondary
DSN2 group) or UNAG (unallocated group) request was made for group GGGGGGGGGGGG.
MBCE351 – xxxx FOR GROUP(gggggggggggg) SUCCESSFUL
Description: An ALOG (allocate group), ALSG (allocate secondary DSN2 group) or UNAG (unallocated group) request
was made for group GGGGGGGGGGGG and the result was successful.
MBCE352 – xxxx FOR GROUP(gggggggggggg) HAD ERRORS - SEE CICS LOG
Description: An ALOG (allocate group), ALSG (allocate secondary DSN2 group) or UNAG (unallocated group) request
was made for group GGGGGGGGGGGG and the result had errors. See the CICS message log for further messages to give
additional information about the problem.
MBCE353 – APPLGRP(gggggggggggg) NOT FOUND
Description: A request to lookup ApplGrp GGGGGGGGGGGG was unsuccessful. The group was not found. Verify the
group is defined on the ApplGrp Directory Screen.
MBCE354 – APPLGRP (gggggggggggg) ALREADY ON FILE, PLEASE REENTER
Description: ApplGrp GGGGGGGGGGGG already exists on file. Choose a new name for the group and try again.
MBCE355 – APPLGRP(gggggggggggg) fffffff BY USER uuuuuuu
Description: ApplGrp GGGGGGGGGGGG was added/deleted by user UUUUUUUU.
MBCE356 –GROUP(gggggggggggg) APPL(aaaaaaaa) NOT FOUND
Description: A request for Resource Group GGGGGGGGGGGG for Applid AAAAAAAA is unsuccessful. The group was
not found.
MBCE357 – GROUP(gggggggggggg) APPL(aaaaaaaa) ALREADY ON FILE, PLEASE REENTER
Description: This Resource Group GGGGGGGGGGGG already exists on file for Applid AAAAAAAA. Choose a new
name for the group or a new Applid and try again.

MBCE358 – GROUP(gggggggggggg) APPL(aaaaaaaa) fffffff BY USER uuuuuuu
Description: Resource Group GGGGGGGGGGGG was added/deleted by user UUUUUUUU.
MBCE359 – ENTER APPLID, NAME AND DESC THEN PRESS PF6 TO ADD ITEMS
Description: This message appears on the Group Maintenance screen when the user has pressed PF6 on the Group
Directory screen to add a new group. Enter the CICS Applid, a group name and a group description. The group name can be
up to 12-characters and identifies the group. The description can be up to 30-characters and helps further identify the
group.
MBCE360 – DOMAIN APPLID(aaaaaaaa) ALREADY ON FILE
Description: Domain Applid AAAAAAAA already exists on file. Choose a new Applid and try again.
MBCE361 – DOMAIN APPLID(aaaaaaaa) ffffffff BY USER uuuuuuu
Description: Domain Applid AAAAAAAA was added/deleted by user UUUUUUUU.
MBCE362 – NO DOMAIN APPLIDS DEFINED
Description: A request was made to display Domain Applids and no Domain records were found. Domain Applids can be
added by authorized users from the Domain Directory Screen (MBCD) or the Administration Menu.
MBCE363 – NO DOMAIN APPLIDS MEET CRITERIA
Description: A request was made to begin the display with a specific Applid value and no records greater than or equal to
this name were found.
MBCE364 – STATUS NOT SUPPORTED FOR RESOURCE TYPE xx
Description: A status request for the resource Type indicated by XX is not supported.
MBCE365 – STATUS NOT ALLOWED FOR APPLGRP
Description: The status function cannot be used for a Resource Group with the Applid value being an APPLGRP.
MBCE366–xxxxxx REQUESTED. PRESS PF5 TO CONFIRM xxxxxx OR PF12 TO CANCEL
Description: A delete or reset of the selected Resource Group, Resource Item or Domain Applid was requested. Verify the
entry being deleted or reset. To proceed with the delete or reset on the indicated entry, press PF5. To cancel the delete or
reset request, press PF12.
MBCE367 – "xxxxxx REQUEST" CANCELLED. PRESS ENTER TO CONTINUE
Description: The user canceled a delete or reset request by pressing the PF12 key.

MBCE370 – RESOURCE(tt:nnnnnnnn) APPL(aaaaaaaa) NOT FOUND
Description: A request to lookup resource TT (type) NNNNNNNN (name) for Applid AAAAAAAA is unsuccessful. The
Resource Item was not found.
MBCE371 – RESOURCE(tt:nnnnnnnn) APPL(aaaaaaaa) ALREADY ON FILE
Description: Adding this resource would create a duplicate record. Change the resource to a new name, type or both.
MBCE372 – RESOURCE(tt:nnnnnnnn) APPL(aaaaaaaa) fffffff BY USER uuuuuuu
Description: Resource TT NNNNNNNN for Applid AAAAAAAA was added/deleted/updated by user UUUUUUUU. TT is
the resource type (FI/PG/TR/TD/TX/IP) and NNNNNNNN is the resource name (file name, program name, etc.).
MBCE373 – STATUS(tt:nnnnnnnn) APPL(aaaaaaaa) fffffff BY USER uuuuuuu
Description: Resource Status TT NNNNNNNN for Applid AAAAAAAA was deleted/reset by user UUUUUUUU. TT is the
resource type (FI/PG/TR/TD/TX/IP) and NNNNNNNN is the resource name (file name, program name, etc.).
MBCE374 – RESOURCE(tt:nnnnnnnn) NOT ASSIGNED TO ANY GROUP
Description: The Resource Item is not currently assigned to any Resource Group.
MBCE375 – RESOURCE(tt:nnnnnnnn) REMOVED FROM GROUP(gggggggggggg) APPL(aaaaaaaa)
Description: Resource TT NNNNNNNN was removed from the listed Resource Group in the listed Applid. TT is the
resource type (FI/PG/TR/TD/TX/IP) and NNNNNNNN is the resource name (file name, program name, etc.).
MBCE376 – RESOURCE TYPE TX NOT SUPPORTED FOR VSE
Description: TX resources require the use of SVC 99 which is not supported in VSE, so TX Resource Items are disallowed
in VSE.
MBCE377 – xxxx FOR FLIST(llllllll) BEGINNING
Description: This message indicates MBC is beginning to process an ALOC, ALOQ, UNAL or UNAQ request was made
for flist LLLLLLLL.
MBCE378 – xxxx FOR FLIST(llllllll) SUCCESSFUL
Description: An ALOC, ALOQ, UNAL or UNAQ request was made for flist LLLLLLLL and the result was successful.
MBCE379 – xxxx FOR FLIST(llllllll) HAD ERRORS - SEE CICS LOG
Description: An ALOC, ALOQ, UNAL or UNAQ request was made for flist LLLLLLLL and the result had errors. See the
CICS message log for further messages to give additional information about the problem.
MBCE380–TR:nnnn SET ena
Description: A request to enable or disable transaction XXXX was successful. YYY is ENA for enable or DIS for disable.

MBCE381–yyy FAILED FOR TR:xxxx
Description: A request to enable or disable transaction XXXX failed. YYY is ENA for enable or DIS for disable. See the
CICS message log for further messages to give additional information about the problem.
MBCE382–FI:nnnnnnnn ope ena {uad DS:dsn} | {FOR DESIRED STATE: UNALLOCATED}
Description: A request to allocate or unallocate file NNNNNNNN was successful. Open (OPE/CLO) and enable
(ENA/DIS) status are always displayed. Update (U upd | ’-‘ no upd), add (A add | ’-‘ no add) and delete (D-del | ’-‘ no del)
status are represented as well as the DSN for allocate.
MBCE383–yyy FAILED FOR FI:xxxxxxxx
Description: A request to allocate or unallocate file XXXXXXXX failed. YYY is ALO for allocate or UNA for unallocate.
See the CICS message log for further messages to give additional information about the problem.
MBCE384–TX:nnnn ope ena FOR {DS:dsn} | {DESIRED STATE: UNALLOCATED}
Description: A request to allocate or unallocate an extra-partition TDQ XXXX was successful. Open (OPE/CLO) and
enable (ENA/DIS) status are always displayed. The DSN value is displayed for allocate.
MBCE385–yyy FAILED FOR TX:xxxx
Description: A request to allocate or unallocate extra-partition TDQ XXXX failed. YYY is ALO for allocate or UNA for
unallocate. See the CICS message log for further messages to give additional information about the problem.
MBCE386–TD:nnnn SET ena
Description: A request to enable or disable TDQ XXXX was successful. YYY is ENA for enable or DIS for disable.
MBCE387–yyy FAILED FOR TD:xxxx
Description: A request to enable or disable TDQ XXXX failed. YYY is ENA for enable or DIS for disable. See the CICS
message log for further messages to give additional information about the problem.
MBCE388-CANNOT DISABLE TD:xxxx-BEGINS WITH C
Description: A request to disable TDQ XXXX failed because the TDQ name begins with the letter ‘C’. This is a CICS
restriction.
MBCE390–PG:nnnnnnnn SET ena
Description: A request to enable or disable program NNNNNNNN was successful. YYY is ENA for enable or DIS for
disable.
MBCE391–yyy FAILED FOR PG: nnnnnnnn
Description: A request to enable or disable program NNNNNNNN failed. YYY is ENA for enable or DIS for disable. See
the CICS message log for further messages to give additional information about the problem.

MBCE392–IP:nnnnnnnn SET ope
Description: A request to open or close TCPIP service NNNNNNNN was successful. YYY is OPE for open or CLO for
close.
MBCE393–yyy FAILED FOR IP:nnnnnnnn
Description: A request to open or close TCPIP service NNNNNNNN failed. YYY is OPE for opend or CLO for close. See
the CICS message log for further messages to give additional information about the problem.
9.2 ABEND Codes from Online Programs
Abend Code Cause
MBCE An error occurred on the link to DFHEMTA.

MBCG A general error occurred while running MBCPMSG
MBCM Missing input data on START of program MBCPMSG
MBCN Commarea missing or invalid on EXCI link (z/OS) or TCP/IP link (VSE).
MBCR Unsupported CICS release

APPENDIX A - EIBFN
EIBFN contains a code identifying the last CICS command issued by the task (updated when the requested function
completes). Listed below are some common EIBFN values.
Code Command Code Command
0202 ADDRESS 1806 SEND TEXT

0204 HANDLE CONDITION 1812 SEND CONTROL
0206 HANDLE AID
0208 ASSIGN 1A02 TRACE
020A IGNORE CONDITION 1A04 ENTER
020C PUSH
020E POP 1C02 DUMP
0402 RECEIVE 2002 BIF DEEDIT

0404 SEND 2202 ENABLE
0406 CONVERSE 2004 DISABLE
0414 ISSUE DISCONNECT 2006 EXTRACT EXIT
0420 ALLOCATE
0422 FREE 4A02 ASKTIME ABSTIME
0430 ISSUE ABEND 4A04 FORMATTIME
043A ISSUE PASS 4C02 INQUIRE DATASET
043C EXTRACT LOGONMSG 4C04 SET DATASET
4E02 INQUIRE PROGRAM
0602 READ 4E04 SET DATASET
0604 WRITE
0606 REWRITE 5002 INQUIRE TRANSACTION
0608 DELETE 5004 SET TRANSACTION
060A UNLOCK 5202 INQUIRE TERMINAL
060C STARTBR 5204 SET TERMINAL
060E READNEXT 5206 INQUIRE NETNAME
0610 READPREV 5212 INQ TERMINAL ALT
0612 ENDBR 5216 INQ NETNAME ALT
0614 RESETBR 5402 INQUIRE SYSTEM
5404 SET SYSTEM
0802 WRITEQ TD 5602 SPOOLOPEN
0804 READQ TD 5604 SPOOLREAD
0806 DELETEQ TD 5608 SPOOLWRITE
5610 SPOOLCLOSE
0A02 WRITEQ TS 5802 INQUIRE CONNECTION
0A04 READQ TS 5804 SET CONNECTION
0A06 DELETEQ TS 5C02 INQUIRE TDQUEUE
5C04 SET TDQUEUE
0C02 GETMAIN 5E02 INQUIRE TASK
0C04 FREEMAIN
6C02 WRITE OPERATOR
0E02 LINK
0E04 XCTL 7802 INQ DSNAME
0E06 LOAD 7804 SET DSNAME
0E08 RETURN
0E0A RELEASE 8002 INQUIRE TSQUEUE
0E0C ABEND 8012 INQ TSQUEUE ALT
0E0E HANDLE ABEND
1002 ASKTIME
1004 DELAY
1006 POST
1008 START
100A RETRIEVE
100C CANCEL
1202 WAIT EVENT

1204 ENQ
1206 DEQ
1208 SUSPEND
1602 SYNCPOINT
1802 RECEIVE MAP

1804 SEND MAP
188 Appendix A - EIBFN

APPENDIX B - EIBRCODE
EIBRCODE contains the CICS response code returned after the function requested by the last CICS command the task
issued was completed.
The following list contains the values of the various bytes together with the names of the conditions associated with the
return codes. For a complete list of response codes, refer to IBM's Problem Determination Guide.
EIBFN EIBRCODE condition EIBFN EIBRCODE condition
02 .. EO .. .. .. .. .. INVREQ 0E .. 01 .. .. .. .. .. PGMIDERR
0E .. D6 .. .. .. .. .. NOTAUTH
04 .. 04 .. .. .. .. .. EOF 0E .. E0 .. .. .. .. .. INVREQ
04 .. 10 .. .. .. .. .. EODS
04 .. C1 .. .. .. .. .. EOF 10 .. 01 .. .. .. .. .. ENDDATA
04 .. C2 .. .. .. .. .. ENDINPT 10 .. 04 .. .. .. .. .. IOERR
04 .. D0 .. .. .. .. .. SYSIDERR 10 .. 11 .. .. .. .. .. TRANSIDERR
04 .. D2 .. .. .. .. .. SESSIONERR 10 .. 12 .. .. .. .. .. TERMIDERR
04 .. D3 .. .. .. .. .. SYSBUSY 10 .. 14 .. .. .. .. .. INVTSREQ
04 .. D4 .. .. .. .. .. SESSBUSY 10 .. 20 .. .. .. .. .. EXPIRED
04 .. D5 .. .. .. .. .. NOTALLOC 10 .. 81 .. .. .. .. .. NOTFND
04 .. E0 .. .. .. .. .. INVREQ 10 .. D0 .. .. .. .. .. SYSIDERR
04 .. E1 .. .. .. .. .. LENGERR 10 .. D1 .. .. .. .. .. ISCINVREQ
04 .. E3 .. .. .. .. .. WRBRK 10 .. D6 .. .. .. .. .. NOTAUTH
04 .. E4 .. .. .. .. .. RDATT 10 .. E1 .. .. .. .. .. LENGERR
04 .. E5 .. .. .. .. .. SIGNAL 10 .. E9 .. .. .. .. .. ENVDEFERR
04 .. E6 .. .. .. .. .. TERMIDERR 10 .. FF .. .. .. .. .. INVREQ
04 .. E7 .. .. .. .. .. NOPASSBKRD
04 .. E8 .. .. .. .. .. NOPASSBKWR 12 .. 32 .. .. .. .. .. ENQBUSY
04 .. EA .. .. .. .. .. IGREQCD 12 .. E0 .. .. .. .. .. INVREQ
04 .. EB .. .. .. .. .. CBIDERR 12 .. E1 .. .. .. .. .. LENGERR
04 .. F1 .. .. .. .. .. TERMERR
04 .. .. 20 .. .. .. .. EOC 16 .. 01 .. .. .. .. .. ROLLEDBACK
04 .. .. 40 .. .. .. .. INBFMH
04 .. .. .. .. F6 .. .. NOSTART 18 .. 01 .. .. .. .. .. INVREQ
04 .. .. .. .. F7 .. .. NONVAL 18 .. 02 .. .. .. .. .. RETPAGE
18 .. 04 .. .. .. .. .. MAPFAIL
06 .. 01 .. .. .. .. .. FILENOTFOUND 18 .. 08 .. .. .. .. .. INVMPSZ
06 .. 02 .. .. .. .. .. ILLOGIC 18 .. 20 .. .. .. .. .. INVERRTERM
06 .. 08 .. .. .. .. .. INVREQ 18 .. 40 .. .. .. .. .. RTESOME
06 .. 0C .. .. .. .. .. NOTOPEN 18 .. 80 .. .. .. .. .. RTEFAIL
06 .. 0D .. .. .. .. .. DISABLED 18 .. E1 .. .. .. .. .. LENGERR
06 .. 0F .. .. .. .. .. ENDFILE 18 .. E3 .. .. .. .. .. WRBRK
06 .. 80 .. .. .. .. .. IOERR 18 .. E4 .. .. .. .. .. RDATT
06 .. 81 .. .. .. .. .. NOTFND 18 .. .. 02 .. .. .. .. PARTNFAIL
06 .. 82 .. .. .. .. .. DUPREC 18 .. .. 04 .. .. .. .. INVPARTN
06 .. 83 .. .. .. .. .. NOSPACE 18 .. .. 08 .. .. .. .. INVPARTNSET
06 .. 84 .. .. .. .. .. DUPKEY 18 .. .. 10 .. .. .. .. INVLDC
06 .. D0 .. .. .. .. .. SYSIDERR 18 .. .. 20 .. .. .. .. UNEXPIN
06 .. D1 .. .. .. .. .. ISCINVREQ 18 .. .. 40 .. .. .. .. IGREQCD
06 .. D6 .. .. .. .. .. NOTAUTH 18 .. .. 80 .. .. .. .. TSIOERR
06 .. E1 .. .. .. .. .. LENGERR 18 .. .. .. 01 .. .. .. OVERFLOW
18 .. .. .. 04 .. .. .. EODS
0A .. 01 .. .. .. .. .. ITEMERR 18 .. .. .. 08 .. .. .. EOC
0A .. 02 .. .. .. .. .. QIDERR 18 .. .. .. 10 .. .. .. IGREQID
0A .. 04 .. .. .. .. .. IOERR
0A .. 08 .. .. .. .. .. NOSPACE 22 .. 80 .. .. .. .. .. INVEXITREQ
0A .. 20 .. .. .. .. .. INVREQ
0A .. D0 .. .. .. .. .. SYSIDERR 4A .. .. .. .. 01 .. .. ERROR
0A .. D1 .. .. .. .. .. ISCINVREQ
0A .. D6 .. .. .. .. .. NOTAUTH
0A .. E1 .. .. .. .. .. LENGERR
0C .. E1 .. .. .. .. .. LENGERR
0C .. E2 .. .. .. .. .. NOSTG
Appendix B - EIBRCODE 189

APPENDIX C – Running IP Trace
For debugging TCP/IP issues, an IP Trace is often needed to help in determining the cause of the problem. MBC provides
its own high-level internal tracing option via the IPTR command described below. If running the internal IPTR trace does
not result in enough information to resolve the issue, you may need to run a trace provided by your TCP/IP vendor (IBM,
CSI, or BSI). Contact your TCP/IP vendor for information on running those traces.
The IPTR command is used to set the internal TCP/IP trace ON or OFF. This adds additional MBCTRC messages to
the normal batch and CICS logs to assist in debugging TCP/IP issues. The Command format follows:
IPTR
IPTR ON | OFF
ON – turn the trace on and create MBCTRC entries as shown below. Specify before the first CICS header.
OFF – turn the trace off
IP Trace Messages
The MBC internal IP Trace (IPTR command) produces several different format trace messages:
MBCTRC-PG: pppppppp APL: aaaaaaaa RTO:ttt PT:ppppp US:uuuuuuuu CD:xxxxxxxxsdt
Description: This MBCTRC message displays information for the IP initial connection to the CICS server. The following
values are provided: PPPPPPPP – program issuing IP command; AAAAAAAA – server region Applid; TTT – Domain
record read timeout value; PPPPP– IP Port; UUUUUUUU– Batch Userid: XXXXXXXX – Execution Userid from Domain
Record or Batch Userid if Domain User is blank; S – EXTSEC installation option value (Y/N); D – force Execution Userid
from Domain Record (Y/N); T – Trace active (Y/N)
MBCTRC-PG:pppppppp APL:aaaaaaaa R15:nnn ER:eeeee [LN:lllll | FM:INET(6)] ffffffffffff
Description: This MBCTRC message displays information for IP command FFFFFFFFFFFF. The following values are
provided: PPPPPPPP – program issuing IP command; AAAAAAAA – region Applid where command was issued; NNN –
register 15 value; EEEEE – command ERRNO value; LLLL – command Length value For SOCKET IP command; Family
INET (IPV4) or INET6 (IPV6) is provided rather than Length.
MBCTRC-PORT(ppppp) IP(xxx.xxx.xxx.xxx) | (nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn)
Description: For CONNECT IP command, this additional line identifies the IP port PPPPP and the IPV4 address
XXX…XXX or IPV6 address NNN…NNN.
MBCTRC-PG: pppppppp APL: aaaaaaaa ECB:xxxxxxxx cc TIM:tttt WTE: ffffffffffff
Description: The MBCTRC message displays ECB Wait Time information for IP command FFFFFFFFFFFF. The
following values are providedd: PPPPPPPP – program issuing IP command; AAAAAAAA – region Applid where
command was issued; XXXXXXXX – Timer ECB address; CC – Timer ECB post value; TTTT – Wait time (Hex).
190 Appendix C – Running IP Trace

Below is a sample CICS log of a TCP/IP session with Trace active including comments enclosed within braces {}.
{CICS Message indicating Listener is ready}

EZY1258I 05/22/20 11:36:28 EZACIC01 ENTRY POINT IS 19D3CAD0
EZY1261I 05/22/20 11:36:28 EZACIC03 ATTACH SUCCESSFUL, TCB ADDRESS=007A3E88 TRAN=CSKL TASK=0000345
EZY1291I 05/22/20 11:36:28 LISTENER TRANSACTION= CSKL ACCEPTING REQUESTS VIA PORT 3100
{other log messages can appear between these messages}
...
{CICS Message indicating Listener has picked up Connect Socket from batch and has started MBCZ}
EZY1325I 05/22/20 11:39.32 START SUCCESSFUL TRANID= MBCZ PARTNER INET ADDR=27.0.0.1 PORT=1295
MBCTRC-PG:MBCPTCI APL:T540 RTO:030 PT:01295 US:T540 CD:RJS1 NNY
MBCTRC-PG:MBCPTCI APL:T540 R15:002 ERR:00000 LEN:0000 TAKESOCKET
{Message written by MBC server program MBCPTCI indicating Connection is complete and USERID who submitted job}
MBCE170-IP CONNECTION COMPLETE TO APPL(T540) PORT(01295) XUSR(RJS1 ) 05/22/20 11:39:43 MBCPTCI x.x RJS1
MBCE170-JOB(JOB00020:MBC$RUN) FAMILY(INET) IP(127.000.000.001) 05/22/20 11:39:43 MBCPTCI x.x RJS1
MBCTRC-PG:MBCPTCI APL:T540 R15:001 ERR:00000 LEN:0080 SELECT WRITE 05/22/20 11:39:43 MBCPTCI x.x RJS1
MBCTRC-PG:MBCPTCI APL:T540 R15:080 ERR:00000 LEN:0080 WRITE 05/22/20 11:39:43 MBCPTCI x.x RJS1
MBCTRC-PG:MBCPTCI APL:T540 R15:001 ERR:00000 LEN:3792 SELECT READ 05/22/20 11:39:43 MBCPTCI x.x RJS1
MBCTRC-PG:MBCPTCI APL:T540 R15:268 ERR:00000 LEN:3792 READ 05/22/20 11:39:43 MBCPTCI x.x RJS1
MBCE175-CONNECTED FROM BATCH(JOB16470) USER(RJS1) XUSR(RJS1 05/22/20 11:39:43 MBCPTCI x.x RJS1
{Sample command message indicating a successful completion}
CLOS EMLSTS <OK 05/22/20 11:39:43 MBCPCMFI x.x MBC$RUN
MBCTRC-PG:MBCPTCI APL:T540 R15:001 ERR:00000 LEN:0268 SELECT WRITE 05/22/20 11:39:43 MBCPCMFI x.x MBC$RUN
MBCTRC-PG:MBCPTCI APL:T540 R15:268 ERR:00000 LEN:0268 WRITE 05/22/20 11:39:43 MBCPCMFI x.x MBC$RUN
MBCTRC-PG:MBCPTCI APL:T540 R15:001 ERR:00000 LEN:3792 SELECT READ 05/22/20 11:39:43 MBCPCMFI x.x MBC$RUN
MBCTRC-PG:MBCPTCI APL:T540 R15:008 ERR:00000 LEN:3792 READ 05/22/20 11:39:43 MBCPCMFI x.x MBC$RUN
MBCTRC-PG:MBCPTCI APL:T540 R15:000 ERR:00000 LEN:3784 SHUTDOWN 05/22/20 11:39:43 MBCPCMFI x.x MBC$RUN
MBCTRC-PG:MBCPTCI APL:T540 R15:000 ERR:00000 LEN:3784 CLOSE 05/22/20 11:39:43 MBCPCMFI x.x MBC$RUN
{Message written by MBC server indicating TCP/IP session has completed}
MBCE172-CLOSE SOCKET COMPLETE FOR APPL(T540) 05/22/20 11:39:43 MBCPTCI x.x MBC$RUN
Appendix C – Running IP Trace 191

A sample batch job log with tracing active appears on the following page.
Below is a sample batch job log of a TCP/IP session with Trace active. Any messages created by an executing
command should follow the actual command. Each command has an indicator such as <OK, <WARN or <ERR
indicating the success or failure of the command.

OPTS: ERRCNCL (016) CEDACMD (Y) ENQXS (N) RLUPDIS (N) IPVERS (N)
OPTS: ERRSTS (000)
MBCB001-MBCBATCH 2.1 STARTING JOB(JOB16470:MBC$RUN ) USER(RJS1 ) 07/25/20 14:12:21 MBCRXCI x.x RJS1
MBCB003-COMMAND PRE-PROCESSING STARTING 07/25/2014:12:21 MBCRXCI x.x RJS1
{Execution phase processes cards using TCP/IP}
MBCB004-COMMAND EXECUTION PHASE STARTING USING TCPIP 07/25/2014:12:21 MBCRXCI x.x RJS1
{Sample header card preceded by IPTR card followed by connection complete message}
MBCTRC-IP TRACING ACTIVE 07/25/2014:12:21 MBCRZIN x.x RJS1
CICS T540 <HDR 07/25/2014:12:21 MBCRZAPL x.x RJS1
BSD100I IPNRBSDC 01.05 F 09/12/11 18.37 0248F000 0026 20190725 122117:54
MBCTRC-PG:MBCRXINI APL:T540 R15:000 ERR:00000 FAM:INET SOCKET 07/25/2014:12:21 MBCRIPTR x.x RJS1
MBCTRC-PG:MBCRXINI APL:T540 R15:000 ERR:00000 LEN:00000 CONNECT 07/25/2014:12:21 MBCRIPTR x.x RJS1
MBCTRC-PORT:03100 IP:27.0.0.1 07/25/2014:12:21 MBCRIPTR x.x RJS1
MBCTRC-PG:MBCRXINI APL:T540 R15:001 ERR:00000 LEN:00016 SELECT WRITE 07/25/2014:12:21 MBCRIPTR x.x RJS1
MBCTRC-PG:MBCRXINI APL:T540 R15:016 ERR:00000 LEN:00016 WRITE 07/25/2014:12:21 MBCRIPTR x.x RJS1
MBCTRC-PG:MBCRXINI APL:T540 R15:001 ERR:00000 LEN:00080 SELECT READ 07/25/2014:12:21 MBCRIPTR x.x RJS1
MBCTRC-PG:MBCRXINI APL:T540 R15:080 ERR:00000 LEN:00080 READ 07/25/2014:12:21 MBCRIPTR x.x RJS1
MBCE170-IP CONNECTION COMPLETE TO APPL(T540) PORT(04097) XUSR(RJS1 ) 07/25/2014:12:21 MBCRXINI x.x RJS1
MBCTRC-PG:MBCRXDPL APL:T540 R15:001 ERR:00000 LEN:00268 SELECT WRITE 07/25/2014:12:21 MBCRIPTR x.x RJS1
MBCTRC-PG:MBCRXDPL APL:T540 R15:268 ERR:00000 LEN:00268 WRITE 07/25/2014:12:21 MBCRIPTR x.x RJS1
MBCTRC-PG:MBCRXDPL APL:T540 R15:001 ERR:00000 LEN:00268 SELECT READ 07/25/2014:12:21 MBCRIPTR x.x RJS1
MBCTRC-PG:MBCRXDPL APL:T540 R15:268 ERR:00000 LEN:00268 READ
{Sample command was successful}
CLOS EMLSTS <OK 07/25/2014:12:21 MBCRXDPL x.x RJS1
{Additional trace entries prior to Socket connection closing}
MBCTRC-PG:MBCRXCL APL:T540 R15:001 ERR:00000 LEN:00008 SELECT WRITE 07/25/2014:12:21 MBCRIPTR x.x RJS1
MBCTRC-PG:MBCRXCL APL:T540 R15:008 ERR:00000 LEN:00008 WRITE 07/25/2014:12:22 MBCRIPTR x.x RJS1
{Sample MBC message indicating Close Socket is complete}
MBCB172-CLOSE SOCKET COMPLETE FOR APPL(T540 ) 07/25/2014:12:23 MBCRXCL x.x RJS1
MBCB010-BATSTAT PROCESSING STARTING 07/25/2014:12:24 MBCRXCI x.x RJS1
MBCB011-BATSTAT RESOURCE UPDATES COMPLETED FOR FOLLOWING COMMANDS 07/25/2014:12:21 MBCRSTS x.x RJS1
MBCB012-UPDATED RESOURCE APPL:T540 TYPE:FI NAME:EMLSTS 07/25/2014:12:21 MBCRSTS x.x RJS1
MBCB013-CMD:CLOS EMLSTS 07/25/2014:12:21 MBCRSTS x.x RJS1
MBCB002-MACKINNEY BATCH TO CICS 2.1 ENDING MAXCC(000) 07/25/2014:12:21 MBCRXCI x.x RJS1
192 Appendix C – Running IP Trace

APPENDIX D – File List Processing
File List processing using MBCFLIST is a method to issue one command to operates on multiple resources. File List
processing is available as a limited compatibility method for previous users of the MTPFLIST and is not recommended
for new installations or for adding new file lists. Resource Groups (Section 3.8), which can be maintained either online
or by batch, is the preferred method. File list processing is only available for OPEN, CLOS, ENAB, INQY, UPDT,
ALOC, UNAL, ALOQ, and UNAQ commands. It is not available for CEMT SET commands. This section is included
for customers who previously used file lists.
WARNING! We do not recommend using File List with Status Tracking. If a file is defined in multiple MBCFLIST
groups and you OPEN and CLOS (or other commands) the groups at different times, then the file may end up in an
incorrect state after startup since for security reasons, startup reset processing is done in resource order and not by
timestamp. The same issue can occur if you OPEN and CLOS (or other commands) a resource both individually and
as part of a File List.
MBCFLIST is a table containing groups of files (file lists) which are processed by a single command from
MBCBATCH. MBCBATCH sends the command to CICS through the online/batch interface, providing as a parameter
a file list name which must begin with an '@' character. When the command is processed in CICS, the command is
processed on all of the files in the group denoted by the file list name. Each of the list(s) is terminated by a new file list
name or by the end of file list terminator (see warning below).
WARNING! The last entry in MBCFLIST must be DC CL8’@@@@@@@@’ and must immediately precede the END
statement.
Create this list as a source library member (MBCFLIST). Since it is only a data table, MBCFLIST is assembled and
linked using batch assembly JCL. It must be link edited into a library on the CICS RPL chain, preferably the same
library where MBCPXCI resides, and in the STEPLIB of the MBCBATCH job. MBCFLIST is then loaded into storage
when needed by MBCPXCI to process a file list command from MBCBATCH. A CICS transaction RDO (PPT) entry
is needed for MBCFLIST if file list processing is used. A sample file list is included on the installation tape as source
member MBCFLIST (VSE MBCFLIST.A).
z/OS: Following is a z/OS sample version of MBCFLIST incorporating the group name and files used above. Each
'DC' begins in column 10. Dataset name information, signified by data within quotes after the ‘CL48’, is used only by
the ALOC and ALOQ commands. If ALOC and ALOQ commands are not used in your system, code the 48 bytes as
spaces by entering: CL48' '.
DC CL8'@ACCTFIL' ← ACCTFIL file list

DC CL8'ACCT01 ',CL48'your01.acctfile.dsn'
DC CL8'@TRS ' ← TRS file list
DC CL8'TRSTXT ',CL48'DBDCCICS.TRSTXT'
DC CL8'TRSIND ',CL48'DBDCCICS.TRSIND'
DC CL8'TRSBKX ',CL48'DBDCCICS.TRSBKX'
DC CL8'TRSSTP ',CL48'DBDCCICS.TRSSTP'
DC CL8'TRSUSR ',CL48'DBDCCICS.TRSUSR'
DC CL8'TRSSYN ',CL48'DBDCCICS.TRSSYN'
DC CL8'@@@@@@@@' ← End of file list (Required!)
END
If your DSN does not fit on one line, continue on the next line using the following rules for extension:
1. No end quote is needed on first line

2. Any non-blank character should be placed in column 72 of the first line. ‘*’ is suggested
3. The constant name continues in column 16 of next line and ends with a quote mark
Col
1 1 7
0.....6 2
DC CL8’VERYLONG',CL48'your.very.long.dataset.name.that.will.no*
tfit'
Appendix D – File List Processing 193
VSE: Following is an equivalent file list for use on VSE. Note: there is no Dataset Name specification for VSE.
DC CL8'@ACCTFIL' ← ACCTFIL file list

DC CL8'ACCT01 '
DC CL8'ACCT02 '
DC CL8'ACCT03 '
DC CL8'ACCT04 '
DC CL8'@TRS ' ← TRS file list
DC CL8'TRSTXT '
DC CL8'TRSIND '
DC CL8'TRSBKX '
DC CL8'TRSSTP '
DC CL8'TRSUSR '
DC CL8'TRSSYN '
DC CL8'@@@@@@@@' ← End of file list (Required!)
END
194 Appendix D – File List Processing

APPENDIX E – CICS System Number and APPLIDs
A special record in the BATCNTL file is maintained for compatibility purposes with the CEMT from Batch
product users using a CICS system number in their JCL (either a CICS header card with a system number or using
header overrides in Column 72 or 80). This record is not needed if you are using CICS header cards with an
Applid or ApplGrp specified. This special record is maintained in one of two ways - online from the
Administration Menu (Section 3.4.2) or using the APPL command as input to MBCBATCH. The latter method is
described here.
After the BATCNTL file was defined and loaded from the installation tape and you have verified the installation
options are satisfactory, you can update the BATCNTL file with your CICS Applids by using APPL command as
shown in the following JCL. Up to 99 different CICS systems can be defined in this special record in the
BATCNTL file. Only include an APPL card for those CICS systems you defined to access using a CICS system
number in your JCL. 'DBDCCICS' and 'CICSTEST' are used only as examples.
z/OS
//CEMTAPPL JOB (ACCT),'NAME',NOTIFY=tsoid,MSGCLASS=X,CLASS=A
//*
//* Sample of JCL to update BATCNTL file with your CICS Applids
//*
//STEP01 EXEC PGM=MBCBATCH
//SYSUDUMP DD SYSOUT=*
//SYSIPT DD *
APPL 01 DBDCCICS
APPL 02 CICSTEST
/*
VSE
The LIBDEF should point to the lib.sublib where MacKinney Batch to
CICS was installed.
// JOB MBCBATCH
*
* SAMPLE OF JCL TO UPDATE BATCNTL FILE WITH YOUR CICS APPLIDS
*
// DLBL BATCNTL,'MBC.BATCNTL',,VSAM,CAT=XXXXXX
// EXEC MBCBATCH,SIZE=64K
APPL 01 DBDCCICS
APPL 02 CICSTEST
/*
NOTE: Do NOT specify the same Applid for more than one CICS system number.
You can use the same JCL with APPL commands to change existing Applids on the BATCNTL file. To inactivate an
Applid on the BATCNTL file, use the command ‘APPL nn *UNUSED*’. It replaces the Applid defined to CICS
number ‘nn’ with an Applid of *UNUSED* (where ‘nn’ is the number associated with the Applid to inactivate).
Appendix E – CICS System Number and APPLIDs 195

APPENDIX F – Message Cross Reference
Below is a cross reference for most of the messages produced by the CEMT from Batch product with respect to the new
MBC product messages. In many cases, the message text for the new message is not the same as it was with the old.
You should review text to compare the new and old messages if you are using automation utilities that rely on message
text.
CMTB001 – MBCB001 CMTE121 – MBCE121 CMTE307 – MBCE307

CMTB005 – MBCB005 CMTI122 – MBCE122 CMTE308 – MBCE308
CMTB067 – MBCB205 CMTE146 – MBCE166 CMTW322 – MBCE322
CMTE000 – MBCE000 CMTE147 – MBCE167 CMTE323 – MBCE323
CMTE103 – MBCB052 CMTE148 – MBCE168 CMTE324 – MBCE324
CMTE106 – MBCE106 CMTE147 – MBCE167 CMTI326 – MBCE326
CMTE107 – MBCE107 CMTI152 – MBCE109 CMTI327 – MBCE327
CMTE111 – MBCE111 CMTE301 – MBCE301 CMTI329 – MBCE329
CMTE119 – MBCE119 CMTE305 – MBCE305
CMTI120 – MBCE120 CMTE306 – MBCE306
196 Appendix F – Messages Cross Reference

APPENDIX G – MBCE128 Error Codes
Below is a cross reference for most of the error codes produced by the DFHEMTA interface. The DFHEMTA interface has
not been documented by IBM since CICS ESA Version 3 although its use is still supported. Some newer return codes are
being used by IBM but these are not documented. If possible, use CEMT online to duplicate error and to obtain the error
description.
ERROR CODE DESCRIPTION ERROR CODE DESCRIPTION
001 NOT FOUND 066 <=TCLASS MAXTASKS

002 CLASS NOT FOUND 067 PARTIAL DUMP
003 ERROR 068 DDNAME NOT FOUND
004 BEGINS WITH DFH 069 BEING ACQUIRED
005 CHANGE INVALID 070 BEING FORCECLOSED
006 CANNOT NEWCOPY 071 NOT FOR HOLD PROG
007 NOT AUTHORIZED 072 LOAD FAILED
008 OPTION CONFLICT 073 SDUMP FAILED
009 PRIORITY > 255 074 NOT CLOSED
010 NOT FOR CONSOLE 075 NOT DISABLED
011 PROGRAM NOT FOUND 076 CLOSE REQUESTED
012 BROWSE ERROR 077 BEING OPENED
013 INVALID ATI / TTI 078 BEING UNENABLED
014 IS NOT INTRA 079 BEING DISABLED
015 OPEN/SWITCH FAIL 080 READY FOR RECOVER
016 SDUMP BUSY 081 READY FOR DUMP
017 NOT SUCCESSFUL 082 START/SWITCH FAIL
018 0>TRIGGER>32767 083 DLI NOT ACTIVE
019 NOT FOR INDIRECT 084 INVALID INTERVAL
020 0>MAXIMUM>999 085 OUT & ACQ INVALID
021 IS NOT EXTRA 086 SEE MSG DFH3768
022 OPEN/CLOSE FAILED 087 SEE MSG DFH3786
023 SDUMP SUPPRESSED 088 NOT FOR MAPSET
024 BEGINS WITH C 089 SEE MSG DFH3771
025 JACD I/O ERROR 090 NOT FOR PARTITION
026 JACD LOGIC ERROR 091 SEE MSG DFH3773
027 NOT FOR SMF 092 SEE MSG DFH3787
028 ALREADY EXISTS 093 SEE MSG DFH3775
029 CATALOG I/O ERROR 094 SEE MSG DFH3776
030 32>MAXTASKS>999 095 SEE MSG DFH3777
031 NOT FOR REMOTE 096 SEE MSG DFH3778
032 2>AMAXTASKS>999 097 SEE MSG DFH3779
033 0>AGING>65535 098 SEE MSG DFH3780
034 AKP NOT IN SYSTEM 099 SEE MSG DFH3781
035 MAXT. < AMAXT. 100 SEE MSG DFH3791
036 NOT IN SYSTEM 101 ONLY FOR VTAM
037 END/DISA FAILED 102 GOING OUT
038 200>AKP>65535 103 SPECIFY NUMBER
039 CATALOG FULL 104 NUMBER ERROR
040 0>CSCS>CDSASIZE 105 NEGPOLL INVALID
041 1>MAXIMUM>MAXTASK 106 >20000
042 INVALID DUMPCODE 107 INVALID ENDOFDAY
043 FAILING 108 MAX | SHUTDOWN
044 500>RUN. >2700000 109 LINE DCB NOT OPEN
045 100>TIME>3600000 110 JOURNAL NOT FOUND
046 TCLASS>10 111 SET FAILED
047 TIME < SCANDELAY 112 REMOVE FAILED
048 CEILING REACHED 113 REQUEST FAILED
049 1>MROBATCH>255 114 FILECOUNT > 0
050 0>ECSCS>ECDSASIZE 115 NOT OPEN
051 CLOSE FAILED 116 BACKOUT FAILED
052 NOT FOR BDAM 117 DAT X NOT READY
053 CLOCK INOPERATIVE 118 >MAXIMUM
054 NOT VALID VTAM 119 NOT LUC
055 NOT FOR PATH 120 PREV IRLM CLEANUP
056 OPEN FILE 121 NO LOCAL DLI
057 BEING CLOSED 122 CONNECTION \ACQD
058 BEING IMMCLOSED 123 IRLM REQUEST FAIL
059 0>SCANDELAY>5000 124 IN PROGRESS
060 NOT FOR SNASVCMG 125 IRLM NOT UP YET
061 NOT FOR THIS TASK 126 NO IRLM SUPPORT
062 NOT FOR YOUR TERM 127 ALREADY CONNECTED
063 NOT FOR YOUR CU 128 RESOURCE MISSING
064 NOT FOR YOUR LINE 129 STATS MISSING
065 QUEUE IS DISABLED 130 IS SIT PARAMETER
Appendix G – MBCE128 Error Codes 197

131 CANNOT LOAD PLT 170 BWO ERROR
132 ALREADY EXISTS 171 DFHTMP ERROR
133 NO DATASET 172 PRESET SIGNON ERR
134 DLI I/F ERROR 173 NOT FOR CPSVCMG
135 PURGE FAILED 174 PRM UNAVAILABLE
136 FILE IN USE 175 NOT WHEN XLN DONE
137 ONLY FOR BDAM 176 0>USCS>UDSASIZE
138 STOPPED 177 0>EUSCS>EUDSASIZE
139 SEE MSG DFH3798 178 0>EUSCS>ERDSASIZE
140 PROGRAM IS URM 179 FREE NOT COMPLETE
141 IN USE 180 BEING RELEASED
142 IN USE BY ICE 181 REUSE DEFINED
143 IN USE BY PCT 182 UNBLOCKED DEFINED
144 NOT RELEASED 183 16< MAX.<16777215
145 DELETE FAILED 184 FORMAT NOT VARIABLE
146 WORK PENDING 185 NO LSRPOOL
147 NOT OUTSERVICE 186 NEVER OPENED
148 IN USE BY TCT 187 INVALID FREQUENCY
149 AUTOINSTALLED 188 0>PURGET>1000000
150 IS ENABLED EXIT 189 INVALID PSDINT
151 IS IN PLT 190 NOT WITH XRF
152 IN USE BY AID 191 SETLOGON FAILURE
153 NOT FOR SESSION 192 BACK LEVEL VTAM
154 NOT FOR PIPELINE 193 ACB CLOSED
155 NOT DISCARDABLE 194 RECOVERY ERROR
156 NOT LOCAL SYSTEM 195 DEFERRED
157 NOT FOR SYSTEM 196 NOT FOR LOCAL SYS
158 NOT FOR MODEL 197 SEE MSG DFHIR3799
159 NO ACTION 198 ONLY FOR APPC
160 CANNOT LOAD XLT 199 ESM INACTIVE
161 ISC NOT DEFINED 200 REGISTER ERROR
162 ALREADY ACTIVE 201 DEREGISTER ERROR
163 JOURNAL NOT TAPE 202 AIDS CANCELED
164 JOURNAL NOT SL 203 ALREADY IN USE
165 NO BWO SUPPORT 204 SUFFIX NOT FOUND
166 DSNB IS INVALID 205 INVALID SUFFIX
167 DSNB BDAM OR PATH 206 NOT REQUIRED
168 UPDATE COUNT > 0 207 STILL CLOSING
169 DSN NOT SMS MGD 208 NO AIDS CANCELED
198 Appendix G – MBCE128 Error Codes

Index
APPLSTS ................................................................ 42, 61, 115, 139

SAPL DN ............................................................................. 42, 139
* SAPL UP ............................................................................. 42, 139
Autoinstall .....................................................................................42
*
Command Parm...................................................................... 118
B
? Batch Utilities ................................................................ See Utilities

BATCNTL................................................................. 29, 35, 54, 111
defining .................................................................................... 29
?
Help Screens ............................................................................. 29
Command Parm.............................................................. 134, 135
loading...................................................................................... 29
SHAREOPTIONS ........................................................................ 29
BATCSTS .....................................................................................35
@ Maintenance .......................................................................... 152
BATSTAT ................................................... 29, 35, 39, 54, 111, 152
@APPLGRP ............................................................................... 124 Maintenance .......................................................................... 152
@ItemScope MBCPRSTX ......................................................................... 152
Region ...................................................................................... 85 retry.......................................................................................... 62
Shared ...................................................................................... 83 SHAREOPTIONS ........................................................................ 29
Unique ...................................................................................... 84 BSI
@RLS1GRP ............................................................................... 124 TCP/IP Tools for VSE ................................................................. 33
< C
<ERR .......................................................................................... 107 CA Datacom/DB ................................................................. 126, 140
<OK ............................................................................................ 107 CDAL ........................................................................ 43, 47, 61, 121
<WARN...................................................................................... 107 CEDA .................................................................... 9, 43, 47, 61, 122
CEDACMD ........................................................................... 61, 105
CEMT ...................................................................................... 43, 61
A CEMT DISCARD .......................................................................123
CEMT INQUIRE.........................................................................123
Abend codes ....................................................................... 174, 189 CEMT PERFORM ......................................................................123
Administration Menu .................................................................... 57 CEMT SET .......................................................................... 123, 195
AEPL ............................................................................................ 47 CEMTPERF .......................................................................... 61, 105
AEZC.................................................................................... 47, 132 from PERFORM......................................................................... 46
ALOC .......................................................................... 119, 143, 195 CEMTRTRY .................................................................................60
ALOG ........................................................................ 47, 57, 82, 119 from CEMTCNT ......................................................................... 46
ALOQ ................................................................................... 47, 119 CICS Header........................................ 57, 60, 61, 63, 105, 114, 124
ALOR ................................................................................... 47, 120 @APPLGRP ............................................................................. 124
ALSG......................................................................... 47, 57, 82, 119 @RLS1GRP.............................................................................. 124
ALSR .................................................................................... 47, 120 CICS Listener .................................................................. 33, 41, 102
API...................................................................................... 106, 146 CICS Log
APPL .................................................................................. 120, 197 Sample EXCI............................................................................ 147
APPLGRP................................................................................... 124 Sample PLT Resource Allocation ............................................ 155
ApplGrps Sample Status Tracking .......................................................... 156
Copy Screen .............................................................................. 68 Sample TCP/IP ........................................................................ 147
Defined ..................................................................................... 65 Sample TCP/IP Trace .............................................................. 193
Directory Screen ....................................................................... 65 CICS Status Tracking ....................................................................98
Maintenance ............................................................................ 57 Detail Screen ............................................................................ 99
SAPL ........................................................................................ 139 Maintenance Screen ................................................................ 98
Update Screen .......................................................................... 66 CICS/Message: ..............................................................................13
Using with Resource Groups .................................................... 72 CICS/MORNING NEWS ............................................................133
APPLID ................................................................................ 63, 120 CLDG ..........................................................................................125
Applid Groups ............................................................ See ApplGrps CLOD ..........................................................................................125
Applid Status Tracking ....................................................42, 61, 139 CLOG .................................................................................... 47, 125
Index 199
CLOS .................................................................................... 59, 125 ENQXS........................................................................ 34, 35, 46, 61
CLOSDIS ..................................................................................... 59 ERRCMD ................................................................ 46, 60, 105, 106
CLOSRQST .................................................................................. 59 from ERRCODE ......................................................................... 46
from CLOREQST ........................................................................ 46 ERRCNCL..................................................................... 60, 105, 106
CLOSRTRY ................................................................................. 60 from ERRFLSH ........................................................................... 46
from CLOSECNT ........................................................................ 46 ERRDOWN ................................................................... 60, 105, 106
CLOV ................................................................................... 47, 125 ERRDRLS ..................................................................... 60, 105, 106
CLVG ......................................................................................... 125 Error Messages ............................................................................159
CMDEXIT ............................................................................ 59, 146 ERRSEC ........................................................................ 60, 105, 106
COBBCMDX ............................................................................. 114 ERRSTS ................................................................ 62, 105, 106, 151
COBBCRCX .............................................................................. 115 ERRWARN ................................................................... 60, 105, 106
COBBHDRX .............................................................................. 114 EXCI............................................................................ 9, 30, 32, 105
COBBLOGX ...................................................................... 114, 115 Connections ............................................................................. 32
COBBLXGX .............................................................................. 114 Sessions .................................................................................... 32
COBBOPSX ............................................................................... 115 Execution Userid
COLUMN80 ........................................................................... 61, 63 Defined ..................................................................................... 50
Command Extended Data
Comment ................................................................................ 118 Batch User Exit ....................................................................... 114
Syntax ..................................................................................... 116 Commands ............................................................................... 43
Comment .................................................................................... 118 EMTMSGS ................................................................................. 43
CSCQ Header ..................................................................... 124, 157 LOGXDD .................................................................................... 43
CSDA ......................................................................................... 126 MBCBLXGX ............................................................................. 114
CSDD ......................................................................................... 126 SYSLSTX .................................................................................... 43
CSMT ........................................................................................... 59 Extrapartition TDQ ........................................................ 45, 119, 143
EXTSEC .............................. 30, 39, 46, 50, 51, 52, 59, 61, 140, 141
EZACIC20.....................................................................................33
D EZACICD......................................................................................33
EZASTRUE...................................................................................33
Datacom/DB ....................................................................... 126, 140
DBLC ................................................................................. 126, 140
DBOC ................................................................................. 126, 140 F
DFHRPL ....................................................................................... 35
DFHXCOPT ........................................................................... 32, 36 FAILACT .............................................................................. 60, 105
CICSSVC .................................................................................... 32
from ERRWTOR ........................................................................ 46
XCFGROUP ................................................................................ 32 File
DL/I .................................................................................34, 45, 126 Allocate .................................................................................. 119
DLBC ........................................................................................... 34
Close ....................................................................................... 125
DLOC ................................................................................... 34, 126
Disable .................................................................................... 125
STOP ....................................................................................... 126
Enable..................................................................................... 127
STRT ........................................................................................ 126
Inquiry ............................................................................. 131, 137
DLPV.......................................................................................... 126
Domain Applids.......................................................................... 102 In-Use ..................................................................................... 125
Applid value ............................................................................ 103 Open ....................................................................................... 134
Directory Screen ..................................................................... 102 RLSACCESS ....................................................... 131, 137, 138, 144
Maintenance ............................................................................ 57 Unallocate .............................................................................. 143
Update Screen ........................................................................ 103 Update............................................................................. 138, 144
Domain Security ..................................................................... 48, 50
DOMSEC .............................................................. 35, 46, 48, 50, 61
DOWNNON ......................................................................... 60, 105 G
DOWNSPC........................................................................... 60, 105
DOWNSTS ........................................................................... 47, 127 generic file name ................................................. 125, 127, 131, 144
DSNC ......................................................................................... 127 GLQY .......................................................................... 129, 131, 137
DTIMOUT .................................................................................... 42 GLSQ .................................................................................. 128, 137
Dynamic file allocation......................................................... 35, 143 GLSU .................................................................................. 128, 138
GLUP .................................................................................. 129, 138
GPQY .................................................................................. 129, 137
E GPUP ................................................................................... 129, 138
GRS ...............................................................................................34
EIBFN return codes .................................................................... 190 MIM.......................................................................................... 34
EIBRCODE response codes ....................................................... 191 SDSI .......................................................................................... 34
ELSE ............................................................................................ 47 GSQY .................................................................................. 129, 137
EMTMSGS ............................................................................. 43, 61 GSSQ ................................................................................... 128, 137
ENAB ......................................................................................... 127 GSSU ................................................................................... 128, 138
ENAG ................................................................................... 47, 127 GSUP ................................................................................... 129, 138
ENDIF .......................................................................................... 47
200 Index
H M
HDROVER ............................................................................. 61, 63 MAXCC ........................... 106, 108, 130, 151, See IF/ELSE/ENDIF
Header ......................................................... 57, 60, 61, 63, 105, 114 MBC1 ...................................................................................... 54, 98
Help Screens MBCA ............................................................................... 51, 56, 57
MBCJFILB .................................................................................. 29 CLR ........................................................................................... 56
Help Screens MBCB ..................................................................................... 52, 57
Loading ..................................................................................... 29 MBCBAGRP ......................................................................... 69, 104
MBCJHELP................................................................................. 29 MBCBATCH....................................................... 34, 37, 38, 60, 105
alias .......................................................................................... 40
Sample VSE JCL ......................................................................... 38
I Sample z/OS JCL ....................................................................... 37
MBCBCMDX .............................................................................114
MBCBCNV .................................................................................109
IDIS .............................................................................................. 47
MBCBCNVS ...............................................................................109
IF 47
MBCBCPRE ...............................................................................154
IF/ELSE/ENDIF ......................................................................... 130
MBCBCPRT ....................................................................... 109, 113
LASTCC.................................................................................... 130
MBCBCRCX...............................................................................115
MAXCC............................................................................ 130, 139 MBCBCSTS ................................................................................100
SET .................................................................................. 130, 139 MBCBCUTL ...............................................................................109
user variables ................................................................. 130, 139 MBCBDOM ........................................................................ 102, 104
INQG .......................................................................................... 131 MBCBHDRX ..............................................................................114
INQUIRE .................................................................................... 136 MBCBLOGX ................................................................ 46, 114, 115
INQY .......................................................................................... 131 MBCBLXGX ........................................................................ 43, 114
Installation Options....................................................................... 57 MBCBOPSX ...............................................................................115
Intrapartition TDQ ........................................................................ 45 MBCBPREX ...............................................................................114
IPTR ................................................................................... 132, 192 MBCBRGRP ................................................................... 82, 96, 100
IRCSTRT...................................................................................... 30 MBCBRITM ........................................................................... 70, 79
ISC ................................................................................................ 30 MBCBSTAT ...............................................................................101
MBCBSUTL ...............................................................................153
MBCC ................................................................................... 52, 145
J MBCD ................................................................................... 52, 102
MBCDLOC
JCL Password ........................................................................... 34, 126
Sample VSE MBCBATCH JCL ..................................................... 38 MBCFLIST ........................... 34, 125, 127, 131, 134, 143, 144, 195
Sample z/OS MBCBATCH JCL .................................................... 37 MBCG ..................................................................................... 52, 82
Job Log MBCH ...........................................................................................52
Batch User Exit ............................................................... 114, 115 MBCI....................................................................................... 52, 70
MBCJAGRP ..................................................................................69
Sample EXCI ............................................................................ 107
MBCJASMC ......................................................................... 34, 146
Sample TCP/IP ........................................................................ 108
MBCJBAT.....................................................................................37
Sample TCP/IP Trace .............................................................. 194 MBCJCPRE.................................................................................154
MBCJCPRT.................................................................................113
MBCJCSTS .................................................................................100
L MBCJCUTL .......................................................................... 62, 109
MBCJDOM .................................................................................104
LASTCC .................................. 106, 115, 130, See IF/ELSE/ENDIF MBCJEZA .....................................................................................33
LFP ..................................................................... See Linus Fax Path MBCJFILC ....................................................................................29
Link MBCJFILS ....................................................................................29
Commarea .............................................................................. 132 MBCJRDO ....................................................................................30
Program .................................................................................. 132 MBCJRDO ....................................................................................30
LINK .......................................................................................... 132 MBCJRDOA .................................................................................30
Linux Fast Path ............................................................................. 33 MBCJRDOC .................................................................................32
Listener MBCJRDOC .................................................................................30
Address Family ......................................................................... 33 MBCJRDOF ............................................................................ 30, 31
IP Address ............................................................ 33, 41, 102, 103 MBCJRDOS ............................................................................ 30, 31
MBCJRGRP ..................................................................................96
Port ...................................................................... 33, 41, 102, 103
MBCJRITM...................................................................................79
Userid ................................................................................. 33, 61
MBCJSTAT.................................................................................101
LNKL ......................................................................................... 132 MBCJSUTL.................................................................................153
LOADPGM .................................................................................. 60 MBCJZLU .....................................................................................43
LOGXDD .......................................................... 43, 46, 61, 122, 136 MBCL...................................................................................... 52, 65
ASSGN....................................................................................... 43 MBCM ..........................................................................................52
SYSLSTX..................................................................................... 43 MBCO ............................................................................... 52, 82, 94
MBCP ............................................................................................52
MBCPCMD .................................................................................146
Index 201
MBCPCMDX ............................................................................. 145 PLT.applid ............................................................ 40, 88, 150, 151
MBCPDLOC .............................................................................. 126 PLTPIUSR............................................................................... 49, 51
MBCPMSG ................................................................................ 133 PLTSD
MBCPOCP ................................................................................. 145 EZACIC20 .................................................................................. 40
MBCPPLA ................................................................................... 40 EZASTRUE ................................................................................. 40
MBCPPLQ .................................................................... 40, 157, 158 MBCPPLT .................................................................................. 40
MBCPPLT .................................................................................. 151 PREFIX .........................................................................................59
MBCPRSTX ....................................................................... 146, 152 Product Password
MBCPSCN ......................................................................... 145, 146 Batch Maintenance .................................................................. 58
MBCQ .............................................................................52, 61, 140 Maintenance ....................................................... 57, 58, 109, 113
MBCR .......................................................................................... 52 Update................................................................................. 35, 36
MBCS ................................................................................52, 82, 95
PROGAUTOINST ........................................................................42
MBCU .................................................................................... 53, 57 PTF level .......................................................................................28
MBCX .......................................................................................... 53 PTF Level Set ................................................................................64
MBCZ ........................................................................................... 54 PTFs ..............................................................................................64
MESG ......................................................................................... 133
Message ...................................................................................... 133
MESG ................................................................................ 13, 133
MSGL ................................................................................ 13, 133 Q
multi-line ................................................................................ 133
Product ............................................................................. 13, 133 QRYL ........................................................................ 43, 47, 61, 136
MIM.............................................................................................. 34 QRYS ........................................................................ 43, 47, 61, 136
MSGL ......................................................................................... 133
MTPBATCH
alias .......................................................................................... 40 R
MTPFLIST ................................................ 34, 195, See MBCFLIST
MTPSTATR RDO
PLTPI ......................................................................................... 36 BATCNTL entry ......................................................................... 31
BATCSTS entry ..................................................................... 29, 31
BATSTAT entry .......................................................................... 31
N Connection Entries ................................................................... 32
Definitions ................................................................................ 30
NEWC ........................................................................................ 134 File Entries ..................................................................... 31, 39, 48
NEWCOPY ................................................................................ 134 Installing ................................................................................... 30
Program Entries........................................................................ 30
Sample entries.......................................................................... 30
O Sessions Entries ........................................................................ 32
TCT Entries ............................................................................... 30
Online Command Processor ....................................................... 145 Terminal Entries ....................................................................... 30
OPEG.................................................................................... 47, 134 Transaction Entries ................................................................... 30
OPEN.......................................................................................... 134 Resource Groups
Options @ItemScope ............................................................................. 88
Batch ................................................................................ 60, 105 Add Screen ............................................................................... 88
Installation Options ............................................................ 36, 59 Allocate .................................................................................. 119
Online ....................................................................................... 59 Batch Updates ................................................................... 96, 100
Override ................................................................................. 135 Copy Screen.............................................................................. 92
Status Tracking ................................................................. 62, 151 Defined ..................................................................................... 82
Update via Batch ...................................................................... 62 Instead of MTPFLIST ............................................................... 195
OPTR ................................................................. 47, 59, 61, 130, 135 Item Screen .............................................................................. 90
OS390 ........................................................................................... 38 Maintenance ............................................................................ 57
Maintenance Screen ................................................................ 89
Operation Screen ..................................................................... 94
P PLT.applid ............................................................................ 40, 88
Status Screen ............................................................................ 95
PASS .................................................................................... 58, 113 Using with @ApplGrps ............................................................. 65
PHAS .......................................................................................... 135 Using with ApplGrps ............................................................ 66, 72
PHASEIN ................................................................................... 135 Resource Items
PLTPI Allocate .................................................................................. 120
EZACIC20 ............................................................................ 33, 40 Applid .................................................................................. 72, 81
EZASTRUE ........................................................................... 33, 40 Batch Update............................................................................ 79
MBCPPLA .................................................................................. 40 Defined ..................................................................................... 70
MBCPPLQ.......................................................................... 40, 158 Maintenance ............................................................................ 57
MBCPPLT .................................................................................. 40 Name ........................................................................................ 72
MTPSTATR ................................................................................ 36 Shared ...................................................................................... 65
202 Index
Type .......................................................................................... 72 STRL ........................................................................................ 141
Type=FI ..................................................................................... 73 Terminal ................................................................................. 141
Type=IP ..................................................................................... 76 Transaction............................................................................. 141
Type=PG ................................................................................... 74 Userid ..................................................................................... 141
Type=TD ................................................................................... 77 Startup Commands ......................................................................157
Type=TR .................................................................................... 75 CSCQ Header ................................................................... 124, 157
Type=TX .................................................................................... 78 Deleting .................................................................................. 158
Unallocate .............................................................................. 143 Executing ................................................................................ 158
Update Screen .................................................................... 72, 81 MBCPPLQ ............................................................................... 157
Update Status ......................................................................... 142 PLTPI ....................................................................................... 158
RINT ............................................................................................. 47 Storing ............................................................................. 124, 157
RLQY .......................................................................... 129, 131, 137 Startup Manager .................................................................. 148, 150
RLS STATFLAG................................................................... 62, 115, 151
QUIESCE.................................................................................. 128 STATRTRY .................................................................... 46, 62, 151
RLS1GRP ................................................................................... 65 Status Tracking .............................................................. 62, 130, 148
RLSACCESS ....................................................... 131, 137, 138, 144 Administration ....................................................................... 151
UNQUIESCE ............................................................................ 128 DOWNSTS ............................................................................... 127
RLS1GRP ................................................................................... 124 Maintenance ............................................................................ 57
RLSQ .................................................................................. 128, 137 Resources ............................................................................... 148
RLSU .................................................................................. 128, 138 Scope ...................................................................................... 148
RLUP .................................................................................. 129, 138 Startup Manager ............................................................. 148, 150
RLUPDIS ...................................................................... 60, 129, 138 STRL ...........................................................................................141
RPQY ................................................................................. 129, 137 STRTUPMG.................................................................... 46, 62, 151
RPSQ .................................................................................. 128, 137 STSG .............................................................................................47
RPSU .................................................................................. 128, 138 STSR ..................................................................................... 47, 142
RPUP .................................................................................. 129, 138 Surrogate ........................................................................... 33, 50, 51
RSQY ................................................................................. 129, 137 SVC99 ................................................................................... 47, 143
RSSQ .................................................................................. 128, 137 SYSLST .............................................................................. 114, 115
RSSU .................................................................................. 128, 138 SYSLSTX.................................................................... 114, 122, 136
RSUP .................................................................................. 129, 138
T
S
TASKDATALOC.................................................................. 47, 132
SAPL .......................................................................................... 139 TCP/IP ............................................................................... 9, 33, 105
SDFHEXCI................................................................................... 36 BSI ............................................................................................ 33
SDSI ............................................................................................. 34 LFP ............................................................................................ 33
Securing Files ............................................................................... 54 Linux Fast Path ......................................................................... 33
Securing Resources....................................................................... 50 Stack .............................................................................. 10, 33, 43
Securing Transactions ................................................................... 51 Stack ID................................................................................ 33, 38
SET ............................................ 47, 106, 139, See IF/ELSE/ENDIF
Trace.................................................................................. 43, 192
SHUT.................................................................................... 30, 140
TDMESGQ ....................................................................................59
SHUTCMD.................................................................... 61, 105, 140
TDQ
Shutdown
Allocate .................................................................................. 119
CICS......................................................................................... 140
Extrapartition ............................................................ 45, 119, 143
SHUTCMD ......................................................................... 61, 105
Handling ................................................................................... 45
SHUTTERM ....................................................................... 59, 140
Intrapartition ............................................................................ 45
Terminal ................................................................................... 30
Unallocate .............................................................................. 143
Userid ............................................................................... 61, 140
Timeout
SHUTTERM.............................................................. 30, 52, 59, 140
DTIMOUT.................................................................................. 42
SIT Entries .................................................................................... 30
Transient Data Queue ................................................... 45, See TDQ
IRCSTRT .................................................................................... 30
TRKNONFI ..................................................................... 46, 62, 151
ISC............................................................................................. 30
XCMD........................................................................................ 50
XFCT .......................................................................................... 50
XTRAN....................................................................................... 50
U
XUSER ................................................................................. 50, 51
Socket errors ................................................................................. 38 UNAG ...........................................................................................57
SPCOMMAND ............................................................................ 50 UNAL ..........................................................................................143
Stack ID .................................................................................. 33, 38 UNAQ ................................................................................... 47, 143
STAR .......................................................................................... 141 UNAR.................................................................................... 47, 143
STAR DBOC .............................................................................. 140 UPDG .................................................................................... 47, 144
Start UPDT ..........................................................................................144
Data ........................................................................................ 141 URT .............................................................................................126
STAR ....................................................................................... 141 User Exit
Index 203
Batch ...................................................................................... 114 MBCBSTAT .............................................................................. 101
MBCBCMDX ............................................................................ 114 MBCBSUTL ....................................................................... 109, 153
MBCBCRCX ............................................................................. 115 MBCJCNV........................................................................... 35, 111
MBCBHDRX............................................................................. 114 MBCJCNV2.............................................................................. 112
MBCBLOGX ................................................................ 46, 114, 115 MBCJCNVR ............................................................................. 112
MBCBLXGX.............................................................................. 114 MBCJCNVS ......................................................................... 39, 111
MBCBOPSX ............................................................................. 115
MBCBPREX.............................................................................. 114
MBCPCMDX ............................................................................ 146 V
MBCPRSTX .............................................................................. 146
Online ..................................................................................... 146 VSE
user variables ................................................... See IF/ELSE/ENDIF Conversion from CMT Installation............................................ 20
Userid New Installation ....................................................................... 19
Batch ........................................................................................ 49 Sample MBCBATCH JCL ............................................................ 38
Execution ..................................... 50, 51, 52, 53, 59, 61, 104, 140
IP Exec ................................................................. 49, 51, 103, 104
Link ........................................................................................... 51
Listener ........................................................................ 33, 61, 104
W
PLTPIUSR ....................................................................... 49, 50, 51
Region ........................................................................... 49, 50, 51 WAIT .................................................................................... 47, 144
Session...................................................................................... 44 Web refresh ............................................................................. 28, 64
Shutdown ................................................................................. 59
surrogate .................................................................................. 51
Utilities X
MBCBAGRP ............................................................................. 109
MBCBCNV .................................................................. 35, 109, 111 XCF/MRO .....................................................................................10
MBCBCNV2 ............................................................................. 112 XCFGROUP ..................................................................................32
MBCBCNVR ..................................................................... 109, 112 XUSER .................................................................................... 50, 51
MBCBCNVS ....................................................................... 39, 111
MBCBCPRE.............................................................................. 154
MBCBCPRT.............................................................................. 109 Z
MBCBCSTS .............................................................................. 100
MBCBCUTL................................................................................ 35 z/OS
MBCBDOM ............................................................................. 109 Conversion from CMT Installation............................................ 18
MBCBRGRP ............................................................................. 109 New Installation ....................................................................... 17
MBCBRITM ............................................................................. 109 Sample MBCBATCH JCL ............................................................ 37
204 Index

MBC21

Uploaded by

Copyright:

Available Formats

You might also like

MBC21

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MBC21

Uploaded by

Copyright:

Available Formats

MacKinney Batch to CICStm

Installation and User Guide

Copyright 2006,2021 - All Rights Reserved

MacKinney Batch to CICS

0.1 Introduction ............................................................................................................................................. 9

APPENDIX A - EIBFN ............................................................................................................................ 188

Index ......................................................................................................................................................... 199

MacKinney Batch to CICS

Summary of Changes for MacKinney Batch to CICS 2.1

Summary of Changes for MacKinney Batch to CICS 2.0

• Added support for new Startup Manager

Summary of Changes for MacKinney Batch to CICS 1.6

• Added support for multiple administrators in a region at the same time

Summary of Changes for MacKinney Batch to CICS 1.4

Summary of Changes for MacKinney Batch to CICS 1.3

• Support for RLS commands RLSQ (QUIESCE) and RLSU (UNQUIESCE)

Summary of Changes for MacKinney Batch to CICS 1.2

∙ an individual CICS terminal or Netname

0.4.2 CEMT from Batch

1. MBCFDFCT Batch buffer allocation macro

1. MBCJAGRP Sample JCL to run ApplGrp Utility

1. MBCBAGRPOM Batch utility program for ApplGrp records

1.1 Steps for Installing MacKinney Batch to CICS

Download MacKinney Batch to CICS from our Web page at www.mackinney.com.

16 Section I – Installation Guide

1. Review Section 1.2 Description of MBC Files

Section I – Installation Guide 17

1. Review Section 2.2 in its entirety

18 Section I – Installation Guide

1. Review Section 1.2 Description of MBC Files

Section I – Installation Guide 19

20 Section I – Installation Guide

Parallel Testing MBC 2.1 with MBC 1.2 – 1.6 (WARNING!!!)

Section I – Installation Guide 21

Upgrading from MBC 2.0

22 Section I – Installation Guide

Section I – Installation Guide 23

24 Section I – Installation Guide

Section I – Installation Guide 25

1.1.6 Upgrading Current Release to a new PTF Level

28 Section I – Installation Guide

Section I – Installation Guide 29

MBCJRDO – sample program and transaction definitions minus administration

1.3.2 Defining SHUT Terminal Definition [ZNew] [ZCnv] [VNew] [VCnv]

1.3.3 Defining SIT Entries [ZNew] [ZCnv] [VNew] [VCnv]

30 Section I – Installation Guide

Converting from CEMT from Batch users

All Other users

Section I – Installation Guide 31

1.4.1 Verifying EXCI Options (DFHXCOPT) [ZNew] [ZCnv]

MBCB021-CONNECT FAILED: APPL(yourCICS) RESP(00655360) REASON(00078049-00000000)

1.4.2 Defining Connection and Sessions Entries [ZNew] [ZCnv]

32 Section I – Installation Guide

1.5.1 IP Stack Considerations [VNew] [VCnv]

Running BSI TCP/IP Tools for VSE Stack

Running CSI TCP/IP for VSE Stack

1.5.2 Verifying Standard Listener Support [VNew] [VCnv]

1.5.3 Defining Domain Applid Records [VNew] [VCnv]

Section I – Installation Guide 33