11.01.2013 Views

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

5.29 Setting the low-level qualifier (LLQ) standards<br />

LLQ naming standards:<br />

ExpDays Max Migrate Cmd/ Retain Retain<br />

Low-Level Non- Ret Partial Days Auto No.GDG Backup Backup Days Day<br />

Qualifier usage Period Release Non-usage Migrate Primary Freqcy Versns OnlyBUP ExtraBUP<br />

ASM...... NOLIM NOLIM YES 15 BOTH -- 0 5 1100 120<br />

CLIST.... NOLIM NOLIM YES 15 BOTH -- 0 5 1100 120<br />

COB*..... NOLIM NOLIM YES 15 BOTH -- 0 5 1100 120<br />

CNTL..... NOLIM NOLIM YES 15 BOTH -- 0 5 1100 120<br />

DATA..... 400 400 YES 15 BOTH -- 2 2 400 60<br />

*DATA.... 400 400 YES 15 BOTH -- 2 2 400 60<br />

FOR*..... NOLIM NOLIM YES 15 BOTH -- 0 5 1100 120<br />

INCL*.... NOLIM NOLIM YES 15 BOTH -- 0 5 1100 120<br />

INPUT.... 400 400 YES 15 BOTH -- 2 2 1100 120<br />

ISPROF... 400 400 YES 30 BOTH -- 0 2 60 30<br />

JCL...... NOLIM NOLIM YES 15 BOTH -- 0 5 1100 120<br />

LIST*.... 2 2 YES NONE NONE -- NONE NONE -- --<br />

*LIST.... 2 2 YES NONE NONE -- NONE NONE -- --<br />

LOAD*.... 400 400 YES 15 BOTH -- 1 2 -- --<br />

MACLIB... 400 400 YES 15 BOTH -- 1 2 400 60<br />

MISC..... 400 400 YES 15 BOTH -- 2 2 400 60<br />

NAMES.... NOLIM NOLIM YES 15 BOTH -- 0 5 1100 120<br />

OBJ*..... 180 180 YES 7 BOTH -- 3 1 180 30<br />

PLI...... NOLIM NOLIM YES 15 BOTH -- 0 5 1100 120<br />

Figure 5-29 Setting the LLQ standards<br />

Setting the low-level qualifier (LLQ) standards<br />

The LLQ determines the contents and storage management processing <strong>of</strong> the data. You can<br />

use LLQs to identify data requirements for:<br />

► Migration (data sets only)<br />

► Backup (data sets and objects)<br />

► Archiving (data sets)<br />

► Retention or expiration (data sets and objects)<br />

► Class transitions (objects only)<br />

► Release <strong>of</strong> unused space (data sets only)<br />

Mapping storage management requirements to data names is especially useful in a<br />

system-managed environment. In an environment without storage groups, data with differing<br />

requirements is <strong>of</strong>ten segregated onto separate volumes that are monitored and managed<br />

manually. LLQ data naming conventions allow data to be mixed together in a<br />

system-managed environment and still retain the separate management criteria.<br />

Figure 5-29 shows examples <strong>of</strong> how you can use LLQ naming standards to indicate the<br />

storage management processing criteria.<br />

The first column lists the LLQ <strong>of</strong> a data name. An asterisk indicates where a partial qualifier<br />

can be used. For example, LIST* indicates that only the first four characters <strong>of</strong> the LLQ must<br />

be LIST; valid qualifiers include LIST1, LISTING, and LISTOUT. The remaining columns show<br />

the storage management processing information for the data listed.<br />

Chapter 5. <strong>System</strong>-managed storage 291

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!