RE: HTTP job does not go to DEQW status - can't debug -- MIDRANGE-L

OK I get what you mean you can get an idea of the type of the job from its
initial description that it opens I see the following

The first job in my list of server jobs contains no description and is the
daemon job

There is next a job that says 'This is a multiple thread capable CGI job for
IBM HTTP Server instance XXXXXX'

And then all other jobs say 'This is a CGI job for IBM HTTP Server instance
XXXXXXXX.'

I normally see things like Net.Data will get dumped into the second type of
job which isnt multi thread capable. Looking at the servers here thats what
seems to happen? So I would go for debugging that type of job if you run
inhibited processes.

Thanks
Bleddyn

http://www.ignite400.org/ your AS/400 Internet/Intranet questions answered
FREE membership








-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of Stone, Brad V (TC)
Sent: Monday, February 01, 1999 07:09
To: 'MIDRANGE-L@midrange.com'
Subject: RE: HTTP job does not go to DEQW status - can't debug


The problem is that there are 4 or 5 jobs running, and it isn't always
consitant on which one will be running the CGI program.  Before when the one
was in DEQW status, it was easy to find which one to start a service job on.

Make more sense?

Bradley V. Stone
Taylor Corporation - OASIS Programmer/Analyst
bvstone@taylorcorp.com


> -----Original Message-----
> From: Bleddyn Williams [SMTP:bleddyn@morpheus.ltd.uk]
> Sent: Sunday, January 31, 1999 11:06 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: HTTP job does not go to DEQW status - can't debug
>
> Its still the same for a CGI program I think, when we debug Net.Data we do
> it that way still so I cant see why not. Does it not work for you?
>
> Thanks
> Bleddyn
>
> http://www.ignite400.org/ your AS/400 Internet/Intranet questions answered
> -
> FREE MEMBERSHIP
>
>
>
>
>
> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Stone, Brad V (TC)
> Sent: Friday, January 29, 1999 09:59
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: HTTP job does not go to DEQW status - can't debug
>
>
> Bleddyn,
>
> Are there new instructions for debugging CGI jobs then?
>
> Bradley V. Stone
> Taylor Corporation - OASIS Programmer/Analyst
> bvstone@taylorcorp.com
>
>
> > -----Original Message-----
> > From:       Bleddyn Williams [SMTP:bleddyn@morpheus.ltd.uk]
> > Sent:       Friday, January 29, 1999 2:37 PM
> > To: MIDRANGE-L@midrange.com
> > Subject:    RE: HTTP job does not go to DEQW status - can't debug
> >
> > Hi Brad its standard all webserver jobs for the HTTP server now sit in
> > TIMW
> > in their own subsystem.
> >
> > Thanks
> > Bleddyn
> >
> > http://www.ignite400.org/ your AS/400 Internet/Intranet questions
> > answered.
> >
> >
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: owner-midrange-l@midrange.com
> > [mailto:owner-midrange-l@midrange.com]On Behalf Of Stone, Brad V (TC)
> > Sent: Thursday, January 28, 1999 09:41
> > To: 'MIDRANGE-L@midrange.com'
> > Subject: HTTP job does not go to DEQW status - can't debug
> >
> >
> > Hi all.
> >
> > Found another bug most likely cause by the upgrade to V4R3.
> >
> > If you've message around with CGI programming on the AS/400, to debug a
> > job,
> > you must first end HTTP servers, and the start them with the
> >  '-minat 1 -maxat 1'
> >  parameter.  This ensures only one instance running.
> >
> > You would then find the job in the DEQW status.  You then start a server
> > job
> > on this job and then you could use debug on a CGI program.
> >
> > Well, now it seems none of the jobs go into DEQW status.  I've checked
> and
> > double checked my startup parameters and they are fine.  All the jobs
> seem
> > to go into the TIMW status.
> >
> > It's getting old trying to guess the job that will be running the CGI
> > programming.
> >
> > Has anyone else seen this?
> >
> > 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
> > +---
> >
> > +---
> > | 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
> > +---
> +---
> | 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
> +---
>
> +---
> | 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
> +---
+---
| 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
+---

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