Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- H390-Vm
- Messages
Search
|
Re: Sending command output to the stack in VM/370
adriansutherland67
I would be very interested in trying to help beta test BREXX/370 for VM/370 The MVS folks already sent me a link to your github page. I also believe that I have a link to your docker image of sixpack. Do you have a zip of something that I can run in a fully virtualized KVM guest? I have not yet tackled docker. and I do not know if I have the time or skill to tackle installing your BREXX on top of one of my existing sixpack instances running on CENTOS 7 FYI, I started in Main Frame operations in 1981 and have been programming in REXX since 1993. I did a lot of work in the OS/2 days of the 1990s. Since 1999, I have primarily been a GNU/Linux guy (as mentioned above) I briefly taught REXX to undergrads on VM/SP in 1994. Many of my REXXies are now running in CGI. I decided not to learn MS Visual Basic after OS/2 bit the dust. Regards, Larry |
|
Re: Sending command output to the stack in VM/370
On Sun, Sep 6, 2020 at 07:37 PM, Larry Schacher wrote:
IBM's SAA strategy. I may be dating myself here.SAA is long defunct - in fact I have had conversations with IBMers who clearly blinked and missed it - it appeared and then disappeared. I think OS/2 was the closest implementation but it all got bogged down with issues of how to create something new without cannibalising the old. An old story ... I was recently called upon to try to help beta test the newest BREXX/370 for MVS 3.8JPlease do let me know if you would be interested in testing BREXX/370 for VM/370 - sadly a big fork from MVS guys - but I understand MVS not! A |
|
Re: Sending command output to the stack in VM/370
It is obvious that IBM (or indeed anyone who cared to) could implement the ANSI REXX stuff on CMS using the CMS PIPES infrastructure.
However my understanding is that IBM is no longer investing in REXX (or indeed CMS?) so presumably IBM will indeed never implement it on later versions of CMS, But to be practical, to implement it on VM/370 someone would need to develop a MOD so that console output could be redirected. It is not obvious to me how this could be done in a way that would be compatible with anything IBM did (not that I care about that). The question is how did IBM do it for CMS PIPES, and can that be duplicated? The answer is probably - "wont fix" :-) |
|
Re: Sending command output to the stack in VM/370
Thanks again to all for the insights.
I certainly think that it is worth while for all current IBM implementations of REXX to be ANSI compliant as that seems to me to be the purpose of the standard. I have not been actively involved with current IBM operating systems for quite a while now. The last I heard, quite a while ago, REXX was part of IBM's SAA strategy. I may be dating myself here. I fairly recently stumbled onto to Hercules and Its various public domain and free operating systems as a hobby and very much enjoy all of the work being done by this wonderful community. I was recently called upon to try to help beta test the newest BREXX/370 for MVS 3.8J Most of my current work is being done on GNU/Linux with ANSI standard REXX Interpreters. I will look for every opportunity, including this forum, to promote the ANSI standard for the REXX language. Warmest regards, Larry S |
|
Re: Sending command output to the stack in VM/370
I am also only interested in providing a version of REXX that is completely compatible with REXX provided in later IBM VM releases. On Sun, Sep 6, 2020, 2:57 PM Dave Wade <dave.g4ugm@...> wrote: I assume it possible, but to me it seems silly to add things that don't work on later versions of CMS. |
|
Re: Sending command output to the stack in VM/370
I assume it possible, but to me it seems silly to add things that don't work on later versions of CMS.
toggle quoted message
Show quoted text
If you really want I think you should investigate getting IBM to add it to the current CMS via Share Dave On Sun, Sep 6, 2020 at 05:20 PM, Larry Schacher wrote:
|
|
Re: Sending command output to the stack in VM/370
Here is a link to the ANSI standard document for REXX (Language level 5)
Here is a link to the REGINA REXX documentation The ADDRESS instruction documentation for REGINA begins on page 25 of that document. As far as I know, REGINA was the first ANSI compliant REXX. Here is an example quote? from the REGINA doc above. ADDRESS SYSTEM "sort" WITH INPUT STEM names. OUTPUT STEM names. The first command instructs the default command line interpreter to call the program called sort. The input for the command is read from the stem names. (note the trailing period) and the output is sent back to the same stem variable after the command terminates. |
|
Re: Sending command output to the stack in VM/370
What are those additions? Bob Bolch On Sun, Sep 6, 2020 at 12:20 PM Larry Schacher <larryschacher@...> wrote: Thanks for all of the insights. |
|
Re: Sending command output to the stack in VM/370
Thanks for all of the insights.
Is there any possibility of adding the ANSI standard additions to the ADDRESS instruction in the BREXX (or any other REXX) for VM/370 to retrieve command output? I personally believe this to be a valuable addition. My background is Operations and ops support (more on MVS then VM) so this would be beyond my current skill set. |
|
Re: Sending command output to the stack in VM/370
To emphasize Dave's point, it is only the QUERY command (that I can think of)? that can stack its output. There is not a general stacking interface. However, the original EXEC processor (with the &BEGSTACK?and &STACK?statements) and the BREXX processor (using the REXX push and queue statements) can make use of the stack. Some frequently?used Sixpack utilities, like EXECUTIL, also use the stack. I plan to make MAKEBUF, DROPBUF, and SENTRIES commands available soon to facilitate more robust use of the stack in REXX applications. Bob Bolch ? |
|
Re: Sending command output to the stack in VM/370
¿ªÔÆÌåÓýI was just going to say that as far as I know its up to the individual commands to interpret options. There is no ¡°universal¡± support for and even on modern CMS some commands may not support it. ? Dave G4UGM ? From: [email protected] <[email protected]> On Behalf Of Bob Bolch
Sent: 06 September 2020 16:49 To: [email protected] Subject: Re: [h390-vm] Sending command output to the stack in VM/370 ? The VM/370 Sixpack has modifications to support the STACK option on CMS QUERY commands. I don't know your test method, but if you are doing this: ? q blip(stack ? ? ? ? ? ? ? ? ? the Unknown CP/CMS command response is caused because CMS tries to execute the next command, and seeing a stacked?line of input, tries to execute the stacked line "BLIP ? ? = OFF" as a command.? ?? You need to retrieve the stacked line, in an EXEC for example, so CMS won't see it.? ?? ? On Sun, Sep 6, 2020 at 10:31 AM Larry Schacher <larryschacher@...> wrote:
|
|
Re: Sending command output to the stack in VM/370
BREXX (like Regina) for non-mainframe platforms emulated the STACK. Moreover they could use the standard ability to redirect stdin/out/err to provide piping between commands (some implementations more sophisticated than others - but conceptually you can imaging plumbing for redirecting stdout to a file, and reading in that file to STEM variables, for example).
VM/370 has no ability to redirect output (well so far as I am aware). Maybe that was done in VM/SP, or later? CMS PIPES and all that ... In any case, the implementations of BREXX on VM/370 don't do anything. If a command, like "QUERY DISK (STACK" happens to put its output on the stack - great - but nothing to do with BREXX itself. Does that help? A? ? |
|
Re: Sending command output to the stack in VM/370
The VM/370 Sixpack has modifications to support the STACK option on CMS QUERY commands. I don't know your test method, but if you are doing this: q blip(stack ? ? ? ? ? ? ? ? Ready; T=0.01/0.01 11:43:05 Unknown CP/CMS command? ? ?? the Unknown CP/CMS command response is caused because CMS tries to execute the next command, and seeing a stacked?line of input, tries to execute the stacked line "BLIP ? ? = OFF" as a command.? ?? You need to retrieve the stacked line, in an EXEC for example, so CMS won't see it.? ?? On Sun, Sep 6, 2020 at 10:31 AM Larry Schacher <larryschacher@...> wrote: I have a question about VM/370. VM/SP supports sending command output to the stack. BREXX uses the VM method for doing this. ADDRESS COMMAND "QUERY DISK A (STACK" The standard BREXX doc is located at . This method works fine in BREXX 2.1 for PC DOS 'DIR (STACK' I came across this while beta testing BREXX/370 for MVS. Does anyone know if sending command output to the stack is supposed to work on VM/370? I get Unknown CP/CMS command when trying. |
|
Sending command output to the stack in VM/370
I have a question about VM/370. VM/SP supports sending command output to the stack. BREXX uses the VM method for doing this. ADDRESS COMMAND "QUERY DISK A (STACK" The standard BREXX doc is located at . This method works fine in BREXX 2.1 for PC DOS 'DIR (STACK' I came across this while beta testing BREXX/370 for MVS. Does anyone know if sending command output to the stack is supposed to work on VM/370? I get Unknown CP/CMS command when trying.
|
|
Re: CMS updates for Nucleus Extenstions and CMS Subcommands
Adrian and I are currently testing an EXECCOMM subcommand interface into BREXX, built for CMS with HRC404DS in place. I am testing a full function EXECIO?command?built to match the early VM documentation of the command. It is going to take a lot of testing because of all the options and combination of options you can use.? Bob Bolch On Sat, Aug 29, 2020 at 8:24 AM Peter Coghlan <groups@...> wrote: > |
|
Re: CMS updates for Nucleus Extenstions and CMS Subcommands
Thank you for taking on this CMS stuff. I just seem to sink into quicksand every time I go near CMS. I get confused about how many times I have been through the SVC 202 interface :-( A valid assumption. Great - thanks! Years ago, I was looking for a CP modification to get a 7171 to drop the line on logoff or disconnect when I ran into the BLOCKTAP roadblock. I never got around to finding a way past it until now. I wrote an EXECCOMM interface for the EXEC processor (because some package I was trying to build needed it). I added the EXECCOMM command into the CMS command table in DMSFNC as a quick hack to make this work. Now I can change it to register EXECCOMM properly using SUBCOM. I just need to figure out where to make the SUBCOM call from. Regards, Peter Coghlan. |
|
Re: CMS updates for Nucleus Extenstions and CMS Subcommands
Thank you Peter. My updates do assume that the Sixpack updates are already supplied. You are right that the NUCXDROP?ABEND is too harsh. I'll provide an update to issue a message and error return code. Being able to use BLOCKTAP is so great!! Those old tapes have some support?neat? stuff. I even found?an old set of code for the 7171 on there, that I wrote long ago. So many tools from the old days are there, that I have not had time to look at them all yet. Bob Bob On Fri, Aug 28, 2020 at 10:20 AM Peter Coghlan <groups@...> wrote: This is great work Bob - well done and many thanks. |
to navigate to use esc to dismiss