|
Now why would I tell you? <vbg> There is no value *USER and *SUPER will only work under a very limited set of circumstances. Call it repetitive redundancy over and over again... Joel R. Cochran Director of Internet Services VamaNet.com (800)480-8810 mailto:webmaster@vamanet.com > -----Original Message----- > From: Walden H. Leverich [mailto:WaldenL@TechSoftInc.com] > Sent: Monday, August 05, 2002 4:29 PM > To: 'web400@midrange.com' > Subject: RE: [WEB400] Strange QtmhCvtDB problem > > > Joel, > > I don't use QtmhCvtDB so I can't help there, but I have a > question. What is > AUTHCODE (value *SUPER in your example) and what happens when > a *badguy with > a value of *USER changes it to *SUPER before posting his > response? Just > curious <G> > > -Walden > > > ------------ > Walden H Leverich III > President > Tech Software > (516) 627-3800 x11 > (208) 692-3308 eFax > WaldenL@TechSoftInc.com > http://www.TechSoftInc.com > > Quiquid latine dictum sit altum viditur. > (Whatever is said in Latin seems profound.) > > > > -----Original Message----- > From: Joel R. Cochran [mailto:jrc@masi-brac.com] > Sent: Monday, August 05, 2002 13:13 > To: 'web400@midrange.com' > Subject: [WEB400] Strange QtmhCvtDB problem > > > I'm experiencing a strange problem with QtmhCvtDB. > > I have a web page submitting the following form: > > <form name="update" method="post" action="myCGI"> > <input type="hidden" name="STATS" value="p76453tr"> > <input type="hidden" name="SESSION" > value="jsmasi-bracjoelc81853682"> <input > type="hidden" name="AUTHCODE" value="*SUPER"> <input type="hidden" > name="CLIENTID" value="demo"> <input type="hidden" > name="AXTYPE" value="R"> > <input type="hidden" name="AXLOC" value="SWVA"> <input type="text" > name="BEGDATE" value="08/05/2002"> <input type="text" name="ENDDATE" > value="08/05/2007"> </form> > > In debug, the Environment variable String passed to QtmhCvtDB > look like > this... > > STATS=p76453tr > &SESSION=jsmasi-bracjoelc81853682 > &AUTHCODE=*SUPER > &CLIENTID=demo > &AXTYPE=R > &AXLOC=SWVA > &BEGDATE=08/05/2002 > &ENDDATE=08/05/2007 > > > The file used by QtmhCvtDB is defined like this: > > A R AUTH5R > A STATS 128 > A SESSION 60 > A AUTHCODE 15 > A CLIENTID 15 > A AXTYPE 1 > A AXLOC 10 > A BEGDATE 10 > A ENDDATE 10 > > > But after the call to QtmhCvtDB the last variable (ENDDATE) > in the DS is not > populated... > > STATS OF ENVDS = > ....5...10...15...20...25...30...35...40...45...50...55...60 > 1 'p76453tr > ' > 61 ' > ' > 121 ' ' > SESSION OF ENVDS = > 'jsmasi-bracjoelc81853682 > ' > AUTHCODE OF ENVDS = '*SUPER ' > CLIENTID OF ENVDS = 'demo ' > AXTYPE OF ENVDS = 'R' > AXLOC OF ENVDS = 'SWVA ' > BEGDATE OF ENVDS = '08/05/2002' > ENDDATE OF ENVDS = ' ' > > > The fields are all named correctly, the data is present. > What else couldbe > causing this? I've never had a problem with QtmhCvtDB before... > > TIA, > > Joel R. Cochran > Director of Internet Services > VamaNet.com > (800)480-8810 > mailto:webmaster@vamanet.com > > _______________________________________________ > This is the Web Enabling the AS400 / iSeries (WEB400) mailing > list To post a > message email: WEB400@midrange.com To subscribe, unsubscribe, > or change list > options, > visit: http://lists.midrange.com/cgi-bin/listinfo/web400 > or email: WEB400-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/web400. > _______________________________________________ > This is the Web Enabling the AS400 / iSeries (WEB400) mailing list > To post a message email: WEB400@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/web400 > or email: WEB400-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/web400. >
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.