Re: SAVLIBL, MAPICS, RSTLIBL ideas

Dan,

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

----- Original Message ----- 
From: "Dan Bale" <dbale@xxxxxxxxxxxxx>
To: <mapics-l@xxxxxxxxxxxx>
Sent: Monday, July 26, 2004 2:21 PM
Subject: SAVLIBL, MAPICS, RSTLIBL ideas


> We have noticed in the programming department an annoying habit of MAPICS
> whereby when we start MAPICS from a command line, then exit MAPICS, our
> library list was not returned to what it was before we entered MAPICS.  This
> tends to be a headache since we do our development on the production box,
> and if we're ever helping a user with production data and forget to reset
> the library list after exiting MAPICS, well, that's a bad day I'd like to
> avoid.
> 
> I have found a SAVLIBL & RSTLIBL tool elsewhere on the midrange.com lists,
> but wanted to know how others implemented this.  I'd rather not modify the
> AMZPAA program, but am not adverse to modifying the MAPICS command to call a
> "wrapper" CL that does the SAVLIBL, then CALLs AMZPAA, then RSTLIBL.  Here's
> the code for the new CPP:
> 
>   PGM        PARM(&APPID &ENDES &MNOP1 &MNOP2 +
>                      &MNOP3 &EXITA)
> 
>       DCL        &APPID   TYPE(*CHAR)  LEN(1)
>       DCL        &ENDES   TYPE(*CHAR)  LEN(2)
>       DCL        &MNOP1   TYPE(*CHAR)  LEN(2)
>       DCL        &MNOP2   TYPE(*CHAR)  LEN(2)
>       DCL        &MNOP3   TYPE(*CHAR)  LEN(2)
>       DCL        &EXITA   TYPE(*CHAR)  LEN(1)
> 
>       SAVLIBL
> 
>       Call       AMZPAA  Parm(&APPID &ENDES +
>                    &MNOP1 &MNOP2 &MNOP3 &EXITA)
> 
>       RSTLIBL
> 
>   ENDPGM
> 
> These are the same parameters that are used by AMZPAA.  Does anyone see any
> problems doing this that I'm not seeing?  I have tested it by CRTDUPOBJ'ing
> the MAPICS command to MAPICS2 in my library, changing the MAPICS2 command to
> use my new CPP, and it works fine.
> 
> It only saves up to 25 libraries.  Does MAPICS utilize the new 250-library
> limit in the LIBL?  I don't think it would be a big deal to enhance the tool
> to handle it.
> 
> tia,
> db