× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Testing startup program (Was: way to reactivate (IP) ifc automatically?)
  • From: Neil Palmer <npalmer@xxxxxxxxxxx>
  • Date: Thu, 30 Jul 1998 12:29:04 -0600

Actually, you don't have to do a complete IPL to test your startup
program.
>From the console just go to a restricted state (ENDSYS), then when you
are down to a restricted state (check for message in QSYSOPR) just
STRSBS QCTL (assuming QCTL is you controlling subsystem in QCTLSBSD
sysval).
I suggest adding the following line to the beginning of your startup
program:
 CHGJOB     LOG(4 0 *SECLVL) LOGCLPGM(*YES) 
Then after startup you can do WRKJOB QSTRUPJD to check the joblog.



Neil Palmer                                AS/400~~~~~      
NxTrend Technology - Canada   ____________          ___  ~     
Thornhill, Ontario,  Canada   |OOOOOOOOOO| ________  o|__||=   
Phone: (905) 731-9000  x238   |__________|_|______|_|______)   
Cell.: (416) 565-1682  x238    oo      oo   oo  oo   OOOo=o\   
Fax:   (905) 731-9202       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
mailto:NPalmer@NxTrend.com    AS/400  The Ultimate Business Server      
http://www.NxTrend.com

> -----Original Message-----
> From: John Hall [SMTP:jhall@hillmgt.com]
> Sent: Wednesday, July 29, 1998 2:28 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: way to reactivate (IP) ifc automatically?
> 
> rwagner@zeunastaerker.de wrote:
> > 
> > John,
> > 
> > >What was the status of the associated line description used by the
> TCP/IP
> > >interface? (You can get this info by issuing command NETSTAT *IFC
> and then
> > >using list option 12 against this Ethernet interface).
> > 
> > I did not check the status - I simply reipled the machine - did not
> know a
> > better
> > method :-(
> 
> This is not windows NT - for most failures you can simply look in the
> QSYSOPR messages and find the failure and ask the system to retry.  We
> hit the virtual device limit and our windows programmer said "Oh, well
> we'll just have to limit our signon screens until you can change
> that." 
> I said "I just did!"  "You can do that ?"
> 
> Yes!  There are very few reasons you will have to IPL your AS400.
> About
> the only reasons we have is to test the startup program!
> 
> I wish you well with your new AS400.  
> 
> John Hall
> 
+---
| 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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.