|
|
|
In general, define a separate table for each type of resource instead of mixing different resource types in one table. This approach ensures that most of the columns in each table are specific to a particular resource.
For example, suppose that your company has a remote warehouse that uses a CICS-based inventory application. This type of application requires a cluster controller at the remote site, an SNA communications line, a 3745 communications controller, the CICS region, VTAM, and JES. With all of these resources defined in one table, certain data items required for the communications controller (NCP name, for example) or CICS region (JOBNAME) would be null for other resources and would waste space in the table. Wasted space is the main disadvantage of defining too few tables.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |