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 universal access
authority, and an ADDMEM value. The profile name is a three-part identifier
that indicates the origin of the work and the type of security information
you want to validate. The universal access authority determines the actions
that RACF performs on the inbound work.

Best wishes
Jack


On Wed, 15 Nov 2023 at 15:46, Tom Longfellow <
[email protected]> wrote:

> 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 resiliency and
> reliability they all act as store and forward nodes in the NJE network.
> We wish to no longer communicate with one of these nodes.   Every method I
> use simply causes the NJE link to switch over to another mainframe in the
> interconnected network.
> $P $E $I commands at best cause failoever to another NJE node as the
> middle man.   Killing the SNA CDRSC just causes failover as well.
> We have found nothing I can do to the NODE, LINE, or APPL that allow me to
> make this node dead to us.
>
> I am trying to do this gracefully by turning it off before modifying JES
> parms to remove it from my startup.  Trying to preseve the possiblility of
> fallback in case some stealth user pops out from behind the woodshed.
>
> Any suggestions?
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to