|
Hello Brad, I think Neil is on the right track with the memo to user's but I wanted to comment on the signature change. IBM service programs are not supposed to allow the signature to change even if the modules or procedures change. The last I knew was that IBM service programs were supposed to be created with the service program name as the signature (e.g., QTMHCGI) and the service program author assumes responsibility for ensuring the program works correctly (i.e., procedure positions do not change). The net is you should never get a signature violation from an IBM service program and you should NEVER have to recompile YOUR code just to get the new signature. (That is really the point of multiple signature support in service programs). In fact, if you get signature violations from IBM service programs on upgrades (and there is no notice of this possibility in the memo to users) then I'd be raising an APAR on that program. Regards, Simon Coulter. //---------------------------------------------------------- // FlyByNight Software AS/400 Technical Specialists // Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 // Fax: +61 3 9419 0175 E-mail: shc@flybynight.com.au // // Windoze should not be open at Warp speed. //--- forwarded letter ------------------------------------------------------- > X-Mailer: Internet Mail Service (5.5.2232.9) > Date: Wed, 02 Dec 98 17:37:35 -0600 > From: "Stone, Brad V (TC)" <bvstone@taylorcorp.com> > To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com> > Reply-To: MIDRANGE-L@midrange.com > Subject: RE: CGI problem > > Chances are the QTMHCGI service program was changed, changing the signature > of the service program. This is most likely why your program is bombing. > Try recompiling any programs that use this service program. If you were to > debug the http job (how to do this is explained actually pretty well inthe > IBM manuals), you would probably see a signature violation error. > > Give it a shot... To verify this, before recompile, do a DSPPGM on your CGI > program and look at the signature of the Service Program in question. Then > do the same for the service program. They probably will be different. (And > long.. they look like this... 000E15105B5A878C93B56CB5E813152B) > > Bradley V. Stone > Taylor Corporation - OASIS Programmer/Analyst > bvstone@taylorcorp.com > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.