|
Apart for the reasons Rob stated I don't think you are missing anything Dave, I also see no reason it should be anywhere else, but for some reason, in Alans shop, somebody did. Steve -----Oorspronkelijk bericht----- Van: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]Namens Turnidge, Dave Verzonden: vrijdag 12 januari 2007 15:36 Aan: Midrange Systems Technical Discussion Onderwerp: RE: Creating a physical AND Logical file Wow! QTEMP is ONLY used by the current job. Objects in that library have to be created BY that job for use by that job ONLY. We ALWAYS have QTEMP at the top of the user portion of the library list. I don't know of ANY value for QTEMP that would place it at the end of the list... ??? What am I missing here?? Dave -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore Sent: Friday, January 12, 2007 8:29 AM To: Midrange Systems Technical Discussion Subject: RE: Creating a physical AND Logical file Thanks for your reply Steve I'm not saying QTEMP cannot be at the top of the library list. I t looks like I will have to move QTEMP to *FIRST, create the logical< and move it back to the *LAST. QTEMP being the last in the library list is just a "rule" at our shop. Alan Shore NBTY, Inc (631) 244-2000 ext. 5019 AShore@xxxxxxxx midrange-l-bounces@xxxxxxxxxxxx wrote on 01/12/2007 01:51:28 AM:
Why can't QTEMP be at the top of your library list? I have always thought that because of what it is that is the ideal place for it to
be.
Steve -----Oorspronkelijk bericht----- Van: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]Namens Alan Shore Verzonden: donderdag 11 januari 2007 22:10 Aan: Midrange Systems Technical Discussion Onderwerp: RE: Creating a physical AND Logical file Sorry Charles - no go I end up with the same problem. Just doesn't like the situation. I may have to do what someone else has suggested and move the library
QTEMP
to the top of the library list, create the logical and move QTEMP
back.
There must be some other way to do this. I've got to be doing something wrong. Alan Shore NBTY, Inc (631) 244-2000 ext. 5019 AShore@xxxxxxxx midrange-l-bounces@xxxxxxxxxxxx wrote on 01/11/2007 03:27:46 PM:So just ADDLFM.. Not a big deal, the important thing is that the logical in QTEMP is pointing to the physical in QTEMP. Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121-----Original Message----- From: midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx [mailto:midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx] On Behalf Of Alan Shore Sent: Thursday, January 11, 2007 3:18 PM To: Midrange Systems Technical Discussion Subject: RE: Creating a physical AND Logical file Thanks NIck - I've already tried that, with the result that the logical has NO members. What release are you on? We are on V5R4. Like I've said before, maybe its a PTF I need Alan Shore NBTY, Inc (631) 244-2000 ext. 5019 AShore@xxxxxxxx midrange-l-bounces@xxxxxxxxxxxx wrote on 01/11/2007 03:11:22 PM:Hi Alan, Then how about this: CRTLF FILE(QTEMP/CCA012L1) SRCFILE(XALIB/QDDSSRC) DTAMBRS((QTEMP/CCA012PF(CCA012PF))) Instead of specifing DTAMBRS(*ALL), put in your QTEMP/PF FILE(PF
MBR
NAME)This works on my system. I have done this for years this way. Good Luck, Nick Nick Radich Sr. Programmer/Analyst EPC Molding, Inc. Direct (320) 679-6683 Toll free (800) 388-2155 ext. 6683 Fax (320) 679-4516 nick_radich@xxxxxxxxxxxxxx Alan Shore <AlanShore@xxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 01/11/07 01:23 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject RE: Creating a physical AND Logical file Thanks Nick, but unfortunately that picks up the physical file that resides in an earlier library on the library list Alan Shore NBTY, Inc (631) 244-2000 ext. 5019 AShore@xxxxxxxx midrange-l-bounces@xxxxxxxxxxxx wrote on 01/11/2007 02:18:38 PM:Alan, Try this: CRTLF FILE(QTEMP/PHYSFILE) SRCFILE(PRODUCTION/QDDSSRC)DTAMBRS(*ALL)HTH, Nick Nick Radich Sr. Programmer/Analyst EPC Molding, Inc. Direct (320) 679-6683 Toll free (800) 388-2155 ext. 6683 Fax (320) 679-4516 nick_radich@xxxxxxxxxxxxxx Alan Shore <AlanShore@xxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 01/11/07 01:05 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject RE: Creating a physical AND Logical file Hello everyone IIIIII'MMMMMM baaack Okay - due to auditing constraints and other things, I amnot allowed touse CRTDUPOBJ So - I am trying the suggestion put forth by Clyde, and Iam havingproblems I am creating a physical file in QTEMP CRTPF FILE(QTEMP/PHYSFILE) SRCFILE(PRODUCTION/QDDSSRC)SRCMBR(PHYSFILE)and I can populate this file no problem Then when I create the logical CRTLF FILE(QTEMP/LOGFILE) DTAMBRS((QTEMP/PHYSFILE)) The logical file gets created but with NO member The error that occurs is File PHYSFILE in QTEMP on DTAMBRS not valid. An F1 on this message shows Message ID . . . . . . : CPF7356 Severity . . .. . . . : 30Message type . . . . . : Information Date sent . . . . . . : 01/11/07 Time sent . . . . .
. :
13:58:48 Message . . . . : File SLSCOMP in QTEMP on DTAMBRS not
valid.
Cause . . . . . : File SLSCOMP in library QTEMP on the
DTAMBRS
parameter is not valid. The physical files on the DTAMBRS parametermust match thephysical files on the PFILE or JFILE keywords in theDDS for thelogical file. In addition, the physical file names cannot bespecified moreoften on the DTAMBRS parameter than on the PFILE or JFILEkeywords in the DDSfor the logical file. Recovery . . . : Change the DTAMBRS parameter so thefile namesmatchthe names on the PFILE or JFILE keywords in the DDS for the
logical
file.Then try the request again. Technical description . . . . . . . . : If a libraryname was notspecified for the physical files on the PFILE or JFILE keywordsin the DDS forthe logical file, the library list (*LIBL) was used to findthe physicalfiles. The physical files specified on the DTAMBRS parametermust match thephysical files found in the library list. The name on the DDS is PHYSFILE - so right now I amdrawing a blank onthis ANY help with this would be greatly appreciated. Thanks in advance Alan Shore NBTY, Inc (631) 244-2000 ext. 5019 AShore@xxxxxxxx midrange-l-bounces+alanshore=nbty.com@xxxxxxxxxxxx wroteon 01/10/200712:02:23 PM:Use the command: CRTLF FILE(QTEMP/LOGFILE) DTAMBRS((QTEMP/PHYSFILE)) Clyde -----Original Message----- From: Troy Foster [mailto:tfoster@xxxxxxxxxx] Sent: Wednesday, January 10, 2007 10:52 AM To: Midrange Systems Technical Discussion Subject: Creating a physical AND Logical file A R HDR810 PFILE(POLIB/EDIP810H) A K IVNUMB Troy Foster wrote:Make sure that your logical points to the PHYSFILE in
QTEMP.
Alan Shore wrote:Mornin' everyone. Here is my predicament I need to create a physical file PHYSFILE in QTEMP using theCRTPF.This isno problem. I then need to create a Logical LOGFILE (also inQTEMP) againstthisPhysical PHYSFILE in QTEMP. Heres where the problem lies. The Logical that is created is against a physicalfile of the samenamePHYSFILE that is in an earlier library on the library
list.
How can I create the logical LOGFILE against thephysical PHYSFILEthatresides in QTEMP? Alan Shore NBTY, Inc (631) 244-2000 ext. 5019 AShore@xxxxxxxx-- This is the Midrange Systems Technical Discussion (MIDRANGE-L)mailinglist To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.************************************************************** ************************************This e-mail and any files transmitted with it are confidential and are intended solely
for
the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering theto theintended recipient, be advised that you have received thise-mail in error,and that any use, dissemination, forwarding, printing, or copying of thise-mail isstrictly prohibited. If you received this e-mail in error, please immediately notify Postmaster@xxxxxxxxxxxx Woodhead Industries, Inc. and its affiliates reserve the right to monitor all internal and external communications at
any time. *** WARNING *** Any email correspondence including responses to
this
withWoodhead Industries Inc or any of its subsidiaries will be scanned for Viruses and content deemed inappropriate by Woodhead Industries Inc.************************************************************** ************************************-- This is the Midrange Systems Technical Discussion (MIDRANGE-L)mailinglistTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailinglist To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailinglistTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailinglist To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailinglistTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.