Writer instructions | ||
Purpose | Use this page to display a banner announcement on each page of the space. Create the Space announcements page in the master space, outside of the Home branch. You can version the Space announcements page to enable different banners to be published into different target spaces, however, the banner that is displayed in the versioned (master) space itself only displays the most recently-published banner. If you find errors in the banner area of your versioned space and you are sure the Space announcements page is set up correctly, try publishing the page to the same space. For more information, see Space-announcements-banners. | |
Removing | When an announcement is no longer needed, remove the BMC Space Banner macro. | |
Translation | Localized spaces using the L10n Viewport theme must change the name of this page to Space announcements l10n. See Configuring-the-Scroll-ViewPort-theme-for-translated-spaces. | |
Usage | Choose one or none of the following BMC Space Banner macros. If your space requires another kind of announcement, you can use this page in coordination with your team lead and editors. | |
FLEX JCL
File-AID for IMS/FLEX is invoked through standard MVS JCL. The main program is passed a parameter that is similar to a standard IMS parameter string. The following JCL identifies the parameters and DD statements required to execute File-AID for IMS/FLEX.
JCL - Execute File-AID for IMS/FLEX
PARM Field
The execution parameters in the PARM field of the EXEC statement are similar to a standard IMS parameter string. The format of the execution parameters is determined by the execution environment of DLI or BMP.
DLI Environment
// &SPIE&TEST&EXCPVR&RST,&PRLD,
// &SRCH,&CKPTID,&MON,&LOGA,&FMTO,
// &IMSID,&SWAP,&DBRC,&IRLM,&IRLMNM,
// &BKO,&IOB,&SSM,&APARM’
All database datasets must be in the JCL or dynamically allocated; they cannot be intermixed.
BMP Environment
// &PSBNAME,&IN,&OUT,
// &OPT&SPIE&TEST&DIRCA,&PRLD,&STIMER,
// &CKPTID,&PARDLI,&CPUTIME,&NBA,&OBA,
// &IMSID,&AGN,&SSM,&PREINIT,&ALTID,&APARM’
In either environment, the mode operand determines the type of PSB processing that File-AID for IMS/FLEX will use. The mode operand has the format of xyyyy,
where... | equals... |
|---|---|
x | S (staticl.) or D (dynamic) PSB usage. If a static PSB is used, then the &PSB operand specifies the name of the pre-existing PSB. If a dynamic PSB is used, then the &PSB operand specifies the name of the DBD to be processed. |
yyyy | For a DLI region, this field must be present but is not used. For a BMP region, yyyy identifies the File-AID IPRMS BMP entry to use. |
Refer to IMS/ESA System Definition Reference for the definitions of the other parameters.
The DD statements shown in the following table are required for the XIXBATDV program to execute.
DD Statements for XIXBATDV
DD Statement | Description |
|---|---|
STEPLIB | The IMS system data sets that contain the IMS nucleus, required action modules, and the library where the File-AID for IMS/ISPF load modules are stored. Remember to concatenate the customized (CXIXLOAD) and target (SXIXLOAD) load libraries. |
DFSRESLB | The IMS system data sets that contain the IMS nucleus and required action modules. |
IMS | The PSB load library data set (that contains the PSB member) and DBD load library data set (that contains DBD members) that describe the databases. |
IEFRDER | The IMS log data set. This DD is not required for BMP jobs. |
DFSVSAMP | The data set that contains the control statements that describe the buffer pools used by IMS. This DD is not required for BMP jobs. |
IXPMLIB | File-AID for IMS message data set. |
SYSOUT | All File-AID for IMS/FLEX reports are written to this DD statement. |
IXPSTATS | The DD statement that contains the File-AID for IMS/FLEX Execution Summary report and any error messages. |
DB data sets | (Optional) These DDs are not required for BMP or IRC extract job types. For DLI job types, the DD statements are either included as actual DD statements or they are included as comments. If all the database dataset names were obtained from the IMS dynamic allocation source, then a DD DUMMY statement with DD name IXPIMSDY is included to indicate this. The DD statements for the database datasets are included as comments only. When the JCL is submitted, the current data sets will be dynamically allocated by File-AID for IMS using the IMS dynamic allocation source to obtain the names. If all the data set names were not obtained from the IMS dynamic allocation source, then the IXPIMSDY DD statement is included as a comment only and the database dataset DD statements are included as true DD statements. |
IXPFD | The data set that contains the File-AID for IMS segment to layout XREF members. Required, even when XREF=NONE is specified. |
IXPC1 | The first data set that contains the COBOL or PL/I layout members. |
IXPC2 | The second data set that contains the COBOL or PL/I layout members. |
IXPED | The data set that contains the command statements used by File-AID for IMS/FLEX. The data set must have the following attributes:
If DSORG=PO, a member must be included in the specification of the dataset name. |
IXPAT | (Optional) Specifies the desire to create an audit trail dataset. See Audit-trail-facility. |
IXPIN | (Optional) The data set that will supply the input values for the INPUT(start,length,type) parameter. This data set must have a DSORG attribute of PS or PO. |
IXPOUT | (Optional) The data set that will contain the concatenated keys of those segments designated with the OPTION=CKEY keyword of the COUNT command. The data set must have the following attributes:
|
EXTRACT1 through EXTRACT 5 | (Optional) The data set(s) that will contain output from the field level extract corresponding to the EXTRACTn FLEX subcommand with the same name as the DDNAME. Each EXTRACTn data set must have the following attributes:
|
LAYOUT 1 through LAYOUT 5 | (Optional) The data set(s) that will contain layouts generated for each field level extract for which a LAYOUTn FLEX subcommand is used. Each LAYOUTn data set must have the following attributes:
|