Scott, I'm paying attention to this one because it mentioned EE, by which I expect you mean Enterprise Extender. In fact mentioning Enterprise Extender is a "red herring".
If you are using Enterprise Extender, you are using an SNA session for your NJE and the fact you are using SNA - as opposed to other protocols for establishing the NJE connection - may be all that needs to be mentioned[1]. Actually I believe not even the fact of running over SNA may be relevant. Many years ago I ran my own test/education systems and, in order to have some variety in the SNA sessions supported, I used to set up sessions for NJE connections - although rarely used. However, I remember having to code checkpointing parameters for just this situation where a JES2 stream was broken mid-transfer. With such checkpointing arrangements, you can't actually expect to resume precisely[2] at the point of failure but from the previous checkpoint. Well, I decided to refresh my memory and indeed it seems there are CKPTLINE, CKPTPAGE and CKPTSEC parameters to the used for streams to printers (and punches). However, I'm not a JES2 specialist so I can't be sure these parameters will satisfy your requirements. What I am fairly sure about is that the protocol underlying the NJE connection will generally not affect the JES2 functions supported. Finally and perhaps rather obscurely, thanks for pointing me to the z/OS V1R7 JES2 bookshelf. There used to be a very interesting manual from the Washington Systems Center which was, in effect, an architecture manual for NJE. I see that this manual, perhaps because of the adoption of TCP as an additional transport in z/OS V1R7, has become a "regular" manual and is now included on the JES2 bookshelf. It is "z/OS V1R7.0 Network Job Entry Formats and Protocols". The fact that the "z/OS V1R7.0" should really *not* be part of the title is indicated by the existence of Appendix A, "System-Dependent Considerations" which covers all of JES2, JES3, RSCS and VSE/POWER. I Googled in order to find a reference to the old WSC manual. It is "Washington Systems Center Technical Bulletin Network Job Entry Formats and Protocols for System/370 Program Products GG22-9373 June 1986 ". Chris Mason [1] With z/OS V1R7 NJE connections are possible over TCP so you could take SNA and Enterprise Extender out of the jumble of protocols. [2] Actually there are some SNA techniques used by IMS and maybe CICS where it is possible to restart just about precisely at the point of failure[3] but I don't think NJE uses them. [3] If you spot "Set and Test Sequence Numbers" in the documents you know this is the sort of restart being discussed. ----- Original Message ----- From: "Scott Doherty" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Thursday, 08 June, 2006 1:59 PM Subject: NJE EE Restart > If you have a NJE connection established via EE and the connection > is terminated for some reason can the sysout being transmitted be > restarted at the point of failure or does it have to restarted > from the beginning. The JES2-L seems to be dead for quite some time > and I could not find anything substantial in the archives or docs so far. > > Scott ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
