Hello Alan/All,

Initially I wanted to make the NJE TCP working with just a dynamic
commands. Once the dynamic command works I can update the JES deck.

Has anyone undergone this situation ?

Peter

On 23-Jan-2018 1:20 PM, "Alan(GMAIL)Watthey" <[email protected]> wrote:

> Peter,
>
> It's a while since I did this but I usually just copy/pasted whatever I
> had coded in the new startup options and added a few commas and issued it
> as a JES2 command.  You obviously need to add a $ADD or $T command as
> appropriate but I don't remember not being able to add anything new or
> change anything already there.  The $DEL command is a bit limited as some
> things cannot actually be deleted.  They just hang around until the next
> WARM start.  If I remember correctly the DESTIDs can be a bit of a pain as
> JES2 invents some of those itself so changing node names can run into them
> so you need to $DEL them first.  You might have to stop certain things
> before they can be changed but many can be changed whilst active.
>
> The JES2 manual is very good at telling you what can be changed with a
> HOT, WARM or COLD start.
>
> My next test was always a $PJES2,ABEND as that reads the new startup deck
> and tells me about any problems in it which I can quickly fix.  Do this at
> a quieter time obviously but I never got any complaints from anyone.  Some
> things won't work whilst JES2 is down (usually less than a minute for us)
> but these seem to be minimal and unimportant (perhaps TSO STATUS).
>
> The final test was the next IPL of course.
>
> Hope this helps.
>
> Regards,
> Alan Watthey
>
> -----Original Message-----
> From: Peter [mailto:[email protected]]
> Sent: 22 January 2018 6:00 pm
> Subject: Dynamic command to Activate NJE TCP
>
> Hello All,
>
> Cross Posted
>
> Is there anyone who have tried activating NJE TCP connections dynamically ?
>
> Any set of commands that can issued sequentially ?
>
> Could someone point me ?
>
> Peter
>
> ----------------------------------------------------------------------
> 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
>

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

Reply via email to