Difference between revisions of "SYSCMDUSNO"

From MidrangeWiki
Jump to: navigation, search
m (Oops ... prior was also minor ... format cleaning up)
m
 
(18 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:CLP/400]]
+
{{delete|a lot of discussion for a pretty simple & meaningless, IMO}}
[[Category:CLP/400 examples]]
+
== Discussion of the Source Code ==
 +
 
 +
This software did NOT come with BPCS or any other packaged software.  [[BPCS]] comes with a Menu Generator where we can add our own [[CLP]] and other programs to be options from these menus.
 +
 
 +
This program is one of a set of related [[CLP/400 examples]].
 +
 
 +
Most sites need to have menu(s) for IT users for easy access to into about what's doing on our system that we ought to know about.
 +
 
 +
We can DSPLOG then F4 but there is grave risk of drowning in information we not interested in, thus as we identify those entries in the log of greatest interest to us, we can place them in a program such as this.  Remember that when you are in DSPLOG or a sub-set of it like this example, you can cursor on any line and F1 for more info, including the message # that this kind of program needs to know to be included.
 +
 
 +
=== What This [[CLP]] Program Does ===
 +
 
 +
This [[CLP/400]] program:
 +
* checks the System Log for events related to Security problems;
 +
* when was the last successful backup;
 +
* any recent changes to System Values;
 +
* any IPL errors;
 +
* stuff that we might think belongs in QSYSMSGQ but it aint there because IBM has a different agenda;
 +
* File Size Churning that may call for us to tweak the file dimension standards. 
 +
 
 +
Note that there is a ceiling on how many scenarios you can put in one picture this way, so make your selections wise ones.  Of course you can always have different menu selections for different kinds of scenarios that interest you.
 +
 
 +
=== Naming Conventions Clarification ===
 +
 
 +
[[BPCS]] security has been rewritten for various versions to apply lessons of the evolving needs of 400 computer security.
 +
 
 +
[[BPCS]] security in some versions is heavily dependent on [[BPCS Naming Conventions]].
 +
 
 +
[[BPCS]] security in Version 405 CD is heavily dependent on the first few characters of software names, so that groups of people are authorized to do certain function sets in certain applications.  So this drives naming conventions for additions to the collection of software.
 +
 
 +
No ordinary user may access SYS system stuff.
 +
 
 +
SYSCMD is an exception at http://www.globalwiretechnologies.com/ whose software prefixed SYSCMD is that which anyone who is authorized to have Green Screen command line access, which are IT staff and some system helpers.
  
 
== Here is the Source Code ==
 
== Here is the Source Code ==
 
+
<pre>
 
/*********************************************************************/  
 
/*********************************************************************/  
 
 
/*                                                                  */  
 
/*                                                                  */  
 
 
/* Program SYSCMDUSNO                            from BPCS Menu      */  
 
/* Program SYSCMDUSNO                            from BPCS Menu      */  
 
+
/*                                                                  */
 +
/* Written by your pal Al Mac, then modified by a host of 400 Gurus  */
 +
/*                                                                  */
 
/*                    Do DSPLOG vs. CPF2234 & other security oops    */  
 
/*                    Do DSPLOG vs. CPF2234 & other security oops    */  
 
 
/*                    and other serious stuff worth checking        */  
 
/*                    and other serious stuff worth checking        */  
 
 
/*                                                                  */  
 
/*                                                                  */  
 
 
/*********************************************************************/  
 
/*********************************************************************/  
        PGM                                                         
+
          PGM                                                         
 
                                                                        
 
                                                                        
 
               DSPLOG    PERIOD((*AVAIL *BEGIN)) MSGID(CPA1E01 +         
 
               DSPLOG    PERIOD((*AVAIL *BEGIN)) MSGID(CPA1E01 +         
Line 23: Line 52:
 
                       CPF0934 CPF0994 CPF0998 CPF1806 CPF2234 +     
 
                       CPF0934 CPF0994 CPF0998 CPF1806 CPF2234 +     
 
                           CPF4058 CPF8192 CPF9E72 CPI1E23 CPI0964 +     
 
                           CPF4058 CPF8192 CPF9E72 CPI1E23 CPI0964 +     
              CPI2203 CPI1479 CPI5970 CPPEA13 MCH1604)                                                     
+
                    CPI2203 CPI1479 CPI5970 CPPEA13 MCH1604)                                                     
 
   
 
   
 
ENDPGM
 
ENDPGM
 +
</pre>
 +
 +
==Categories==
 +
[[Category:CLP/400 examples]]

Latest revision as of 17:41, 18 July 2010

Discussion of the Source Code

This software did NOT come with BPCS or any other packaged software. BPCS comes with a Menu Generator where we can add our own CLP and other programs to be options from these menus.

This program is one of a set of related CLP/400 examples.

Most sites need to have menu(s) for IT users for easy access to into about what's doing on our system that we ought to know about.

We can DSPLOG then F4 but there is grave risk of drowning in information we not interested in, thus as we identify those entries in the log of greatest interest to us, we can place them in a program such as this. Remember that when you are in DSPLOG or a sub-set of it like this example, you can cursor on any line and F1 for more info, including the message # that this kind of program needs to know to be included.

What This CLP Program Does

This CLP/400 program:

  • checks the System Log for events related to Security problems;
  • when was the last successful backup;
  • any recent changes to System Values;
  • any IPL errors;
  • stuff that we might think belongs in QSYSMSGQ but it aint there because IBM has a different agenda;
  • File Size Churning that may call for us to tweak the file dimension standards.

Note that there is a ceiling on how many scenarios you can put in one picture this way, so make your selections wise ones. Of course you can always have different menu selections for different kinds of scenarios that interest you.

Naming Conventions Clarification

BPCS security has been rewritten for various versions to apply lessons of the evolving needs of 400 computer security.

BPCS security in some versions is heavily dependent on BPCS Naming Conventions.

BPCS security in Version 405 CD is heavily dependent on the first few characters of software names, so that groups of people are authorized to do certain function sets in certain applications. So this drives naming conventions for additions to the collection of software.

No ordinary user may access SYS system stuff.

SYSCMD is an exception at http://www.globalwiretechnologies.com/ whose software prefixed SYSCMD is that which anyone who is authorized to have Green Screen command line access, which are IT staff and some system helpers.

Here is the Source Code

/*********************************************************************/ 
/*                                                                   */ 
/* Program SYSCMDUSNO                            from BPCS Menu      */ 
/*                                                                   */ 
/* Written by your pal Al Mac, then modified by a host of 400 Gurus  */ 
/*                                                                   */ 
/*                    Do DSPLOG vs. CPF2234 & other security oops    */ 
/*                    and other serious stuff worth checking         */ 
/*                                                                   */ 
/*********************************************************************/ 
           PGM                                                        
                                                                       
              DSPLOG     PERIOD((*AVAIL *BEGIN)) MSGID(CPA1E01 +         
                       CPC1E1D CPS2356 CPC3707 CPD2609 CPD27EF +     
                      CPF0934 CPF0994 CPF0998 CPF1806 CPF2234 +     
                           CPF4058 CPF8192 CPF9E72 CPI1E23 CPI0964 +     
                    CPI2203 CPI1479 CPI5970 CPPEA13 MCH1604)                                                     
 
ENDPGM

Categories