David Devine wrote: >Different strokes for different folks. Does any one really use native tso >these days for file manipulation? how retro :-)
How retro? Hmmm, did you ever need to recover back to that native TSO (READY prompt plus boring three stars) to resolve something unpleasant? In ancient days, while practising Ancient Art of Computing during MVS/ESA days, I have been there, done that, because that CLIST library with the correct logon CLIST was not available due some secondhand asshole varied the volser OFF via Hardware Config setup. I could logon, well sort of, using alternative logon CLIST, but the CLIST stopped at one statement. (last one which was an ALLOC thing) I redo that ALLOC statement and then redo a ISPF command for starting my ISPF panels. All tedious typing from a hardcopy printouts (shame you tree-killers!) of that CLIST. Once in ISPF, I could change the logon CLIST and have someone else to test it out. Big fun while the whole planet was waiting... ;-) Oh, the person who did that Hardware Config was of course out of city for added exciting fun. ;-/ Since that fun, we have a few emergency logon procs to avoid above painful stunts and tricks and drama... >Yep, practically anything that's poorly coded. Ever forget to initialise a >variable? or delstack? results not always as designed! :-) Shhhhhhhhhhhhhhhhh! You will awake debug demons. ;-) >> Can contention occur within a single address space? >With poorly written code or implementation? been there so i wouldn't be >suprised, hence "sneaky feeling" :-) Suprised? Thats a new fun word ;-) Some products can only be used in one ISPF panel, not on both or more ISPF panels, due to bad design or allocation methods. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
