RE: net.data error Incorrect symbol (looking at DB2WWW)

 
Thanks Peter.  I think some of my replies to Mike were addressed off
list so you didn't see them.
Yes, the Amra quote says it well.  Mike should be OK now. 

--
Doug Hart
 

-----Original Message-----
From: midrange-l-bounces+doug.hart=itt.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+doug.hart=itt.com@xxxxxxxxxxxx] On Behalf Of
Peter Levy
Sent: Wednesday, August 09, 2006 1:28 PM
To: Midrange Systems Technical Discussion
Subject: Re: net.data error Incorrect symbol (looking at DB2WWW)

According to Amra (Net.Data developer) on the dtwdude.com forum:

"technically....qsyscgi and qhttpsvr are the same, qsyscgi is used by
the OS, and is equivalent to QHTTPSVR.  Both these programs are really
stubs that call into a service program in qhttpsvr.

As for the one in qtcp....that was the original location of Net.Data
(back in
v3r2 and v3r7 and i think v4r1), and should not be used.  Although if
you do use it, it will call a service program in qtcp which then calls
the service program in qhttpsvr."

http://dtwdude.com/forum/view.php?SID=20041207173314704564&NRL=2
  ----- Original Message -----
  From: Mike Cunningham
  To: Doug.Hart@xxxxxxx ; Midrange Systems Technical Discussion
  Sent: Wednesday, August 09, 2006 12:07 PM
  Subject: RE: net.data error Incorrect symbol (looking at DB2WWW)


  Thanks for the reminder, I had forgot about this being the recommended
  procedure.
   
  I currently have 4 DB2WWW *PGM objects on my system
   
  CGI Library (our own and the one the Apache map directive points to)
  created 01/14/05 V5R2M0 size 53248
  QTCP created 12/06/00 V5R1M0 size 61440
  QSYSCGI created 06/10/05 V5R3M0 size 57344
  QHTTPSVR created 12/05/03 V5R3M0 size 57344
   
  Any idea as to which one is the correct one that is patched as PTFs
are
  applied? I would guess it's the QHTTPSVR one. We clearly appear to be
  using an out of date version.

  >>> Doug.Hart@xxxxxxx 8/9/2006 11:22:40 AM >>>


  It is common to make a copy of the IBM program DB2WWW in one of your
  own
  libraries.  Chances are that if you upgraded or applied PTFs you need
  to
  replace this copy of the program with the IBM version again.   

  --
  Doug Hart 


  -----Original Message-----
  From: midrange-l-bounces+doug.hart=itt.com@xxxxxxxxxxxx
  [mailto:midrange-l-bounces+doug.hart=itt.com@xxxxxxxxxxxx] On Behalf
  Of
  Mike Eovino
  Sent: Wednesday, August 09, 2006 9:49 AM
  To: Midrange Systems Technical Discussion
  Subject: Re: net.data error Incorrect symbol

  We get that error occasionally, and it's pretty tough to diagnose
  exactly what is going wrong.  We find that if we make a simple change
  to
  the macro (add a few blank spaces somewhere) and save the file, it
  usually takes care of the problem.

  I think (and I'm just guessing here) that there is probably a problem
  with the tokenized macro in the macro cache.  Changing the last
  modified
  date/time will force the db2www cgi program to reread and re-tokenize
  the macro.

  Like I said, that's just a guess as to why this works, but regardless,
  it generally solves the issue.

  Mike E.

  On 8/8/06, Mike Cunningham <MCUNNING@xxxxxxx> wrote:
  > We started getting an error sent from net.data that has "Incorrect
  > symbol <varies> encountered in macro <varies> at line <varies>" If
we

  > restart the Apache server right away when we catch this the error
  goes

  > away without making any changes to the macro or any of the includes
  > (just about all of our macros have includes) so we can prove it's
not

  > a constant error. The errors will start at random times and then go
  > away by themselves. We were able to force it to happen by putting an

  > error in one of the includes (add an extra @) and then taking it
away

  > again. No errors in any logs (that we can find). Anyone else come
  > across this error before?


  ************************************
  This e-mail and any files transmitted with it are proprietary and
  intended solely
  for the use of the individual or entity to whom they are addressed. If
  you have
  received this e-mail in error please notify the sender. Please note
  that any views
  or opinions presented in this e-mail are solely those of the author
and
  do not
  necessarily represent those of ITT, Inc. The recipient should check
  this e-mail and any attachments for the presence of viruses. ITT
  accepts
  no liability for any damage caused by any virus transmitted by this
  e-mail.
  ************************************


  -- 
  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.