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
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
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
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
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
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
: 15 November 2023 15:46
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: The JES2 NJE node that cannot die.
I have been in this business for decades and have run in to this situation on a
few occaisions. Never really came up with the right recipe to make this
happen.
Our JES2 systems are NJE
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
131-dmarc-requ...@listserv.ua.edu>
Sent: Wednesday, November 15, 2023 10:45 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: The JES2 NJE node that cannot die.
I have been in this business for decades and have run in to this situation on a
few occaisions. Never really came up with the right recipe t
I have been in this business for decades and have run in to this situation on a
few occaisions. Never really came up with the right recipe to make this
happen.
Our JES2 systems are NJE interconnected over SNA links interconnected with
several other mainframes at other agencies. For
10 matches
Mail list logo
