|
Results |
|
LOAD of saved record selection criteria does not retain numeric operators
When loading Saved record selection criteria, the operator value is not reloaded if it is numeric. Record selection criteria that is saved . PDSPESE2 ----------- PEDIT: Record selection panel for KSDS -------------------
|
|
|
REPLACE command no longer accepts space before WRITE parameter
REPLACE MEM1 /ZZ/XX/ WRITE PDS844E Syntax error: INVALID KEYWORD
|
|
|
USAGE and FIXPDS commands show no free space for PDSE data sets
USAGE and FIXPDS commands show no free space for PDSE data sets
|
|
|
VUSE results in 'This volume has no free space' for empty MOD27 device
VUSE results in 'This volume has no free space' for empty MOD27 device
|
|
|
PEDIT Record Selection does not show changed value even if not in copybook mode
When using PEDIT record selection, if a value is changed on panel PDSPN41 and SAVE command issued on the command line, the changed value reverts back to its value before the change. If PEDIT is exited and then go back to the data and look at the value, the change is actually reflected.
|
|
|
StarBat MULTICOPY incorrectly issues STRB79W One or more input data sets had no data selected for output, RC= 04
STRB79W RC=4 is issued even though the record is read from the single input dataset and written to both output datasets.
|
|
|
output records padded by blanks when StarBat writes records to output dataset
Product: Starbat 7.5.3 Problem: starbat output records appear to be padded by blanks (as if writing entire block instead of record) This can occur when writing to a PDS member or as sequential dataset that does not have blksize=lrecl
|
|
|
'selection description' deleted after exit FDM for SAVED selection criteria
When record selection criteria get saved from the record selection panel, a 'selection description' can be added which will be viewable in PROFMAN. If exit FDM and go back into FDM and invoke the PROFMAN command, the 'selection description' no longer exists. PDSPESE2 ----------- PEDIT: Record selection panel for KSDS -------------------
|
|
|
values do not automatically increment for DB2 columns defined with IDENTITY
Detail: With table containing a column defined with the IDENTITY parm, and insert does not automatically increment the value. If I attempt to change the value, the save fails because this is not allowed. I can use SQL to perform the process though.
|
|
|
Hyper Fix: TLOD install library does not contain product members, only $DUMMY
1) save the file to your PC 2) send the file to the mainframe, issuing the following command from your PC command prompt
|
|
|