-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EXECIO Does Not Process Multiple Uses of STEM Correctly #80
Comments
EXECIO is on the MAINT 093 minidisk, as DMSXIO ASSEMBLE, and is part of VM/370 CE. The reason the problem occurs is that the right parenthesis used ')' for example in the following:
Is consumed by the STRING parameter and passed to CP, causing an error. Therefor the solution is to NOT use the right parenthesis. Hence, the following code works as is needed.
|
')' character included in the string which was issued as a CP command caused the command failure. IBM deocuments that the trailing ')' should not be included when an EXECIO is issued with the STRING option. |
I think I found a bug in EXECIO when using the STEM option. When I use the same variable to catch the CP output, it works the first time, but not after that. I have tried initializing the stem variable each time I use it, and not initializing it. Neither helps. Remove CPinfo. = '' from the EXEC, found at the bottom, to see for yourself. The following is the output of performing this task manually. Hence I don't use the STEM option., but I do get CP output.
The following is the output from PARS EXEC, which is at the bottom of this missive. The stem variable, CPinfo. , only contains results the first time. Hence, I don't catch a spool ID for the closed console file.
Another odd thing, is that the console spool file seems vanish upon closing. I tried a manual STOP CLOSE, and still nothing.
If the spool ID were to show up, then I could process the file.
Below is the EXEC. It's longer than it would be if everything was working correctly. I have tried to be consistent in usage and catch all the information I could.
Finally, does anyone know if the EXECIO source code is kept on CE V1R1M1, and where? If not, I can always go yank it off the 'net.
... Mark S.
The text was updated successfully, but these errors were encountered: