There's not much experience you can learn by using an emulated SYSG. For humans a real SYSG is entirely different from an emulated one. - a SYSG emulated on a PCOMM session still looks like PCOMM, with your PCOMM keyboard definitions, but without file transfer or GDDM. - a real SYSG has its own keyboard layout. So, I don't see any end-user use for TERM SYS3270 ON.
And, no, I didn't know PA1 isn't working then. 2011/1/18 Jeff Gribbin <[email protected]> > Greetings, > I've been playing around in my sandpit again and could, once more, do with > confirmation of what I appear to have learned ... > > The objective of my playing around was to gain experience (2nd-level) in > using the (HMC) Integrated 3270 Console. All 2nd-level ... > > Logon 2NDLEVEL userid > TERM SYS3270 ON > IPL <2NDLEVEL sysres address> CLEAR LOADPARM SYSG > > ... SAPL screen appears ... brilliant > > Press PA1, expecting to break back to 1st level (as with CONMODE 3270) but > stay within SYSG emulation and SAPL screen. Eventually use CP FOR from > MAINT to logoff 2NDLEVEL. (Yes, BRKKEY IS set to PA1 - I double-checked.) > > From the above, it would SEEM that SYS3270 is a one-way street - once it's > established there's no way back to allow one to enter CP commands at 1st > level (with the intention of subsequently returning to the 'SYSG' screen). > > I've had a good hard look at CP Commands and Utilities Reference and > haven't > found a definitive statement either way. > > Would anyone with greater experience care to (please) share with me what > they know on this topic? > > As usual for me nowadays, nothing's hanging on this except, 'knowledge' - > please don't go to any great efforts. > > Regards > Jeff > -- Kris Buelens, IBM Belgium, VM customer support
