|
Thanks for your help! -----Original Message----- From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx]On Behalf Of Jay Sulzmann Sent: Thursday, August 05, 2004 10:46 AM To: COBOL Programming on the iSeries/AS400 Subject: Re: [COBOL400-L] QlnDumpCobol Problem I tried. Call IBM? ----- Original Message ----- From: "Chris Johnson" <CJohnson@xxxxxxxxxxxx> To: "'COBOL Programming on the iSeries/AS400'" <cobol400-l@xxxxxxxxxxxx> Sent: Thursday, August 05, 2004 11:40 AM Subject: RE: [COBOL400-L] QlnDumpCobol Problem > Jay > > I tried both of the directory's you listed. It did not solve the problem. > I have not been able to find any information on the directory in IBM's > documentation. > > Chris > > -----Original Message----- > From: cobol400-l-bounces+cjohnson=dotfoods.com@xxxxxxxxxxxx > [mailto:cobol400-l-bounces+cjohnson=dotfoods.com@xxxxxxxxxxxx] > Sent: Thursday, August 05, 2004 10:20 AM > To: COBOL Programming on the iSeries/AS400 > Subject: Re: [COBOL400-L] QlnDumpCobol Problem > > > Chris, > > It should be one whose name begins with a "Q". > Like QCBLLE or QUSAPIBD. > You might want to check IBM's documentation, > http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm > look under Programming, API's. > Hope this helps. > > Jay > > > ----- Original Message ----- > From: "Chris Johnson" <CJohnson@xxxxxxxxxxxx> > To: "'COBOL Programming on the iSeries/AS400'" <cobol400-l@xxxxxxxxxxxx> > Sent: Thursday, August 05, 2004 11:11 AM > Subject: RE: [COBOL400-L] QlnDumpCobol Problem > > > > Jay, > > > > No I left it as *none. Which binding directory do I need to use? > > > > Chris > > > > -----Original Message----- > > From: cobol400-l-bounces@xxxxxxxxxxxx > > [mailto:cobol400-l-bounces@xxxxxxxxxxxx] > > Sent: Thursday, August 05, 2004 10:08 AM > > To: COBOL Programming on the iSeries/AS400 > > Subject: Re: [COBOL400-L] QlnDumpCobol Problem > > > > > > Chris, > > > > Did you specify the appropriate binding directory parameter value when you > > attempted to compile the program? > > > > Jay > > > > ----- Original Message ----- > > From: "Chris Johnson" <CJohnson@xxxxxxxxxxxx> > > To: "COBOL Programming on the iSeries/AS400" <cobol400-l@xxxxxxxxxxxx> > > Sent: Thursday, August 05, 2004 11:03 AM > > Subject: [COBOL400-L] QlnDumpCobol Problem > > > > > > > We are new to ILE at my shop and are having problems with the > QlnDumpCobol > > > API. When compiling the code listed below we receive the following > error. > > > We are currently running 5VR2. Does anyone have any suggestions? > > > > > > * 1070 MSGID: LNC0047 SEVERITY: 20 SEQNBR: 044300 > > > Message . . . . : Program-name '"QlnDumpCobol"' is not valid. > > > > > > CALL PROCEDURE "QlnDumpCobol" USING WS-PROGRAM-NAME > > > WS-LIBRARY-NAME > > > WS-MODULE-NAME > > > WS-PROGRAM-TYPE > > > WS-DUMP-TYPE > > > WS-ERROR-CODE. > > > > > > Chris Johnson > > > Computer Programmer > > > Dot Foods Inc. > > > 217-773-4486 Ext. 2685 > > > > > > > > > _______________________________________________ > > > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing > > list > > > To post a message email: COBOL400-L@xxxxxxxxxxxx > > > To subscribe, unsubscribe, or change list options, > > > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l > > > or email: COBOL400-L-request@xxxxxxxxxxxx > > > Before posting, please take a moment to review the archives > > > at http://archive.midrange.com/cobol400-l. > > > > > > > > > > > > _______________________________________________ > > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing > list > > To post a message email: COBOL400-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l > > or email: COBOL400-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/cobol400-l. > > > > _______________________________________________ > > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing > list > > To post a message email: COBOL400-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l > > or email: COBOL400-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/cobol400-l. > > > > > > > _______________________________________________ > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list > To post a message email: COBOL400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l > or email: COBOL400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/cobol400-l. > > _______________________________________________ > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list > To post a message email: COBOL400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l > or email: COBOL400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/cobol400-l. > > _______________________________________________ This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/cobol400-l or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-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.