What is this: ISPF PGM(EZYIIF) PARM(DPANEL(ISR@PRIM)) NEWAPPL(ISR) Can it be turned off?

Products

• PDSMAN

Issue/Introduction

While working on an ispf issue with ibm support in the ibm ispf trace we saw

     ISPVCALL Version:    ISPVCALL  2021.057  z/OS 2.05 BASE                 
     ISPVCALL Command: ISPVCALL TRACE STATUS                                 
     ISPF Invocation:  ISPF PGM(EZYIIF) PARM(DPANEL(ISR@PRIM)) NEWAPPL(ISR)  

when / why does pdsman hook into ibm ispf?

What impact is seen when turning it off?

 

 

Environment

Release : 7.7

Resolution

EZYIIF is part of the ISPF frontend process that supports the EZYEDIT TSO Command Shell and creating dynamic ISPF Command Table entries as defined by $EZYCMD rules.

This process is triggered by $EZYEDIT CMDTABUPD=Y (is the default). PDSMAN frontends ISPSTART or ISPF and changes ISPF's parameter list so ISPF knows to call EZYIIF as each split session is created. EZYIIF drives EZYCTU to update the ISPF System Command table as first logical ISPF screen has fired up. EZYIIF then invokes whatever the specified or default ISPF initial command happens to be. 

Another option:

Besides the CMDTABUPD=N, it might be easier for the user that was having the problem to allocate an EZYOFF DD DUMMY - like this:

//EZYOFF DD DUMMY

This would effectively set CMDTABUPD=N for that user only. They could set CMDTABUPD back to Y and it would be effective for other uses.

To answer the last question on impact - users depending on CMDTABUPD=Y would see commands not recognized for commands defined on $EZYCMD PDSMINIT statements.