** c:\djh\cc\slc\SNF310c005.txt *** L=008 --- 2013/02/08 15:38:22 (L07) .c ____________________________________________ | | | Changes in SLC Rel 3.10 Build Level 005. | |____________________________________________| Offset on PRINT output. (New Feature) ** When the length of data being printed exceeds the DATAWIDTH value as set on an OPTION statement, the offset to the start of the data printed on the 2nd and subsequent lines is also shown. For example, with OPT DW=50 in effect, a record of length 215 is shown as: INPUT SEL SEL RECORD RECNO TOT ID. 1 2 3 4 5 LENGTH ----- --- --- ....,....0....,....0....,....0....,....0....,....0 ------ 9 9 7 10010005....Mrs...Patricia.......Sample........... 215 +50 ...Mrs Sample..............xxxxxxxx xxxxx......... +100 .....xx. xxxxxxxxx xxx............................ +150 ..........Fxxxxxxxxx......Kxxx..xxxx xxx..xxxxxx x +200 xxxxxx......C.. ....,....1....,....2....,....3....,....4....,....5 When the offset exceeds 999, it is punctuated with a comma. e.g. +1,200 xxxxxx......C.. Default RECFM. (Change) ** For MVS, if RECFM is not coded for an HFS output file, the RECFM used is the same as that of the input file. For example, a RECFM=VB native MVS input file would still be written to the HFS as RECFM=VB, with BDWs and RDWs as on MVS. Previously it defaulted to RECFM=U for an HFS file, regardless of the RECFM of the input file. LRECL in summary. (Change) ** For MVS, the LRECL value reported in the summary for RECFM=V or RECFM=U output, and for VSAM output, has been changed to the length of the largest record written during the current run. Previously, the system defined maximum length allowed was reported. Fixes. *** 1. (SQ12040) "Logic Error 3303" was issued when a minus sign (-) was used in an EQU name and the same equate name occurred as part of a subsequent label name. 2. (SQ12023) The bottom-of-page scale line was not printed for PRINT TYPE=B of a large record that involved multiple pages to print all the DATAWIDTH lines needed to display the record. 3. (SQ12018) Assignment of an exponential or rational string literal to a decimal DCL variable assigns incorrect value and sets RC=8. e.g. DCL VAR1 DEC(5,2) VAR1 = 1.2e+2 * RC=8 and wrong value. VAR1 = 1.2 * RC=8 and wrong value. 4. (SQ12005) Assigning a binary field in the workarea, (e.g. 4 at 20 TYPE=B), from another field in the workarea of any data type, set the required binary field, but used the wrong numeric value. Assigning a binary field from a numeric string literal was correct. 5. (SQ12010) The MOVE statement did not respect arithmetic conversion rules when the fields concerened were DCL vars or had TYPE=x coded. The data type was ignored and the fields were treated as CHAR strings. The MOVE statement now operates as a MOD statement (an assignment) and arithmetic conversion rules are obeyed, using the data types obtained from the DCL vars or from the TYPE=x coded for the fields. 6. (SQ12049) For MVS only: Command line options and control statements were ignored. 7. (SQ11994) For MVS only: DIRDATA input of a pre-allocated library (PDS) performs repeated dynamic allocation of a library of the same name but with additional HLQ of the the current user's TSO prefix or, for batch, the RACF userid. e.g. 'ABC.ABC.USERLIB' for 'ABC.USERLIB' The unnecessary dynamic allocation of the second library occurs once for each member in the pre-allocated library as shown in the JES2 output for the job. 8. (SQ11981) For MVS only: Mainframe VSAM processing has been brought more into line with the Assembler version with the following enhancements: 1. Reading a KSDS by key no longer requires a KEYPOS parameter unnecessarily. 2. READ BWD or FWD parameters are supported as on Assembler version. ____________________________________________ | | | Changes in SLC Rel 3.10 Build Level 006. | |____________________________________________| No changes to program logic, no fixes applied. The source was simply updated to eliminate compiler warnings on the HP-UX platform re declaration of variables which were unused. ---End---