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




I have some questions regarding the start-up program (QSTRUP), of which the
IBM docs did not answer.  (Note that we have retrieved the source from
QSYS/QSTRUP and modified that source, compiled it in a user library, and
changed the system value QSTRUPPGM to point to that program.)

1.  Can I safely use CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES) in this
program?
We made a change to this program that supposedly did not do what it was
supposed to, but we have no record of whether or not this is true.  We
would
like to be able to look at the job log for the startup program to check
this.

This should be ok.

2.  When I insert new commands to run, I believe I need to at least
duplicate
IBM's effort to monitor for escape messages.  IBM uses MONMSG
MSGID(CPF0000) .
 Is that enough?  I thought I have seen in the past where the absolute
catch-all MONMSG monitored for CPF0000, CPF9999, & MCH0000.  Yea or nay?
What
happens if a command fails and a message is issued waiting for a reply?
Will
the console ever show a signon screen?

I think that MONMSG CPF0000 is sufficient.

3.  Doesn't it seem odd that IBM qualifies all the commands except the
MONMSG,
IF, CALL, and others?  Don't these also have the same exposure to being
"hijacked" by another library higher than QSYS in the library list?  Is it
possible to have a library higher than QSYS during the normal execution of
this command at IPL?  (Possibly the QSYSLIBL system library list?)

This is IBM new paranoid thing where they want to qualify every command to
QSYS "for your protection".  This IMHO has proven to be a fiasco.  It
certainly has screwed up many third party vendors.  My opinion is to do
whatever you want here.

Two parting words of advice here:

1).  This program is release sensitive, so check for changes on each
release.
2).  Most people start TCP/IP in their startup programs, which is good.  In
V5R1 the starting of TCP/IP has been turned into an IPL attribute, but the
default is not to start it as an IPL attribute.  You might chose to move
the starting of TCP/IP out of your start-up program in V5R1, and change to
the IPL attribute.

Al  -  in London for COMMON Europe  (It's a tough job, but somebody's...)

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.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
+---

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.