RE: SAVLIBL, MAPICS, RSTLIBL ideas

> -----Original Message-----
> From: mapics-l-bounces@xxxxxxxxxxxx / Dave Shaw
> Sent: Monday, July 26, 2004 4:02 PM
>
> This is very similar to what I always did.  DB Mod 4 has never
> catered to the extended library lists, and almost certainly never
> will.  XA through Release 6 also never did when I was working on
> it.  I don't know if that has been or will be changed at any time.
>
> The only gotcha I've ever encountered with making a copy of the
> MAPICS command is that ACSAPPLY used to have problems with that
> if a PTF or release upgrade needed to replace the MAPICS command.
>  I learned to delete or rename my copy beforehand so it wouldn't
> 'see' it.  Of course, you would need to make sure that your CL
> still works afterward.
>
> Dave Shaw
> MAPICS-L Moderator

What does ACSAPPLY do?  Object description of "ACS APPLY BOOTSTRAP MAINLINE"
doesn't tell me much.

If we were to implement this in production, I'd probably put my new MAPICS
command in a library that sits higher in everyone's library list than the
QGPL/MAPICS command.  I realize that if we apply MAPICS PTFs, we'll need to
verify that the original command/program hasn't changed/added any parameters
but, jeez, I hope they'd have that pretty stable by now! <g>

db