CONTROL-M/TAPE (formerly CONTROL-T) Messages. The following CONTROL-M/TAPE messages are intercepted by the SMC. Refer to BMC's INCONTROL for OS/390 and z/OS Message Manual for the exact format and meaning of each message. Feb 16, 2019 DOWNLOAD: Control m user guide for z/os proclib concatenation READ ONLINE: Control m user guide for z/os proclib concatenation 16 Feb 2019 This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all US Government Users Restricted Rights – Use, duplication. World #1 site for IBM Mainframe Computers with Support Forums, Free Downloads, IBM Manuals, Tutorials & Job openings since 1998. . CONTROL-M/Desktop User Guide describes the components used. 1-2 CONTROL-M Option for Oracle Applications Administrator Guide Overview. Applications production processing (for example, OS/390 jobs, Unix shell scripts) into a single, homogenous production environment. View and Download ADOBE PREMIERE PRO 2 manual online. PREMIERE PRO 2 Software pdf manual download. Adobe music mixer user manual (308 pages) Software Adobe 22011292 - Audition User Manual. Pc (390 pages). Or Control-M controllers installed on a given computer. Page 76 User Guide In the Device Control section of the Settings pane, specify.
It's been quite a while since I played with Control-M and I'm hoping someone knows the manual I'm looking for. We've got a tool which can translate our generic scheduling rules/jobs into inputs for OPC, CA-7, Jobtrac and a locally written mainframe scheduler. But I'm not able to remember how Control-M stuff can be created via 'batch' input (like CA-7). Or whether it's similar to Jobtrac, in that the schedule member contains all the relevant information.Does anyone know the manual where this is described? I've been going through the User manual and have found the KSL (which might be useful - and which I don't remember from 15 years ago).
But I guess I'm looking for info on the formats of the scheduling table and the job network file. Or should these never be updated directly, but via a batch process (similar to the load process in CA-7)? Possibly the afore-mentioned KSL?
Slight problem is this is all being done without access to a working Control-M facility, as I'm currently not on-site...
This appendix describes messages from external sources that are intercepted by the SMC.
IBM Operating System Messages
The messages listed in Table A-1 are received by the SMC. IBM message manuals describe the exact format (for example, spacing) and definition for each message. Ellipses indicate that the message contains more text than is shown.
Correct operation of the SMC depends on these messages. Do not suppress or alter them using products designed to handle messages through the subsystem interface (SSI). Many automated operations systems use the subsystem interface to intercept and alter or suppress messages.
Note:
If the 'suppressed by subsystem' and 'hardcopy only' bits are turned on in the WQE (the MVS write queue element) before the SMC has received the message, the SMC ignores the WTO, and the message is not displayed at the console.Control-m User Manual For Os 390 2
If you plan to use an automated operations system and are unsure about how it intercepts messages, contact the product vendor.
Although these messages may be suppressed (that is, prevented from displaying in the console) by using MPFLSTxx parameters or an MPF exit, the text of these messages should not be changed. The use of other WTO exits to change the display characteristics or the text of these messages is not supported by the SMC.
Control-m User Manual For Os 390 Free
Volume serial numbers ('ser') as specified in messages from the operating system, are defined as follows:
Messages that contain VOLSERs with more than six characters or any character except AZ, 09, # (crosshatch), $, ¥ (yen character), and optional trailing blanks are ignored by the SMC.
Table A-1 Intercepted Operating System Messages
| Message ID | Description |
|---|---|
IEC068A | U dddd,ser |
IEC101A | M dddd,ser,... |
IEC111E | D dddd,ser |
IEC114E | D dddd... |
IEC135A | U dddd,ser... |
IEC400A | M dddd, ser... |
IEC401A | F dddd,ser... |
IEC501A | M dddd,ser{,labtyp} |
IEC501E | M dddd,ser{,labtyp} |
IEC502E | n,dddd,ser... |
IEC509A | F dddd,ser... |
IEC512I | I/O ERR|LBL ERR|SEC VOL... |
IEC701D | M dddd, VOLUME TO BE LABELED ser |
IEC702I | dddd, VOLUME LABELS CANNOT BE VERIFIED |
IEC703I | dddd, VOLUME IS FILE PROTECTED |
IEF233A | M dddd,ser{,labtyp} |
IEF233D | M dddd,ser{,labtyp} |
IEF234E | {K|D|R} dddd{,ser...} |
IGF500I | SWAP dddd to eeee - OPERATOR|I/O ERROR |
IGF502E | PROCEED WITH SWAP OF dddd TO eeee |
IGF503I | ERROR ON dddd, SELECT NEW DEVICE |
IGF509I | SWAP ddd - OPERATOR|I/O ERROR |
IGF511A | WRONG VOLUME MOUNTED ON dddd, MOUNT ser,... |
IOS000I | MVS I/O error message processed only for specific Fault Symptom Codes generated by StorageTek tape devices |
TA0233D | Message for ASM2 |
JES3 Messages
The following JES3 messages are processed by the SMC:
IAT5210IAT5310IAT5410
IBM message manuals describe the exact format (for example, spacing) and definition of each message.
Tape Management System Messages
SMC processes messages from several tape management systems, including CA-1, CONTROL-M/Tape, and DFSMSrmm.
CA1 Messages
The following CA1 (TMS) messages are intercepted by the SMC. Refer to the Computer Associates publication CA-1 User Manual, Volume 1 for the exact format and meaning of each message.
CTS001CTS002CTS004CTS005CTS007CTS008CTS009CTS010CTS011CTS014CTS015CTT100ACTT101ACTT102ACTT103ACTT104ACTT105ATMS001TMS002TMS004TMS005TMS007TMS008TMS009TMS010TMS011TMS014TMS015IECTMS7CA$F810ACA$F813A
CONTROL-M/TAPE (formerly CONTROL-T) Messages
The following CONTROL-M/TAPE messages are intercepted by the SMC. Refer to BMC's INCONTROL for OS/390 and z/OS Message Manual for the exact format and meaning of each message.
CTT100ACTT101ACTT102ACTT103ACTT104ACTT105A
DFSMSrmm Messages
DFSMSrmm mount message (EDG6627A) must be acted on by the SMC when the volume or drive specified in the message is under the control of the SMC. The action of the SMC is similar to the SMC actions for the normal MVS mount messages (for example, IEC233A, etc).
The DFSMSrmm Tape Initialization program (EDGINERS) issues a series of messages describing the success or failure of tape initialization, erasure, and verification. These messages drives the dismount of the tapes mounted from the EDG6627A message. The following messages must be acted on by the SMC to dismount a tape:
Control-m User Manual For Os 390 Windows 10
Table A-2 Tape Management System Messages - DFSMSrmm
| Message ID | Description |
|---|---|
EDG6620I | VOLUME volser INITIALIZATION AND VERIFICATION SUCCESSFUL |
EDG6621E | VOLUME volser INITIALIZATION FAILED |
EDG6623I | VOLUME volser ERASE, INITIALIZATION AND VERIFICATION SUCCESSFUL |
EDG6624I | VOLUME volser ERASE FAILED |
EDG6627E | M dev VOLUME (volser) RACK (rack-number) TO BE action, lbltype |
EDG6642E | VOLUME volser LABELLED SUCCESSFULLY |
EDG6643E | VOLUME volser ERASED AND LABELLED SUCCESSFULLY |