The transportability process uses internal tables to keep from duplicating definition of jobs, networks, and other items in the final output. These tables also ensure that a minimum of commands are issued during the intermediate steps of this process.
Each of the three modules executed in the three jobs that constitute this process uses tables for these purposes as follows:
|
Module |
Maximum# |
Component |
|---|---|---|
|
SASSDT10 |
50,000 |
Job names |
|
SASSDT20 |
5,000 |
Application system names |
|
SASSDT20 |
50,000 |
Job names |
|
SASSDT20 |
10,000 |
Workstation network names |
|
SASSDT20 |
300,000 |
CA WA CA 7 Edition assigned data set numbers |
|
SASSDT30 |
50,000 |
Execution JCL member names |
|
SASSDT30 |
50,000 |
Cataloged procedure names |
|
SASSDT30 |
256 |
In-stream procedures (maximum per job) |
All but one of these limits apply to the entire workload definition being moved. The only exception is the limit of in-stream procedures, in SASSDT30, which is the maximum number within any one execution JCL member. (This table is used to distinguish between cataloged procedures and in-stream procedures.)
If any of these limitations are insufficient for any particular move, the user could:
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|