RE: CL command

Hi, Murali:

I cannot come there and do it for you, if that's what you mean.  :)  A
little busy today.  :)

Ummm....

Change current library to be that of the PF that you want to create the
logical:
    CHGCURLIB LIBRARY_CONTAINING_PF
Then, use ADDLFM to add a member to the LF.  Specify the library where you
want the LF to be created (which I have called SOMELIB) and the name of the
Logical (which I have called LFNAME.  Specify *CURRENT as the library name
for the PF, specify the PF name (which I have creatively called PF1NAME),
and specify the names of any members you want included in the view (which I
have called MBR1 and MBR2 in this case).
> CHGCURLIB LIBRARY_CONTAINING_PF
> ADDLFM FILE(SOMELIB/LFNAME) MBR(MBRNAME) +
>        DTAMBRS((*CURRENT/PF1NAME (MBR1 MBR2)))


What is it that you don't understand?

Dennis






"N, Muralidhar" <Muralidhar.N@blr.hpsglobal.com>@midrange.com on 01/13/2003
07:50:22 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:    RE: CL command


Can you just give some more explanation to justify this?
regards,
Murali.

> -----Original Message-----
> From:     Dennis Lovelady [SMTP:dlovelady@dtcc.com]
> Sent:     Monday, January 13, 2003 6:04 PM
> To: Midrange Systems Technical Discussion
> 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!