Memorex LOCK - VERSION 2-24 Technical Information PDF herunterladen (Seite 299)

100

101

CPU and Partition Independence

User Reference

Use Pursuant to Company Instructions

7-31

CPU and Partition Independence

Description CPU and partition independence are normally used with work datasets.

CPU and partition independence allow you to use a single set of JCL to

run in any partition or CPU. Because BIM-EPIC inserts a partition and/or

CPU ID into the dataset name to make the dataset name unique, there is

no duplication of the dataset names in different partitions or machines.

For example, in your JCL you could specify ===.SORTWRK1 as the

dataset name. The three equal signs (=) designate both CPU and partition

independence. When you run the job in the BG partition of CPU ID 1,

BIM-EPIC uses the dataset name BG1.SORTWRK1. When you run the

job in the F4 partition of CPU ID 2, BIM-EPIC uses the name

F42.SORTWRK1.

DSN Catalog When using the “===.” format, you must catalog a separate dataset

definition for each partition/CPU ID combination you intend to use.

When cataloging your dataset, specify the partition/CPU ID first, then a

period, and then the dataset name. Using the previous example, the

catalog names would be BG1.SORTWRK1 and F12.SORTWRK1. When

using both CPU and partition independence, the partition ID precedes the

CPU ID.

When using Common Work Datasets (CWDS), it is not necessary to

catalog a separate dataset definition for each partition/CPU ID

combination used. You may also choose to use CWDS for temporary

datasets, especially compiler work files, such as IJSYSnn. However,

since they are deleted at end-of-job, they may not be appropriate for

everything.

JCL

Requirements

There are several JCL requirements you must consider.

 For both DLBL and DD statements, you must prefix your dataset

name with at least one equal sign (=) and a period (.). For

example:

 The “=” and “.” are part of the 44 character dataset name.

 For DD statements, you can substitute two ampersands (&&) for

the equal signs and omit the period. If you are concerned about

MVS compatibility, using the ampersands can be an advantage

because ampersands signify a temporary dataset to MVS.

Format Specifies...

=.dataset.name CPU independence only

==.dataset.name Partition independence only

===.dataset.name Both CPU and partition independence

1 2 ... 294 295 296 297 298 299 300 301 302 303 304 ... 567 568

Kommentare zu diesen Handbüchern

Keine Kommentare

Memorex LOCK - VERSION 2-24 Technical Information Seite 299

Kommentare zu diesen Handbüchern