Re: CL command

["Jim Franz" <franz400@xxxxxxxxxxxx>]

If you do not want to chgcurlib, then rtvmbrd will give you the actual
library
name the file is found in from your *libl, then use that parm to execute
your
other commands.
jim franz

----- Original Message -----
From: "Dennis Lovelady" <dlovelady@dtcc.com>
To: "Midrange Systems Technical Discussion" <midrange-l@midrange.com>
Sent: Monday, January 13, 2003 7:33 AM
Subject: Re: CL command


>
> Yes, that approach is sound.
>
> CHGCURLIB LIBRARY_CONTAINING_PF
> ADDLFM FILE(SOMELIB/LFNAME) MBR(MBRNAME) +
>        DTAMBRS((*CURRENT/PF1NAME (MBR1 MBR2)))
>
>
>
>
>
>
>
> "N, Muralidhar" <Muralidhar.N@blr.hpsglobal.com>@midrange.com on
01/13/2003
> 07:08:05 AM
>
> Please respond to Midrange Systems Technical Discussion
>        <midrange-l@midrange.com>
>
> Sent by:    midrange-l-bounces@midrange.com
>
>
> To:    "'Midrange Systems Technical Discussion'" <midrange-l@midrange.com>
> cc:
> Subject:    CL command
>
>
>
> some of the CL commands do not accept *LIBL and either require a
> library-name or *CURRENT to be specified. One example is ADDLFM command
> while specifying PF data-members. In this case, is it safe to specify
> *CURRENT, by expecting the data-file to be in current-library ?
>
> Since we are using members in our transaction-files, this has become  an
> important issue...
> Kindly suggest me!
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>