Posted by Frank Schubert on June 12, 2007 at 14:55:31:
In Reply to: ED on command line z/os v1.8 posted by Ron Fritz on June 07, 2007 at 10:14:11:
: We have just brought up z/OS V1.8 on our TEST lpar. When entering the ED command on the command line after selecting a job, we are put into ISPF(Spiffy) edit. If ED is entered as a line command next to JCL it works correctly. Is this something that you know about relating to z/OS V1.8.
After communicating with the customer, we found out that using the ED command as a line command to a datatset on the "IOF Job Summary", or as a line command to a job on the "IOF Job List Menu", worked ok. The ED command did not work from the "COMMAND ===>" line on the "IOF Job Summary". Everything was working ok on their production z/OS 1.6 system. The problem only existed on their z/OS V1.8 system.
It turns out that they had an ISPF Command called "(ED)it" defined in their z/OS V1.8 ISPF Command table, ISPCMDS, which was not defined in their z/OS V1.6 ISPF Command table. When a command is entered at the "COMMAND ===>" line of IOF, ISPF first tries to match it to any ISPF Command defined in ISPCMDS. If no match is made, then ISPF passes the command onto the application, in this case IOF. When they issued "ED" on the IOF "COMMAND ===>" line of their z/OS V1.6 system, no match was found and ISPF passed it onto IOF. But on their z/OS V1.8 system, a match was found and ISPF processed that instead of passing it to IOF.
The solution is to update the ISPF Command Table by removing the "(ED)it" command.
An alternate solution is possible. If needed, please contact IOF Technical Support for assistance.