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



Anyone remember the GETSYSINFO program that Jeff at Dilgard Foods shared
with us.
http://archive.midrange.com/midrange-l/200304/msg01902.html

I implemented it that day.  From this thread it occurred to me to add
the PRTSYSINF output to the saved information.
There is probably some overlap between the RTVSYSINF and the PRTSYSINF,
but I couldn't find the system values on the RTVSYSINF output.  

What do you all think, is this overkill?

             CLROUTQ    OUTQ(SYSTEMINFO/PRTSYSINF) /* 6/20/2003 - +
                          output from PRTSYSINF */                 
              MONMSG     MSGID(CPF0000)                            

<< Jeff's original program is here >>
<< + Rob's suggestion for RTVCFGSRC >> 

/** 6/20/2003 ** ADD PRTSYSINF FOR SYSTEM VALUES, ETC **/           
/**  NOTE: USES GENERIC SOFTWARE SAVOUTQ TO SAVE SPLFS **/          
                                                                    
             CRTOUTQ    OUTQ(SYSTEMINFO/PRTSYSINF) RMTSYS('output + 
                          from PRTSYSINF command')                  
             CRTSAVF    FILE(SYSTEMINFO/PRTSYSINF) TEXT('saved +    
                          spooled output from PRTSYSINF')           
             CHGJOB     OUTQ(SYSTEMINFO/PRTSYSINF)                  
                                                                    
             PRTSYSINF                                              
                                                                    
             SAVOUTQ    OUTQ(PRTSYSINF) OUTQL(SYSTEMINFO) +         
                          SAVFNM(SYSTEMINFO/PRTSYSINF)              


"Jones, John (US)"
<John.Jones=nLzMa1qvDZ/sHjKUpOl6B2sBamAEyd5Q@xxxxxxxxxxxxxxxx> wrote
in message
news:<CA1C7D9DF382FA42A70529E9E20A52B3AB26@xxxxxxxxxxxxxxxxxxxxxx>...

> Towards that end, I would recommend using PRTSYSINF periodically. 
At
> least whenever new subsystems are created, system values changed,
and
> immediately before and after an OS upgrade.  You rarely need to refer
to
> it, but it can be a godsend when trying to track down changes to
system
> values, subsystem descriptions, etc.
> 
> What I've found to work best is to not actually print it out,
though.
> Generate it and use OpsNav/iNav to copy the spool files to a
directory
> on your PC.  They are much more easily searched using Windows file
> search capabilities that manually scanning the spool files online. 
If
> PC space is a concern, you can zip them.
> 
> I know that doesn't help much with the immediate problem, but
perhaps
> some changes can be spotted by running through a current PRTSYSINF.
> 
> - John
> 
> -----Original Message-----
> From: Andy Nolen-Parkhouse
[mailto:aparkhouse=K2GnTyEPumIAvxtiuMwx3w@xxxxxxxxxxxxxxxx] 
> Sent: Tuesday, June 17, 2003 9:43 AM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Security
> 
> 
> >Good luck, I don't think that there is an easy answer to this one,
> unless you listed out your system values not to long ago.
> 
> >Regards,
> >Andy Nolen-Parkhouse
> This e-mail is for the use of the intended recipient(s) only.  If you
have received this e-mail in error, please notify the sender immediately
and then delete it.  If you are not the intended recipient, you must not
use, disclose or distribute this e-mail without the author's prior
permission.  We have taken precautions to minimize the risk of
transmitting software viruses, but we advise you to carry out your own
virus checks on any attachment to this message.  We cannot accept
liability for any loss or damage caused by software viruses.
> 
> 
> 
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
> To post a message email:
MIDRANGE-L=Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request=Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxxx

> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 
THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH 
IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL 
AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the reader of this message 
is not the intended recipient, or the employee or agent responsible for 
delivering the message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, downloading, storing or forwarding of 
this communication is prohibited.  If you have received this communication in 
error, please notify us immediately via email and delete the message from your 
computer files and/or data base.  Thank you.

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.