Re: Console Address Space
The Console Address Space cannot be restarted. Peter Fatzinger z/OS Core Design & Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Whether MSGFLD handle IOS050I,SUP(NO) in MPFLST.
During normal activity the processing of the IOS050I message will be governed by the MPFLSTxx setting which in your case means it will not be suppressed. If Message Flood Automation detects that the IOS050I is part of a flood then the MSGLFDxx settings will take effect - in your case the message would be deleted. Peter Fatzinger z/OS Core Design & Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: MDB (message data block)
Pierre, You can probably accept the text objects in the order you find them because as you note, you don't really have other options. However, you probably shouldn't make assumptions regarding the other objects. In SYS1.SAMPLIB you can find an example of processing MDBs. IEAMDBLG reads MDBs from the log stream and converts the messages into SYSLOG format. You can see that it first finds and extracts information from the general and control program objects and then goes back to the beginning to look for the text objects. Peter Fatzinger z/OS Core Design & Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: MVS PURGE command
As noted, the PURGE command was related to the 3850. The code backing the command was eventually removed from the product in z/OS 1.11 which is why you now get the IEE305I message. I was unaware of the table in the SDSF book. I'll work with the publications team to get the discrepancies corrected. Peter Fatzinger IBM z/OS Core Design and Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: direct z/OS operator command output to SYSLOG only?
John, Glad you found the problem. The reason you couldn't find the MASTER console is because the concept of the MASTER console went away somewhere around z/OS 1.8. Since then issuing an internal DISPLAY command without the L= would normally cause the command response to go to the hardcopy log as well as any operator console with INTIDS=Y unless the command processor did additional checking to not allow it. Peter Fatzinger IBM z/OS Core Technologies Design & Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: APAR OA56180 / RUCSA
Mark, The 1M increment for RUCSA storage was not chosen haphazardly. We understand the scarcity of below-the-line memory, but in order to provide the isolation needed to adequately protect the area we couldn't use any increment smaller than 1M. Also, in case anyone is unaware, beginning in z/OS V2R4 RUCSA is a separately ordered paid feature. Peter Fatzinger z/OS Core Technologies Development and Service -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Documentation error z/os 2.3
Joseph, Thank you for noting the error in the documentation. The EXECUTABLE= keyword has not been implemented on the IARST64 macro. It is available on the STORAGE and IARV64 REQUEST=GETSTOR macros. I will work with the publication team to remove the extraneous information. You can communicate directly with that team via mhvr...@us.ibm.com when you find issues with the documentation. If you would like to be able to obtain non-executable 64-bit storage via the IARST64 macro please submit an RFE with that request. Thanks, Peter Fatzinger IBM z/OS Core Technologies Design & Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How long may a console command be?
Charles, - No, most commands will not accept format 2 syntax. If the documentation for a command does not explicitly state that the newer format is acceptable it should be assumed that it is not valid for that command. - The maximum command length is 126 regardless of the format. Peter Fatzinger z/OS Core Technologies Design and Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: descriptor code for iplcheck
Jason, IBM ships IEAMDBLG in SYS1.SAMPLIB as an example of how to extract records from the operations log logstream and convert them into SYSLOG format. You can see how it gets to the MDBCDESC (defined in macro IEAVM105) field and uses it to determine if the message is a command response. Peter Fatzinger z/OS Core Technologies Design and Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEE042I in OPERLOG - why no century?
Tim, Yes, it's working as designed. The IEE042I message is built in the System Log Initialization module and bypasses much of normal WTO processing. It builds the year based on the HCFORMAT setting in CONSOLxx to try to be consistent. I expect it looks like the other messages when looking at SYSLOG. Specifying CENTURY should give you a consistent format in both logs. Peter Fatzinger z/OS Core Technologies Development and Service -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEARELCN for orphaned console definitions
Bob, You can run IEARELCN on any system in the sysplex. The service essentially allows the Consoles component to forget that there ever was a console with that name. There is no longer any association between that console name and any device on any of your systems (as indicated by the D C response). I would recommend moving to distributed mode at your earliest convenience. Peter Fatzinger z/OS Core Design & Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Console messages which has precedence and related questions
Hi Michael, A message will be delivered to all receivers whose attributes match those of the message. When you retrieve a message via MCSOPMSG you can make no assumptions about whether the message has or hasn't been delivered to any other recipient. A DOM can potentially keep a message from being displayed on an MCS console, but in the scenario you describe it's highly unlikely to happen quick enough. You cannot obtain a specific message id via MCSOPMSG. It is recommended that you limit the routing attributes of the EMCS console to the bare minimum required. If you are using it to issue a command and receive a response then give the EMCS console no routing attributes and use the CART on the MGCRE and MCSOPMSG. If you need to monitor for a wider range of messages then give the EMCS console only those routing attributes needed, and limit the amount of processing done on the unneeded messages obtained via MCSOPMSG. The message dataspace will be created in the console address space and will be shared by all EMCS consoles activated in your address space. Peter Fatzinger z/OS Core Components Development and Service -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RES: Console status after IEARELCN
Skip, To answer your original question, No, prior to v2r1 (and being in distributed mode) there is no way to add an MCS console without an IPL. I also don't know of any system command that will show you that a console device is pinned. Note that any device you've specified in CONSOLxx as a console will be pinned. Peter Fatzinger z/OS Core Components Development and Service -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: VARY OFFLINE fat finger
There have been requests for IBM to provide a confirmation prompt or a limit on the range, but they've always been rejected because, as several have indicated, an exit can be written to meet the installation's specific requirements. Given that alternative we haven't been able to justify the cost of implementing a solution within the BCP. Peter Fatzinger z/OS Core Components Development and Service -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEE313I when varying a console online
System command D C,U=xxx will show you if console services believes there is a console defined for that device. There's also a Redbook for the 2074 (http://www.redbooks.ibm.com/abstracts/sg245966.html) which may help. Peter Fatzinger -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: exit add in progxx for cnz_wtomdbexit and setprog
Bernard, MVS Installation Exits definitely says that you should be able to add the exit via PROGxx, and you have collected ample evidence that it is not working correctly for you. I believe last week you had indicated you were considering opening a PMR, and I would say that is the correct course of action. I'm also passing along my findings to the Poughkeepsie consoles level 2 team so they can watch for the PMR. Peter Fatzinger z/OS BCP Core Technologies Design Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEZVX100 field CTXTHABD (for ieavxmit)
Bernard, The bit would most likely be set for a message that has been displayed on some console/device, and is now going through normal WTO processing to insure it gets sent to the hardcopy log. Two examples of messages that may have this bit set would be messages that were issued during NIP, or synchronous messages. An explanation of synchronous messages can be found in MVS Planning: Operations. Peter Fatzinger z/OS Core Components Development and Service -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
