|
Hi: Allow me to join in your interesting and important topic on COBOL. As far as I can see, COBOL (whether it be on the mainframes, midrange computers, PC, etc.) it is still COBOL (of course with some minor differences), am I right? I have been working as a COBOL programmer for almost 9 years. The environment is PC COBOL, little exposure on CICS on the mainframes, but lots and lots of experience in the HP 3000 and HP9000 arena where we use COBOL 85 and interfacing it with Screen Design (like the one on System 36) but it is called VP-PLUS and reading data from the database using IMAGE database. I don't dare to say that it is easy for a newcomer, as one has to be very familiar with the API and INTRINSIC calls to produce good quality screens and/or reading data from the various datasets from various databases at one time. What I don't understand is that why AS400 employers are reluctant to hire competent COBOL programmers coming from other platforms? I have a hard time find a job in the AS400 arena (not to say COBOL is NOT popularly used now) .... but when I go for these interviews the employer's excuse is NOT on the language itself, but ".... I am looking for somebody with additional knowledge in CL, SDA etc. as well". Why? I know that anybody with the knowledge of the language can pick up the other things ..... but why employers are so reluctant to hire non AS400 COBOL programmers? The reason for me to look for an AS400 job is because I like to program in that environment using externally described files, using embedded SQL and so forth. Any offer? -----Original Message----- From: Weatherly, Howard [mailto:hweatherly@dlis.dla.mil] Sent: Monday, July 23, 2001 10:06 AM To: 'COBOL400-L@midrange.com' Subject: RE: System API QlnDumpCobol The COBOL is much the same and you experience is not wasted, but there are some different ways of doing things, The COBOL Guide and Reference are as much as you should need but any book on COBOL-85 or COBOL/II will help with the additions to the Language. The environment might be culture shock though and the best way to learn that is to try things (assuming you have that luxury) otherwise, IBM has excellent courses available, here is a good place to start looking http://www-3.ibm.com/services/learning/ <http://www-3.ibm.com/services/learning/> -----Original Message----- From: IDNONADA [ mailto:idnonada@home.com <mailto:idnonada@home.com> ] Sent: Friday, July 20, 2001 17:06 To: COBOL400-L@midrange.com Subject: Re: System API QlnDumpCobol Bruce: I have a ton of Cobol and RPGII experience, but none in the AS400 environment. My experience has been 'Legacy', using IBM, NCR, TI, and Unisys(Burroughs). Is Cobol that much different in the AS400 environment than it is elsewhere? What resources are available to 'Educate' one for smooth transition into the AS400 environment. I appreciate any response. Thanx. ----- Original Message ----- From: "R. Bruce Hoffman, Jr." <rbruceh@attglobal.net> To: <COBOL400-L@midrange.com> Sent: Friday, July 20, 2001 1:50 PM Subject: Re: System API QlnDumpCobol > I would suspect case. The QlnDumpCobol vs. QLNDUMPCOBOL. > > It's a procedure and I have never tried to call the all uppercase value. > > > =========================================================== > R. Bruce Hoffman, Jr. > -- IBM Certified Specialist - AS/400 Administrator > -- IBM Certified Specialist - RPG IV Developer > > "America is the land that fought for freedom and then > began passing laws to get rid of it." > > - Alfred E. Neuman > > -----Original Message----- > From: Weatherly, Howard <hweatherly@dlis.dla.mil> > To: COBOL Midrange (E-mail) <COBOL400-L@midrange.com>; Midrange List > (E-mail) <MIDRANGE-L@midrange.com> > Date: Friday, July 20, 2001 11:45 AM > Subject: System API QlnDumpCobol > > > >Does anyone have a clue what object has become invisible to the compiler > >that is causing this to be not found? > > > >If I CRTBNDCBL it works, When I use CRTSQLCBLI it does not work! I am so > >confused!! > > > > > >CPD5D02 Diagnostic 30 07/20/01 10:20:01 QBNBIND > >QSYS *STMT > > > >QBNBIND QSYS *STMT > >From module . . . . . . . . : QBNBSYMR > > > >From procedure . . . . . . : QBNBSYMR__UnresolvedReferenceIterator > > > >Statement . . . . . . . . . : 31 > > > >To module . . . . . . . . . : QBNBSYMR > > > >To procedure . . . . . . . : QBNBSYMR__SignalUnresolvedReferences > > > >Statement . . . . . . . . . : 8 > > > >Message . . . . : Definition not found for symbol 'QLNDUMPCOBOL'. > > > >Cause . . . . . : No definition was found for reference QLNDUMPCOBOL in > > > > *MODULE object LMTD601D in library QTEMP. The definition either does not > > > > exist or is not of the same data or procedure type as the reference. > > > > Recovery . . . : Try the Create Program (CRTPGM) command again, > >supplying > > an object that contains a definition for symbol QLNDUMPCOBOL. > > > > > > > >Howard Weatherly > >(616) 961-4324 > >hweatherly@dlis.dla.mil > >Howard.Weatherly@ctg.com > > > > > > > > +--- > | This is the COBOL/400 Mailing List! > | To submit a new message, send your mail to COBOL400-L@midrange.com. > | To subscribe to this list send email to COBOL400-L-SUB@midrange.com. > | To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +---END > +--- | This is the COBOL/400 Mailing List! | To submit a new message, send your mail to COBOL400-L@midrange.com. | To subscribe to this list send email to COBOL400-L-SUB@midrange.com. | To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---END +--- | This is the COBOL/400 Mailing List! | To submit a new message, send your mail to COBOL400-L@midrange.com. | To subscribe to this list send email to COBOL400-L-SUB@midrange.com. | To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---END
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.