Thanks. I got BPXMTEXT working, added to SYSPROC. But first I invoked it the
hard way, via:
TSO EXEC 'SYS1.SBPXEXEC(BPXMTEXT)' '7663730C'
I was confused: never having seen the output, and not knowing what caused
7663730C, the output:
TCPIP
JRNetAccessDenied: The user is not permitted to communic
Classification: Confidential
Try "TSO BPXMTEXT 7663730C"
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Lennie Dymoke-Bradshaw
Sent: Saturday, February 3, 2024 11:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Where are Unix reason codes over 7371
Maybe i'm wrong, did you actually try TSO BPXMTEXT ?
Best Regards
Ituriel do Nascimento Neto
z/OS System Programmer
Em domingo, 4 de fevereiro de 2024 às 17:10:16 BRT, Mark Jacobs
<0224d287a4b1-dmarc-requ...@listserv.ua.edu> escreveu:
BPXMTEXT is shipped in SYS1.SBPXEXE
BPXMTEXT is shipped in SYS1.SBPXEXEC and must be in SYSEXEC or SYSPROC to use.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com
On Sunday, February 4th, 2024 at 3:06 PM, Phil Smith II
Colin Paice wrote:
>tso command bpxmtext 7663730c
I get:
COMMAND BPXMTEXT NOT FOUND
?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
RE: decoding UNIX reason codes. It's a bit of a mess. You need to carefully
read Chapter 3 "Description and location information".
Eventually you fall through and find the errno2:
730C
JRNetAccessDenied The user is not permitted to communicate with the specified
network. Action: If access to
I think I remember someone that started this thread there was a S913 violation
error.
Was that violation cured?
Sent from my iPhone
No one said I could type with one thumb
> On Feb 3, 2024, at 17:37, Charles Mills wrote:
>
> It's confusing. The last four nibbles, 730C, are the "real" rea
It's confusing. The last four nibbles, 730C, are the "real" reason code. Just
scroll down in here:
https://www.ibm.com/docs/en/zos/2.5.0?topic=errnojrs-zos-unix-reason-codes
As the first part of the section says
The reason code is made up of 4 bytes in the following format:
Have you tried SU command?
Sent from my iPhone
No one said I could type with one thumb
> On Feb 3, 2024, at 11:37, Colin Paice wrote:
>
> tso command bpxmtext 7663730c
> JRNetAccessDenied: The user is not permitted to communicate with the
> specified network.
> Action: If access to the spec
tso command bpxmtext 7663730c
JRNetAccessDenied: The user is not permitted to communicate with the
specified network.
Action: If access to the specified network is required, the user must be
permitted to the appropriate SAF resource
On Sat, 3 Feb 2024 at 17:13, Lennie Dymoke-Bradshaw <
032fff
I am trying to debug a situation in zSecure where I am getting this message
from the CKNSERVR address space.
CKN017I 12 BPX1AIO connect failed on socket 1 RC 111 permission denied,
reason 7663 730Cx
Port 7173 of 192.168.11.100
BPX1AIO documents that its return and reas
11 matches
Mail list logo
