Supported and unsupported object types
Supported and unsupported object types in independent disk pools.
Objects not supported
The following objects are not supported for use in independent disk pools:
| *AUTHLR | *DEVD | *JOBSCD | *PRDLOD |
| *AUTL | *DOC | *LIND | *RCT |
| *CFGL | *DSTMF1 | *MODD | *SOCKET |
| *CNNL | *EDTD | *M36 | *SSND |
| *COSD | *EXITRG | *M36CFG | *S36 |
| *CRG | *FLR | *NTBD | *USRPRF |
| *CSPMAP | *IGCSRT | *NWID | |
| *CSPTBL | *IGCTBL | *NWSD | |
| *CTLD | *IMGCLG | *PRDAVL | |
| *DDIR | *IPXD | *PRDDFN | |
| 1 *DSTMF is the object type that is returned for stream files that are being accessed through the QNTC file system from a remote system. So you should not see *DSTMF ever when accessing the IASP directories from the local system. | |||
Supported object types
The following objects are supported in independent disk pools:
| *ALRTBL | *FILE | *MODULE | *SBSD |
| *BLKSF | *FNTRSC | *MSGF | *SCHIDX |
| *BNDDIR | *FNTTBL | *MSGQ | *SPADCT |
| *CHRSF | *FORMDF | *NODGRP | *SPLF |
| *CHTFMT | *FTR | *NODL | *SQLPKG |
| *CLD | *GSS | *OUTQ | *SQLUDT |
| *CLS | *IGCDCT | *OVL | *SRVPGM |
| *CMD | *JOBD | *PAGDFN | *STMF |
| *CRQD | *JOBQ | *PAGSEG | *SVRSTG |
| *CSI | *JRN | *PDG | *SYMLNK |
| *DIR | *JRNRCV | *PGM | *TBL |
| *DTAARA | *LIB | *PNLGRP | *USRIDX |
| *DTADCT | *LOCALE | *PSFCFG | *USRQ |
| *DTAQ | *MEDDFN | *QMFORM | *USRSPC |
| *FCT | *MENU | *QMQRY | *VLDL |
| *FIFO | *MGTCOL | *QRYDFN | *WSCST |
Restrictions for supported object types
- *ALRTBL
- If network attributes reference the alert table, this object must exist in the system disk pool.
- *CLS
- If an active subsystem references the class object, the class must exist in the library name space of the job that is being started by that subsystem. The library name space of a prestart job must be the same as the library name space of the subsystem job.
- *FILE
- Database files that are either multiple-system database files, or that have DataLink fields that are created as Link Control, cannot be in an independent disk pool. If an active subsystem references the file object, *FILE must exist in the system disk pool; for example, the sign-on display file.
- *JOBD
- If an active subsystem references the job description object, the job description must exist in the system disk pool or in the ASP group parameter of the subsystem description. A subsystem references a job description from an autostart job entry, communication entry, remote location name entry, a workstation entry, or a prestart job entry. When the job description is referenced by a prestart job entry, the INLASPGRP parameter for the job description must match the ASPGRP parameter of the subsystem description.
- *JOBQ
- Jobs that are contained in a job queue on an independent disk pool are ended when the independent disk pool is varied off or if an IPL occurs for the system. Jobs do not switch with the independent disk pool group to another system. To submit a job to a job queue, the job queue must exist in the library name space of the thread that issued the SBMJOB command. For a subsystem to start jobs from a job queue, the job queue must exist in the library name space of the subsystem job.
- *LIB
- The library that is specified by CRTSBSD SYSLIBLE() must exist in the system disk pool.
- *MSGQ
- If network attributes reference the message queue, *MSGQ must exist in the system disk pool.
- *PGM
- If an active subsystem references the program object, the program must exist in the library name space of the job that is being started by that subsystem. The library name space of a prestart job must be the same as the library name space of the subsystem job.
- *SBSD
- The subsystem description can be restored to an Independent Disk Pool and changed while in the Independent disk pool, but it must be copied to the System disk pool to be used. You cannot start a subsystem whose description is in an independent disk pool. You cannot start a subsystem if the ASP group parameter in the subsystem description names an ASP group that is not varied on and available.