IBM MAINFRAME HELP & SUPPORT FORUMS

karthi_ind · Joined: 24 Feb 2004 Posts: 64 Location: Chennai

hi to all

My questions are

1) What is the use of SYSUDUMP, SYSABEND, SYSLIB AND SYSLIN ?

2) Diff. between SYSOUT AND SYSPRINT ?

3) Whatz the use of Typrun=Scan/hold in realtime (give example)?

4) Diff. between JES2 and JES3 ?

5) Whatz the use of SMS ?

superk · Joined: 26 Apr 2004 Posts: 3304 Location: Charlotte,NC USA

Quote:
1) What is the use of SYSUDUMP, SYSABEND, SYSLIB AND SYSLIN ?

JCL Reference for SYSUDUMP and SYSABEND: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B631/13.6?DT=20030423085347

Programming Guide Reference for SYSLIB and SYSLIN (these terms are only relevent to programming, not to JCL): http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IGY3PG00/2.1.4.3?DT=20011203125201

Quote:
2) Diff. between SYSOUT AND SYSPRINT ?

SYSOUT is one of the positional parameters for a DD (Data Definition) statement in the JCL. SYSOUT data is usually directed for either printing or for capture by an archiving utility or the JES spool:
Code: //REPORT DD SYSOUT=(A,,FORM)
SYSPRINT is a common DD name which may or may not be required, depending on the program used:
Code: //SYSPRINT DD SYSOUT=*

Quote:
3) Whatz the use of Typrun=Scan/hold in realtime (give example)?

TYPRUN is not normally used. Check the JCL Reference Guide for descriptions and usage.

Quote:
4) Diff. between JES2 and JES3 ?

An Internet search will yield quite a bit of information. Here is just one example: http://www.mcg-software.dk/pdf/ejes3.pdf

Quote:
5) Whatz the use of SMS

System Managed Storage. Again, plenty of information is available if you perform a search. Here is one such document: http://www.system.missouri.edu/itss/ss/sms/smdoc1.html

vishwanthini · Joined: 15 Oct 2006 Posts: 6 Location: Mooresville,NC-USA

The difference between the JES2 and JES3 is as below
JES2 processing is considered to be independently controlled. Each
JES2 image processes its own job input, job scheduling and job output.
JES2 uses a contention-based paradigm for managing a multi-image
workload. Each image ?wakes up? periodically and attempts to serialize
the JES2 checkpoint using a hardware serialization technique. The image
that succeeds carries out job and output scheduling activities. The others
go back ?to sleep? waiting for another chance. There is no cooperative
decision-making process. The order in which activities occur and on
which images is random.
By contrast, JES3 processing is considered to be centrally controlled.
One image is designated as the focal point for the entry and distribution
of jobs and for the control of resources needed by the jobs. That image,
called the global processor, distributes work to itself and the other images
in the configuration, known as local processors. It is from the global
processor that JES3 manages jobs and resources for the entire JESplex,
matching jobs with available resources. JES3 manages processors
(images), I/O devices, volumes, and data. To avoid delays that result
when these resources are not available, JES3 ensures that they are
available before selecting the job for processing. Using this centralized
approach, JES3 can make informed and complex decisions about job
scheduling and placement.