Re: Editing Startup program on as/400

[Chuck Lewis <CLEWIS@xxxxxxxxxx>]

OK ! I get it (authority vs timing..) :-) Just wanted to be clear there. The 
way we run the
startup program there shouldn't be ANY authority problems.

So, what ARE the motives to the madness <BG>

Thanks !

Chuck

Mike Shaw wrote:

> Chuck,
>
> No, the delay is a good idea...You have to give the STRTCP a chance to finish 
>starting all of the servers.  I indicated that in my reply to Gary this 
>morning. However, if the authority is not there to run STRHOSTSVR in the 
>startup program, the delay does not matter!  =:-)
>
> The whole concept of host servers takes some getting used and it is weird 
>until you understand the motives in the madness.
>
> Mike Shaw
>
> ----------
> > Mike,
> >
> > Are you saying that the delay job (from STRTCP to STRHOSTSVR) is NOT 
>necessary
> > and that the problem is TOTALY the authority deal ?
> >
> > The way that whole deal works is weird/a pain...
> >
> > When Host Servers/Services stops (i.e. at IPL) I get messages about all of 
>the
> > jobs ending; but NEVER get any information that they started when they start
> > AFTER IPL...
> >
> > I also never see any job logs or anything in the start up job log...
> >
> > I know you can look at the active jobs and find the stuff,  but it seems
> > inconsistant with the way other stuff works...
> >
> > Chuck
> >
> > Mike Shaw wrote:
> >
> > > Gary,
> > >
> > > It really has nothing to do with the changes you made to the startup
> > pgm...It's the authority needed to run STRHOSTSVR that is causing you to 
>start
> > it manually.  Your startup program runs under the user QPGMR.  You will have
> > to edit the object authority for STRHOSTSVR and give QPGMR *USE rights to 
>it.
> > Once you have done that, it should run just fine via the startup program.
> > >
> > > HTH
> > >
> > > Mike Shaw
> > >
> > > ----------
> > > > Sorry for the wrong subject line.  Here's the real one.
> > > > Gary Lehman
> > > > Programmer Analyst
> > > > Missouri Consolidated Health Care Plan
> > > >
> > > >               -----Original Message-----
> > > >               From:   Gary Lehman [mailto:Gary_Lehman@mail.mchcp.org]
> > > >               Sent:   Tuesday, June 16, 1998 2:25 PM
> > > >               To:     'MIDRANGE-L@MIDRANGE.COM'
> > > >               Subject:        RE: Passing numeric fields to COBOL 
>program
> > > >
> > > >               Hello,
> > > >
> > > >               This may be delving deep into the system, but has anyone
> > > > ever edited the
> > > >               QSTRUP program in QGPL library?  It's the system start up
> > > > and I had to
> > > >               modify it to call our START program so as to start TCP/IP
> > > > and do STRHOSTSVR
> > > >               whenever we bring it down.  However, lately it seems like
> > > > after it comes
> > > >               back up TCP/IP comes up but the Host servers do not.
> > > > Consequently, I have
> > > >               to start the servers manually.  Does anyone know where the
> > > > messages go for
> > > >               QSTRUP so I can look at them?  I'd like to see if I could
> > > > find out if its
> > > >               actually hitting certain parts of the CL.
> > > >
> > > >               Thanks
> > > >               Gary Lehman
> > > >               Programmer Analyst
> > > >               Missouri Consolidated Health Care Plan
> > > >               +---
> > > >               | 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
+---