Hello Marc,Hello Patrick
thanks for providing some help!Welcome, happy to help you.
apologies accepted :-)
Am 18.07.2022 um 23:16 schrieb Marc Rauzier <marc.rauzier@xxxxxxxxx>:
If I remember fine, PPP session is running in a batch job with QTCP user profile. Maybe this is the same with SLIP.Yap. Thanks for this nudge in the right direction.
Is there a batch job starting at the same time which could be related to the SLIP session?It was, indeed!
Maybe with the name of the dial profile? Maybe the authority issue happens within this job and is reported in your joblog?Assuming there isn't a huge chain of programs calling each other, this sounds reasonable.
You're right. My apology is: It was already late in the evening. ;-)Adding QSECOFR with *ALL authority to QSYS/QTOCPPSM did not change the behavior.Normally, no need to do so as QSECOFR has *ALLOBJ special authority. And the same applies with owner authority adoption. It is not used with an *ALLOBJ user profile.
I did and the behavior changed fundamentally. 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?Any ideas?What is the authority for other user profiles on that object? If needed, could it be possible to change it so that *PUBLIC can use the object?
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.
Looking at the old BOOK format documentation about TCP/IP for V3R6 explains how to set up point to point links via OpNav. Wasn't OpNav relying on communication over TCP ports? Sounds recursive to me.
However, thank you *very* much for your help. In the end, I got it to work!
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.59.100.1, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 140/145/152 ms
I'll document the necessary steps (as usual) on try-as400.pocnet.net, if any fellow hobbyist also wants to use TCP/IP on V3, over a serial connection (because no LAN).
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.