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. | |
Delete processing options
The Delete Processing Options screen shown in the following figure is displayed when you enter the NEXT command on the Delete Confirmation screen.
Delete Processing Options Screen
Command ===>
Extract Dataset Name: TSOID01.FRSAMP.EXTRACT
Discard Processing Options:
Maximum Rows to Discard ===> * (* for no maximum)
Save Discarded Rows ===> YES (Yes or No)
Dataset for Discarded Rows ===> 'TSOID01.DISCARD.DELETE'
Specify Processing Options for DB2 Objects:
Commit Every Nth Row ===> 5000 (1-99999)
Save a Request ===> (Y or N)
Use the NEXT command to continue
Use this screen to specify how often a Db2 COMMIT should be issued, whether or not tables should be locked during delete processing, and options related to discarding rows that could not be deleted. Use the NEXT command to proceed.
Extract File Name
Displays the name of the extract file that the delete process is using.
Discard Processing Options for DB2 Objects Area
Specify the discard options to be used with delete.
Maximum Rows to Discard
Specify the maximum number of errors encountered before processing stops. Specify an asterisk (*) for no maximum or a value greater than 0. Specify 1 if you want processing to stop after any errors are encountered. The discard file need not exist to specify a value in this field.
Save Discarded Rows
Specify whether or not to save rows that could not be deleted.
Yes | Save rows that cannot be deleted in the discard file. If you specify Yes, you must also specify a file in the File for Discarded Rows field. |
No | Do not save rows that cannot be deleted. |
File for Discarded Rows
Specify the name of the file to which discarded rows will be saved. The discard file must be sequential. If you specify Yes in the Save Discarded Rows field and specify a file that does not exist, File-AID/RDX will display the Discard File Allocation pop-up window. The discard file can be used as input to the Db2 delete process if a previous delete job was completed normally, but rows were discarded.
Specify Processing Options Area
Specify the Db2 processing options to be used when deleting Db2 data. This section only displays when there are Db2 objects in the extract file.
Commit Every Nth Row
Specify the number of rows File-AID/RDX should delete before it performs a Db2 COMMIT. This value must be less than or equal to the value specified for the Max Commit Interval installation parameter.
Save a Request
Specify whether or not to save the delete request to a request file.
Yes | Save the current delete request information to a request file. File-AID/RDX presents the Save Delete Request panel where you identify the delete request file to save your request to. |
No | Do not save the current delete request. |
Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:
NEXT
The NEXT command invokes the next screen in the delete process. If you specified a discard file that does not exist, the Discard File Allocation pop-up window is displayed next. If you specified a discard file that already exists, the Edit Delete JCL screen is displayed. There are no operands associated with this command.
Discard file allocation
The Discard File Allocation pop-up window shown in the following figure is displayed when you specify a non-existent discard file on the Delete Processing Options screen.
DISCARD File Allocation Pop-Up Window
Use this window to specify the characteristics of the discard file to be allocated. Press ENTER to proceed.
Discard File
Displays the name of the file to which discarded rows will be written. For more information about the discard file, see Discard File.
VOLSER
Specify the volume serial number of the file. A volume serial number is optional.
Generic Unit
Specify the device type on which the new file will reside. The names of these devices are installation dependent.
Block Size
Specify the block size for the new file. You can specify BLKSIZE=0 for systems that support it. This causes the system to determine an optimum block size.
Space Units
Specify whether space for the new file will be allocated in blocks (BLK), tracks (TRK), or cylinders (CYL).
Primary QTY
Specify the initial number of space units that will be allocated for the new file.
Secondary QTY
Specify the number of space units that will be allocated for each secondary extent.
Primary Commands
The following File-AID/RDX-specific primary command is valid in the Discard File Allocation window.
NEXT
Opens an edit session on the Delete JCL generated by File-AID/RDX. There are no operands associated with this command.
Save delete request
The Save Delete Request panel shown in the following figure is displayed when you specify Y in the Save a Request field of the Delete Processing Options Screen.
Save Delete Request
COMMAND ===>
Specify Delete Request File Information:
File name ===> FRSAMP.EXTCRIT
Member ===>
Description ===>
Use this screen to save the current delete request information.
Press Enter to process the file information. The saved request will also appear in your Delete Reference List (see Delete Reference List).
The body of the Save Delete Request screen consists of the following fields:
File Name
Specify the name of the file where you want to save the delete request. You can save the request to existing files. Existing files must conform to the format outlined for the request file in File-AID/RDX Extract/Load/Delete Request File.
If you specify a new file, you must specify the following allocation parameters in the Create New File screen.
Member
If the file is partitioned, specify the name of the member to contain the delete request.
Description
Enter a short description of the delete request. This description is displayed in the Delete Reference List. Using this description is a helpful way to document your delete request.
SAVE Confirmation
When saving an Extract, Delete or Load request File-AID/RDX checks to see if the member already exists. If the member already exists, the Save Confirmation window displays:
Save Confirmation window
Viewing delete JCL
The ISPF/PDF VIEW screen shown in the following figure is displayed when you enter the NEXT command on the Delete Processing Options screen or the Discard File Allocation pop-up window.
ISPF/PDF VIEW Screen
COMMAND ===> SCROLL ===> HALF
You are now editing the JCL that File-AID/RDX has generated to perform
the required function. Change this JCL as desired before submitting.
SYSIN data is contained in: TSOID01.RDX.FBCNTL.D080202.T115332
TSOID01.RDX.VBCNTL.D080202.T115332
****** ***************************** TOP OF DATA ******************************
000004 /* XFRJDLT1
000005 //*SQLID TSOID01 IS UNAUTHORIZED TO:
000006 //* DELETE ROWS FROM TABLE FRSAMP.ORDER_TABLE
000007 //* DELETE ROWS FROM TABLE FRSAMP.ORDER_LINE_TABLE
000008 //* DELETE ROWS FROM TABLE FRSAMP.PART_TABLE
000009 //* XFRJSTRD
000010 //*-------------------------------------------------------------------
000011 //* CLEAN1ST: - THIS STEP WILL ENSURE THAT ALL TEMPORARY DATASETS
000012 //* USED IN THIS JOB ARE DELETED.
000013 //* - THIS ALLOWS FOR KEEPING AND RERUNNING THE JOB EVEN IF
000014 //* SUBSEQUENT STEPS FAIL.
000015 //* - THIS JCL IS ALSO RESTARTABLE AT
000016 //* RESTART=XXXXXXXX ON THE JOBCARD.
000017 //*-------------------------------------------------------------------
000018 //CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048
000019 //SYSPRINT DD SYSOUT=*
000020 //SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
Use this screen to edit and submit the delete JCL generated by File-AID/RDX.
If you want to save this JCL, use the ISPF/PDF CREATE or REPLACE command before you exit this screen. Otherwise, File-AID/RDX deletes this file and other temporary files, including the control card PDSEs (prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix and prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix) (see Control Card Cleanup).
Submit this JCL with the SUBMIT command to perform the delete.
Control Card Cleanup
The last 2 steps, CLEANCTL and CLEANEXT, in the load and delete jobs delete the File-AID/RDX control card PDSEs and EXTPARMS parameter files. Whether steps CLEANCTL and CLEANEXT are commented out or executed is determined by the global job option Delete in-stream data datasets at EOJ. If the job option is set to NO, File-AID/RDX control card PDSEs and EXTPARMS parameter files created in the load and delete jobs will NOT be deleted. Keeping the data sets until all steps run successfully allows for the restarting of the JCL at any step.
Periodically, you may want to manually delete the control card PDSEs and EXTPARMS parameter files that are no longer needed for saved jobs to be resubmitted.
Related topics