System Variables and User Defined Variables

Windows Server System Environment Variables and User Variables.

Last week I developed an applet program for an xml masking process in Java.. I was referring to an environment variable in my program. When it was tested by clients they reported an IO Exception for which I couldn't find a cause.. Luckily getMessage() function was handy and I had learned that you can set Environment Variables @ User level and @ System Level.. I have set-up that environment variable @ user level and the program had run successfully, when the client tested the variable was not defined and the program failed..

Code snippet to read OS environment variables

Map<String, String> variables = System.getenv();

for (Map.Entry<String, String> entry : variables.entrySet())
{
   String name = entry.getKey();
   String value = entry.getValue();
   System.out.println(name + "=" + value);
}

My First Contribution in Mighty

CALLTREE

a.     Overview of the Tool

          This REXX tool provides the list of static calls details in the given program, this list proceeds to the end of the call tree.

b.     Execution Procedure

·         Include the REXX source code in your XXXXXXXX.REXX.EXEC dataset.

·         The tool in the REXX.EXEC source is directly called using the JCL with the following required data successful execution

1.      Program name

2.      Source PDS: The list of datasets where the tool can look for the called programs in the input program.

3.      Output dataset name.

4.      Exclude PDS: The PDS list containing program that can be avoided from processing by the tool.

·         The output dataset generated in CSV file format need to be downloaded to the local system with .CSV extension in output file name in TEXT mode.

b.     Limitations of the tool

a.      Applicable only for COBOL code.

b.      The tool has no internal logic to identify the DYNAMIC calls.

c.      Scope of the tool

·         The Tool can be used for find the flow of the code till the end point.

·         The Tool also provides the details of the dataset from where the code is taken for processing.

·         The Tool helps in finding the impact of the code changes any where in the flow from the source program to codes down the order to the last code.

·         The Tool can be used to get the call structure of multiple programs in a single run, which will be useful to get the scope of a particular module.