You're right. My apology is: It was already late in the evening. ;-)apologies accepted :-)
But the most interesting question is: Why did IBM ship the *PGM with *PUBLIC *EXCLUDE? Am I supposed to change this? Is there another, "correct" way?This is a good question and I do not have the answer. However
You can try to set back *EXCLUDE for *PUBLIC and add *USE for QTCP for your SLIP setup to work.
I do not find any information about an APAR or a fix for that issue, but I can only guess that a PTF was provided in the past.
You can find this book here ftp://ftp.www.ibm.com/systems/power/docs/systemi/v5r3/en_US/sc415336.pdf.
Not related to V3R2 but it might apply the same way.
Not sure to understand what you mean with "recursive".
On those versions, it was possible to use both TCP/IP and SNA communications for OpNav.
But in any case, there is still a login with a valid user profile which will run all the actions driven by the OpNav interface, with related authority.
Whatever the way you use to configure SLIP (OpNav or 5250 commands), the batch job handling the SLIP session will run with QTCP user profile.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.