Home  |  Suggestion Box  |  MSU Home Page  |  Database Info

Administrative Information Services - Data Administration

Client Based Computing Environment

The current Client Based Computing batch environment consists of a program editor "SYSD" (CICSCBC on the VTAM menu) and an output display facility "SAR", two programming languages VISION:Results (formerly known as "DYL") and SAS, and a JES output environment that includes several job classes with defined service levels dedicated to Client Based Computing batch throughput. Each of these tools plays an important role in the flexibility of the Client Based Computing batch environment that is supported at Administrative Information Services.

SYSD is the program editor that is supported for Client Based Computing. SYSD is an ISPF-like product that is installed in a CICS region especially for Client Based Computing called CICSCBC. The region CICSCBC is directly accessible from our VTAM front-end menu. Currently, SYSD supports browsing and editing of any PDS dataset or Panvalet library that a client has the appropriate security to read or update. Clients can add/change/delete or submit batch programs from SYSD.

SAR is a Sysout Archive and Retrieval product used at Administrative Information Services. A special SAR environment is supported for Client Based Computing called SARC. SARC is directly accessible from our VTAM front-end menu. Currently, SAR is used in Client Based Computing to view all program HASP's and report output for JCL or program errors prior to sending report output to print. Clients can choose to print report output from SARC or they can specify a direct to printer option when submitting their jobs for execution. Output contained in SARC is saved for three days before being automatically deleted. Clients can also delete their output at any time they choose prior to the three day expiration.

VISION:Results (formerly DYL) is a COBOL-like language that is used in the majority of client jobs executed. VISION:Results is a report generation language and also supports some basic audit and statistical routines. VISION:Results has the capability to read/write sequential disk, tape or VSAM datasets without conversion to special file formats and it also has the capability to read IDMS LRF subschemas. VISION:Results supports the capability to verify program syntax without execution. Use OPTION VERIFY for syntax check (remember to remove this when you want the job to actually execute).

SAS is a statistical analysis language that is used by a growing population of client jobs to support complex statistical analysis and reporting. SAS is a more CPU-intensive language, partially because it must convert input files into a special SAS format. SAS as implemented at Michigan State University does not have the ability to read IDMS LRF subschemas. For syntax check use OBSERVATIONS=0.

JES is primarily a sysout dataset processor. It allows the user to examine the status of all jobs that are present in the system. Individual jobs can then be selected for more detailed examination. Specific sysout datasets or groups of datasets can be selected for browsing. Standard ISPF browse is used for scanning of sysout data and therefore all standard browse commands and facilities are available. Once data has been examined, JES can be used to change the disposition of the sysout data. The attributes of each dataset or the entire job can be modified. Characteristics such as destination, sysout class, forms and so on may be modified before the data is released for printing. Try using J in the SEL column in your output list (SARC) to bring up the print attribute panel. If only a portion of the job's data is required, it is possible to print only those portions by specifying the page ranges in the Print Attribute Panel. Unwanted output can be deleted.

Job Class used in the Run Member (e.g. xxxDYLRUN) or in the JCL at the front of your program (the Job Card) determines how many tape datasets can be used and how long it may take to initiate the start of the program run.

Job Classes available for CLIENT BASED COMPUTING use  

Job Class

(class=    in job card)

CPU limit Max Tapes allowed* Wait-Time** Charged?
5 15 seconds 0 20 minutes No charge for courtesy clients. True-bill clients pay for consumables.
4 15 seconds 2 20 minutes (see above)
I 65 seconds 3 35 minutes (see above)
6 30 minutes 3 Overnight (see above)
J 30 minutes 3 Premium (fast) All clients fully charged

  *Under special circumstances, more than 3 tape drives can be used in classes 6 and J but Client Based Computing must be notified ahead of time so that proper arrangements can be made.

**Wait-time is the amount of time elapsed from the time a job is submitted until it starts. The average wait-time will be much lower than the time stated above. The times stated above are the 95% service level which means that 95% of the time a job should start within the period stated.


Michigan State University Copyright 1998.  All rights reserved.    This page last updated on 06/12/01 04:17 PM.

  If you have comments or suggestions about this webpage Email us.    (Please do not change the subject line)