Re: OPM and Store/Retrieve Associated Space

["Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>]

Hi, Tom:

You can do what you need by using the associated space of an OPM *PGM.

You could use CRTCLPGM to create OPM CLP programs for this purpose, as 
this feature is "bundled" with the "base" OS.  Or, write those programs 
in MI assembler language; the QPRCRTPG API is also built-in to the 
"base" OS.  Are you concerned about future availability of the other 
("heritage") OPM compilers?

I would like to understand more about what you need to do in a 
pre-restore exit that could not also be done in a post-restore exit. 

Contact me "off-list" ...

Thanks,

Mark S. Waterbury

> Tom Liotta wrote:
> Mark S. Waterbury wrote:
>
>   
> > This approach is viable for both OPM and ILE *PGMs, and for ILE 
> > *SRVPGMs, and pretty much ANY OS/400 object type.
> >     
>
> Mark:
>
> Unfortunately, it involves a *USRSPC object rather than a *PGM 
> object. For my intended usage, there is no [apparent] choice but a *PGM.
>
> A very specific example problem involves the pre-restore exit point 
> for RSTLICPGM. The _only_ object type that can be restored during 
> that operation is a *PGM object. No data files, no message files... 
> no user spaces...
>
> The very nice thing about the associated space is that it can be 
> modified even after a LPP is installed. A customer who wants to add 
> some specific customizations can be presented with options that 
> alter values stored in an associated space. A subsequent SAVLICPGM 
> can then save those customizations for distribution to other systems 
> in their network. There's enough available space even to track who 
> made which changes, when they were made, etc., not to mention 
> encryption and just about whatever is needed in such a limited context.
>
> When those options involve pre-restore environment elements, the 
> only available object type is *PGM. And OPM *PGMs seem to be the 
> ones that have this capability.
>
> Tom Liotta
>
>