Do you get a "reconnected message" ? If so, lots of PF3s and logoff ... then start again
On Fri, 8 Nov 2024 at 17:53, Farley, Peter < 0000031df298a9da-dmarc-requ...@listserv.ua.edu> wrote: > I am asking this question here because the ISPF-L list has been pretty > dormant for a while now. > > We have an old ISPF application which does NOT have a callable API of any > kind that I need to be able to automate for a targeted list of "screen" > actions. > > Aside from coding a VBS screen "macro" application using (for instance) > the IBM PCOMM VBS interface (which I have done previously, but which is > tediously tricky to cover "all the possible errors and recovery steps"), is > there any way a BATCH program (Rexx or other language) can interact with > such a system? > > It needs to be something that can be run from a batch job (or Unix > services shell script if needed) as part of a larger automation project. > > I have been investigating the python "tnz" package for 3270 scripting, but > haven't yet had the chance to try to run it under z/OS Unix services. One > "gotcha" I found running a testing script using the "tnz" package from the > PC side is that if your normal LOGON process keeps the "RECONNECT" switch > set and you aren't currently logged off from any real 3270 session, then > the 3270 script "takes over" your prior session, which then totally > bollixes up the script because it doesn't know where it is. We don't have > our TSO logon's enabled for multiple logon to the same LPAR, we are still > strictly one logon at any time and only one TSO userid per user. > > So if there was any way to script an ISPF "screen-only" application from a > batch job that would be a much better solution. > > If anyone knows of any way to handle such a project besides 3270 > scripting, please let me know. > > Peter > > This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. > If the reader of the message is not the intended recipient or an authorized > representative of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, please notify us immediately by > e-mail and delete the message and any attachments from your system. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
