This was definitely about 3800 device support. Historically JES2 had
controlled a slew of peripheral devices: printers, punches, TP, RJE, NJE.
The code to handle I/O to these devices was included in JES2 modules. The
3800 was a logical candidate but a most unfortunate one. The 3800 was far
more complex than any devices previously managed. As a brand new device, it
was also undergoing development and refinement. Every quirk and tweak had
to be handled by JES2 code. It was a quagmire.

As a consequence of that experience, FSS was born. From that point forward,
device support was externalized via a standard interface so that JES2 code
would never again have to confront the innards and foibles of new hardware.
In the interim, customers who suffered unstable JES2 would run a secondary
JES2 to take the hit for 3800 hiccups.

.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[EMAIL PROTECTED]


                                                                           
             Ed Gould                                                      
             <[EMAIL PROTECTED]                                             
             AST.NET>                                                   To 
             Sent by: IBM              [email protected]                
             Mainframe                                                  cc 
             Discussion List                                               
             <[EMAIL PROTECTED]                                     Subject 
             .EDU>                     Re: embarressing SDSF question.     
                                                                           
                                                                           
             10/17/2007 02:17                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
               IBM Mainframe                                               
              Discussion List                                              
             <[EMAIL PROTECTED]                                             
                   .EDU>                                                   
                                                                           
                                                                           




On Oct 17, 2007, at 1:22 PM, Skip Robinson wrote:

> Running a secondary JES2 to support printing is a venerable
> tradition. Back
> in the day when 3800 printers first came out, the device support
> embedded
> in JES code was flaky. Keeping the subsystem running was a nightmare.
> Hardware problems--or software problems that failed to handle the
> hardware
> properly--caused frequent JES2 abends. In my shop we ran a
> secondary JES2
> solely for the purpose of managing the 3800s. When that JES2 went
> down, the
> rest of the world was sheltered from the disruption. It was years
> before we
> felt confident to revert to a single JES2.
>


Skip,

That is interesting as we were early ship for PSF and we had our
hands full with PSF PTF's but, I don't recall of a single JES2 issue
(my memory is fair in this area) I was on the phone daily with the
PSF level 2 people and we got to know each other pretty well. So I
think I would have remembered any JES2 issues or are you talking pre
PSF?

Ed

----------------------------------------------------------------------
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

Reply via email to