Hi Marcus, thanks newly.

My issue is not how to create an ISPF dynamic panel. My solution is very similar to your solution.
When I say dynamic is because when the REXX process builds the panel it takes values from a dataset and this dataset with configuration data can changes n times a day.
It's not so good to do Logoff or 7.2 Test Panel to access to the new copy.

I finished solving this issue creating dynamics panel names "P"||hr.||min.||secs.
and works fine.

Hello Leonardo,
Here are our official documented approachs: When do changes to my ISPF panel take effect? (ibm.com)

Thanks Krasen, good for understand why panel definition remains.

Where are you placing your generated ISPF Panel?  If you are placing it in a library in your ISPPLIB allocation that would account for the reason you need ISPF TEST or exiting ISPF to get access to it.  

A better approach is to allocate a temporary PDS(E) to host the newly created ISPF Panel and the LIBDEF to that PDS(E). That way each time you will get a new LIBDEF and thus access to your newly created ISPF Panel.

hth

Do you LIBDEF release after use and LIBDEF new for the new panel?

Hello Leonardo,

For testing, I start my ispf session with test parameter and then reload ispf by the next display panel new.  You find more details: The dialog test environment - IBM Documentation 

Maybe my hint will help you. 

Kind regards

Roger     

I have a solution, functionaly nice because every time the execution of the Rexx application  builds dynamicaly  the panel, panel name changes; that allows to do nothing, always will work fine.
No Test Panel, no ISPF getout-in or logoff-logon.
This Rexx application is not a monouser application, it can be executed by any user with permissions in a ISPF session. 
CDB2.PNG shows the screen menu.
Until 248 DB2 data models to replicate from an environment to other ( Dev<-> Testing<->UAT<->Prod) can be defined in the screen menu.
Each model has a library; each library has lists of db2 Tables, Keys, relations between tables, etc.
If a user adds a new data model, all the application executions must put this new model in the menu in the next Menu operation.
Same if a user deletes a data model or changes his name.
When a user selects one of the 248 data models and press Enter, newly a data screen is built dinamycally from the data stored in the defined library ( cdb21.png ) allowing the operator to enter the keys of data tables to replicate.
If someone changes the model data, for instance introducing a new table for this particular model, all user must see this table in the screen dynamicaly generated without any logoff, Test Panel, ISPF getout/getin.

When I started this application  I didn't know the rule that maintains 6 screen in memory. Because of this I ask you and today I built a solution.
 
Thanks z  people and REXX people
 

Hi Leonardo,

It's been a while since I wrote ISPF applications in REXX, so I could be wrong. I just found these two lines in an EXEC I wrote in 2002:

'ISPEXEC LMCLOSE DATAID('dataid')'            /* Close library      */
'ISPEXEC LMFREE  DATAID('dataid')'            /* Free library       */

I vaguely recall that I had to close and reopen the ISPF panels dataset so that changes were picked up. Not sure the LMFREE is needed, maybe LMCLOSE is enough.

On other EXECs where I was using EXECIO, I had to close the file with FINIS (sorry, I don't remember the details).

Hope this helps.

Regards,

Emir Garza

------------------------------
Emir Garza
------------------------------

Hello Emir, thanks for your help.
I developed a solution for this issue and works.