|
Results |
|
FDM: Can cylinders or tracks be added to a VSAM file?
FDM: Can cylinders or tracks be added to a VSAM file?
|
|
|
free tracks incorrect for MOD54 in 3.4 listv display
free tracks incorrect for MOD54 in 3.4 listv display
|
|
|
Missing Trailing 'T' in DSNAME LISTC LISTF VMAP INFO and 3.2 for data sets 1,000,000 tracks and larger in FDM 7.8.1
Missing Trailing 'T' in DSNAME LISTC LISTF VMAP INFO and 3.2 for data sets 1,000,000 tracks and larger in FDM 7.8.1
|
|
|
'TEST IAM IS ACTIVE' in CONTROL TESTTRACE command
Beginning in FDM 7.8.1, CONTROL TESTTRACE command is showing an entry for ‘TEST IAM’. Note: IAM is not active when the trace is run. ------>control testtrace Columns 00001 00072
|
|
|
FDM: COPYPREP CLIST operates as if CHECK parameter is always enabled
* move the following statements that have arrows in the following order: 003400 Trace "o" /* WAS o */ 003500 Parse Upper Arg dsn1 dsn2 CHECK debug
|
|
|
FDM730: ML against large PDSE results in S0F4 and S0C4 errors
Analysis of the trace table from the supplied dump shows an SVC 120, GETMAIN request, for 32K below the 16MB line. This fails with a return code of four. The next entry in the trace table shows an ABEND S0F4 issued immediately following the GETMAIN failure.
|
|
|
FDM: DASDVOL error using FIXPDS
Attempted to use FIXPDS to add a secondary amount of 10 tracks to a dataset. Receive a RACF error message that "read" authority to the volume (DASDVOL authority) is needed instead of authority at the dataset level. Also received, in the FIXPDS screen, a message " DASDVOL prevents PDSEAUTH updates to the VTOC".
|
|
|
FDM: Are you sure your backups are usable?
A user was backing up his MVS PROCLIB using a utility that backs up physical tracks to a generation data group. During quarter end processing it was discovered that a number of PROCs were corrupted. The user restored from the backup only to discover that those members were in the same condition.
|
|
|
FDM: Restrict users from using certain FIXPDS functions
Product: StarTool-FDM Problem: RACF security has been set up to restrict users from using FIXPDS; however, they are still able to perform certain functions like adding tracks to the dataset.
|
|
|
LISTC, USAGE and INFO incorrectly display ALLOCATED SPACE for very large datasets
For large datasets that exceed 999999 tracks , FDM is not displaying the higher order byte for ‘Allocated space’ which is displayed in tracks . In the example below, the allocated space should be 1460340. FDM 3.2 display
|
|
|