On Thu, 14 Jul 2022 21:57:33 +0000, Seymour J Metz <[email protected]> wrote:
>The relevant statement is "Which component recognizes the '#' or the '15'x? >CP or VM (or XEDIT)?". > XEDIT can run in either line mode or full screen; in neither case is the CMS > command line relevant. When #CP is used from the line mode command line, the target is CP, not the guest. With a couple of exceptions, # characters are detected by the 3270 device driver and are converted to 0x15. Each line is then executed. The guest is never involved. So the DEFINE STORAGE and IPL succeed. Without the #CP, the data is split on # characters and each line is queued to the guest virtual console with an attention interrupt. CMS reads that data in puts each line in the CMS' internal console input buffer. On its way back to "idle" state, the CMS command processor reads the first buffered line and runs it. The DEFINE STORAGE command is passed to CP (SET IMPCP ON), causing the guest to be reset. The still-queued "IPL" command is never executed. (Note that # is really the current LINEND character according to the CP TERMINAL setting.) Within XEDIT, Fullscreen CMS, and other fullscreen applications, #CP is a programming construct implemented by the application. Fullscreen CMS sees the #CP and hands the entire line to CP via DIAG 8 after converting # to 0x15. XEDIT, on the other hand, has no special behavior for #CP. It simply breaks lines at the linend character and passes them to CMS if they aren't recognized (per SET IMPCPCMS). So what works in fullscreen CMS won't work the same way in XEDIT. Alan Altmark z/VM Consultant IBM Technology Services ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
