Re: The JES2 NJE node that cannot die.

2023-11-27 Thread Tom Longfellow
For those of you with any interest at all.The wicked witch (NJE node) is now dead to me The guardian angel keeping it on life support must have given up.Without any further actions on my part, it was suddenly gone. Wild theories exist: my guardian angel was discovered that I was

Re: The JES2 NJE node that cannot die.

2023-11-16 Thread Tom Longfellow
Here is my second failed attempt using what I think I learned from Brian. >"First you need to (in vtam via V NET,INACT,ID=) inactivate any cross domain >and CDRSC connections between that LPAR and everyone else, then you need to >(in JES) using the >TSOCKET(name) command change it to

Re: The JES2 NJE node that cannot die.

2023-11-16 Thread Tom Longfellow
I have already gone the VTAM Inact route but I have not tried it for EVERYONE. If I do temporarily kick everyone to the curb so that the dead node can be deleted, I have yet to find a JES command to delete a node. Best guess at this point, using your theory is to: Shut all JES2

Re: The JES2 NJE node that cannot die.

2023-11-16 Thread Tom Longfellow
Thanks, While that might shutdown the node, My eventual goal to is remove it entirely. I am trying to do it in stages. First, deactivate it. Wait. Then Remove it. I see no need to apply external solutions (RACF) to the procedure. My experience and monitoring tells me that this node

Re: The JES2 NJE node that cannot die.

2023-11-16 Thread Tom Longfellow
Nice idea. The only CONNECT statements I have are for NJE over IP.I am not sure how to apply this to an SNA connection. I -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: The JES2 NJE node that cannot die.

2023-11-15 Thread Brian Westerman
There are several steps, First you need to (in vtam via V NET,INACT,ID=) inactivate any cross domain and CDRSC connections between that LPAR and everyone else, then you need to (in JES) using the TSOCKET(name) command change it to connect=no. From that point on, the physical connections just

Re: The JES2 NJE node that cannot die.

2023-11-15 Thread Lennie Dymoke-Bradshaw
I think you need to set up your RACF NODES profiles and set the node in question to UNTRUSTED. Lennie Dymoke-Bradshaw https://rsclweb.com ‘Dance like no one is watching. Encrypt like everyone is.’ -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Longfellow

Re: The JES2 NJE node that cannot die.

2023-11-15 Thread Jack Zukt
Hi, You could try using RACF to prevent the node being used. >From the RACF Administrator's Guide: You can use profiles in the NODES class to control how RACF® validates inbound work on an NJE network. As with other RACF profiles, a NODES profile consists of a profile name, a profile class, a

Re: The JES2 NJE node that cannot die.

2023-11-15 Thread Art Zeigler
Have you looked at this webpage on deleting JES network connections - https://www.ibm.com/docs/en/zos/3.1.0?topic=section-del-connect-delete-network-connections Art Zeigler From: IBM Mainframe Discussion List on behalf of Tom Longfellow