Once you have successfully logged onto an ECF session from a console, you have a TSO session in READY mode with which you can interact. Output from your session will be routed back to your console automatically by CA OPS/MVS, but every line of input you enter for this session must be explicitly routed to it by prefixing it with a question mark (?). Do not use the OSF command character string. It is reserved for routing single-line requests to OSF TSO servers. This can be confusing at first because the OSF is still available, even while you are using the ECF. Worse, many commands you might enter through the ECF will also work if entered through the OSF, adding to the potential confusion.
This is an example session with the ECF to fix a broken VTAM procedure:
?LOGON syssup02/secret sub(mstr) OPS1000I START OPSECF.SYSSUP02,SSID=OPSS,UID=SYSSUP02 START <logon-related messages from your security product, if any> OPS2106H SYSSUP02 LOGON FOR OPSS(1) AT 00:18:39 ON JANUARY 12, 2004 IKJ56644I NO VALID TSO user ID, DEFAULT USER ATTRIBUTES USED READY ?edit 'sys1.proclib(vtam)' data EDIT ?verify on EDIT ?f '//vtamlst' 6000 //VTAMLST DD DSN=SYS1.VTAMLST,DISP+SHR EDIT ?c 'disp+shr' 'disp=shr' 6000 //VTAMLST DD DSN=SYS1.VTAMLST,DISP=SHR EDIT ?end save READY ?LOGOFF
This use of the ECF is referred to as system rescue since it allows you to fix z/OS when it is in such a bad state that the typical tools you use (for example, TSO/ISPF) are not available. Naturally, the above session is somewhat simplified. Since it is happening at a console, unsolicited messages can interleave with the messages generated by the ECF session.
The IKJ56644I message above is typical and does not indicate any sort of error in the ECF session.
|
Copyright © 2014 CA.
All rights reserved.
|
|