<snip> I would suggest using a reusable LX and then make sure the caller can locate the sequence number as easily as the PC number(s) </snip>
If you're likely to restart and re-connect, there is little benefit to a reusable System LX (this is unlike the case for a non-system LX for which there is significant benefit to using a reusable LX). It is true that if you do use a reusable system LX, then you would go through the entire process on restart, starting with LXRES. You would not "re-connect". The Share presentation contained this: <snip> If the server terminates and restarts, it would issue AXSET for the new space and re-issue ETCON (and thus must make sure that the TKLIST and ELXLIST areas are accessible). It would not re-issue LXRES. </snip> Note that ETCRE is not mentioned (and it refers to the TKLIST, presumably with data from the ETCRE done the first time). I had told someone very recently that you don't need to do the ETCRE on restart for a system LX that was re-connecting to an LX. I was wrong. On restart, you would do both ETCRE and ETCON; for a non-reusable LX you would not have done (another) LXRES but would have used the information from the initial LXRES (and the new ETCRE) when doing the ETCON. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
