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	*JOBQ	*PRDDFN
*AUTL	*DOC	*JOBSCD	*PRDLOD
*CFGL	*DSTMF1	*LIND	*RCT
*CNNL	*EDTD	*MODD	*SOCKET
*COSD	*EXITRG	*M36	*SSND
*CRG	*FLR	*M36CFG	*S36
*CSPMAP	*IGCSRT	*NTBD	*USRPRF
*CSPTBL	*IGCTBL	*NWID
*CTLD	*IMGCLG	*NWSD
*DDIR	*IPXD	*PRDAVL
1 *DSTMF is the object type returned for stream files that are being accessed through the QNTC file system from a remote system. So you shouldn't see *DSTMF ever when accessing the IASP directories from the local system.

 

Supported object types

The following objects are supported for use in independent disk pools:

*ALRTBL	*FILE	*MSGF	*SCHIDX
*BLKSF	*FNTRSC	*MSGQ	*SPADCT
*BNDDIR	*FNTTBL	*NODGRP	*SPLF
*CHRSF	*FORMDF	*NODL	*SQLPKG
*CHTFMT	*FTR	*OUTQ	*SQLUDT
*CLD	*GSS	*OVL	*SRVPGM
*CLS	*IGCDCT	*PAGDFN	*STMF
*CMD	*JOBD	*PAGSEG	*SVRSTG
*CRQD	*JRN	*PDG	*SYMLNK
*CSI	*JRNRCV	*PGM	*TBL
*DIR	*LIB	*PNLGRP	*USRIDX
*DTAARA	*LOCALE	*PSFCFG	*USRQ
*DTADCT	*MEDDFN	*QMFORM	*USRSPC
*DTAQ	*MENU	*QMQRY	*VLDL
*FCT	*MGTCOL	*QRYDFN	*WSCST
*FIFO	*MODULE	*SBSD

 

Restrictions for supported object types

*ALRTBL

If network attributes reference the alert table, this object needs to exist in the system disk pool.

*CLS

If an active subsystem references the class object, *CLS must exist in the system disk pool.

*FILE

Database files that are either multiple-system database files, or that have DataLink fields that are created as Link Control, cannot be located 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, *JOBD must exist in the system disk pool; for example, autostart job entry, communication entry, remote location name entry, or workstation entry.

*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 needs to exist in the system disk pool.

*PGM

If an active subsystem references the program object, *PGM must exist in the system disk pool; for example, routing entries and prestart job entries.

*SBSD

You cannot start a subsystem whose description is located in an independent disk pool.

 

Parent topic:

Planning for independent disk pools

Related concepts
Application considerations for independent disk pools