Child pages
  • EISCD Setup Procedures

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In order to provide web access to the district using OSU, the ITC will need to do the following:
1. First, add rules to the www_system:http_paths.conf file (or an included file). The following is an example:

Code Block
   protect /eiscdrom/district1/\* www_system:eiscdrom_district1.prot
  pass /eiscdrom/district1/\* /eis$cdrom/district1/\*
 

...

2. The second step to provided web access to the district is to create the EISCDROM_DISTRICT1.PROT file for each district. This is the file the OSU server will read to determine what access limitation to place on the URL path. There are a number of options within the OSU’s authenticator, including hardcoded username and passwords, VMS usernames and passwords, or VMS ACL’s. The following is an example of what a .prot file might look like:

Code Block

<realm>district1 Fiscal Records
username *

...

The ITC can provide additional custom reports by placing two procedures called EISCD_CUSTOM_REPORTS.COM and BLD_EISCDINDEX_CUSTOM.COM in the OECN$CUSTOM directory.  The EISCD_CUSTOM_REPORTS.COM procedure must accept the following four parameters and generate the desired reports in .TXT and .PDF format.

Code Block

P1 = District Name
P2 = Period Start Date in MMDDYYYY format
P3 = Period End Date in MMDDYYYY format
P4 = Output Device and Directory

The BLD_EISCDINDEX_CUSTOM.COM procedure must contain a series of "if" statements checking the global symbol "file" and assigning a global symbol "title" to each .PDF file generated in the EISCD_CUSTOM_REPORTS.COM procedure. For example:

Code Block

$ if file .eqs. "EIS001.PDF" then title == "EIS Code Listing"
$ exit

...

When running interactively, the procedure will prompt for whether the user wishes to include or exclude entity ids in those programs that allow this functionality. In batch mode, if you wish to include or exclude specific entity ids, you will need to create a file containing the entity ids. The first line of this file should say either "INCLUDE" or "EXCLUDE". Subsequent lines should list the entity ids you wish to include or exclude. This file can either be called oecn$eiscd_entities.dat and placed in the district’s oecn$eis$dta directory, or the logical OECN$EISCD_ENTITIES can be defined to point to this file. For example, a sample oecn$eiscd_entities.dat file might look like:

Code Block

EXCLUDE
NOGAAP

Parameters

The EISCD procedure accepts several parameters, as described below.  Some of these parameters can be used to optionally run the procedure in batch mode to generate current reports or to more easily generate fiscal reports from archived fiscal year-end files.

...

Code Block
SUBMIT EISCD.COM/PARAM=(FISCAL,"",dev:\[fyrdir\],dev:\[dir.district1\])

Where the third parameter points to the directory containing the fiscal year-end archive files to run against, and the fourth parameter points to the district’s top level directory set up to store the resulting reports. In this case, if you were running for fiscal year 2009, the procedure would create the directory dev:[dir.district1.f2009.] and place the resulting reports into this directory for archival purposes.

...

Code Block
SUBMIT EISCD.COM/PARA=(CURFISCAL,"",dev:\[livedir\],dev:\[dir.district1\])

In the example above, the third parameter would contain the device and directory of the district’s live EIS files, and the fourth parameter would be the district’s top level directory set up to store the resulting reports. In this case, the procedure would create the directory
dev:[dir.district1.current_fiscal] and generate a set of reports from the beginning of the fiscal year through the current date and placed in the directory dev:[dir.district1.current_year].  In all cases, the appropriate links will be created on the INDEX.HTML file(s) to allow web access to the newly created directories and reports.

...

Code Block
@OECN$EIS:BLD_EISCDINDEX_TOP dev:\[dir.district1\] "Sample District" ALL