SSysBlksize=No (the previous default) means that records are unblocked when BLKSIZE=0.

Assembler macro ZZSNAME (alias CBLNAME) undeclared SELCOPY option SMVSOutQSAM renamed as SMVSOutBSAM with default remaining as "No" (CBLSUSR1 x'02' off). PTF RI00006 interprets this as indication to use QSAM for output data set processing.

i.e. QSAM (not BSAM) processing is default for output sequential and PDS/PDSE library data sets.

Same problem in previous release.

Use of BSAM to process records written to output data sets was introduced as the default for SELCOPY release 3.00. Although use of BSAM processing potentially reduces CPU time, the elapsed run-time may be increased significantly when writing large amounts of data.

Application of this PTF will disable default use of SELCOPY's BSAM processing, defaulting instead to QSAM processing as for previous releases.

BSAM output processing may be re-activated as the installation default using CBLNAME option SMVSOutBSAM=Yes.

Also corrects report of VSAM information for IAM data sets in List Catalog (LC) and List Dataset (LD) windows.

Note that IAM V9.00 PTF P900120 or IAM 8.10 PTF P810278 are pre-requisite.

1. Support for Hierarchical Compare.
2. REPORT output to a specified PDS/PDSE member, e.g. hlq.COMPFILE.REPORT(AB001), now correctly creates associated SDO with the same member name but belonging to PDS/PDSE library of type SDO, e.g. hlq.COMPFILE.REPORT.SDO(AB001).
3. Batch execution of COMPFILE now has default report:

      %racfuser%.SELCOPYI.COMPFILE.REPORT
   

Now returns the following error message on EDIT/BROWSE:

  ZZSD411E A member name was specified for an existing
           sequential dataset.

This includes support for new "Compare Files" panel accessed via the "Utilities" drop menu, list prefix command "CF" or line command COMPFILE.

COMPFILE also supports parameters that allow full function execution from via the command line or CMDTEXT.

The Compare Files utility allows the compare of NEW and OLD versions of a file, with options that include support for the following:

1. Specify the start record.
2. Restrict the number of records compared.
3. Restrict the number of differences reported.
4. Restrict the comparison to specified areas of each record.
5. Re-synchronise record pairs following a mismatch.
6. Specify key segments (at the record-type level) that allow the utility to identify 'corresponding pairs' of records.
7. Control how re-synchronisation should occur following detection of an inserted or deleted record.
8. Apply a structure (copybook) overlay to map records, and optionally restrict the comparison to specified record-types and/or named fields. This is known as a "formatted compare".
9. Apply different structures to the NEW and OLD files, with comparison restricted to fields that exist in both structures. This allows comparison of files where corresponding fields are of different data-type, length and/or location within NEW and OLD records.

See Help for the Compare File panel and COMPFILE line command for details of use and report output. Alternatively, view the SELCOPY/i Compare Files Utility PDF document.

FILTER is particularly useful where FOR #recs is specified (which forces in-storage edit) and the number of records (#recs) to be loaded exceeds available storage.

This update also introduces support for built-in function calls so enhancing support of SDE expressions used by line commands USE WHEN, RCOLOUR, LOCATE, WHERE, EDIT FILTER and BROWSE FILTER. See SDE Help for description of SDE expressions.

The SDE Edit/Browse panel now has menu item FILTER to open the "Create Filter" panel (also started via the FILTER line command.)

See Help for the Create Filter panel and SDE EDIT and BROWSE line commands for details of use.

USE <rectype> <ALWAYS>

Assign rectype to all records.

USE <rectype> NEVER

Exclude rectype from any automatic assignment processing.

USE <rectype> WHEN

No <expression> specified following WHEN will now remove any existing WHEN <expression>.

USE <rectype> FOR FOCUS RECORD <OFF>

Assign rectype to record on focus line.

  RCOLOUR <rectype> <colour> <highlight> WHEN <expr>

SELCOPY/i supports use of IAM files for text edit/browse, SDE edit/browse, File Search and Update, File Copy and File Compare. Furthermore, catalog lists and dataset details lists display IAM data set entries as being DSORG VSAM.

  EDIT  NBJ.GDG01(-1)

Default values are assigned based on the user's TSO login id and options set in the SELCOPY/i Site INI file.

A further presumption is made that the user has authority to allocate new data sets with the prefix specified for System INI option, System.UserINIFile, and that SMS automatic class selection will occur for SMS storage group. If this is not the case, then allocation of new data sets will fail and the user will be prompted to enter new dataset allocation values (Volser).

Any default values that are automatically assigned may be updated by the user at a later time and as required.

1. Non-SDE or text edit MDI child windows no longer show the edit status bar.

2. The MDI client area size is now recalculated if window focus is on an MDI child window that has its own menu bar. This is because the menu bar now occupies the MDI parent window menu bar.

3. List windows now use the two free blank lines before the status line.

4. Modal dialog windows for defining new VSAM data sets can now be open in maximised mode. Also, the action buttons at the bottom of modal dialog windows are no longer obscured when displayed on a 24x80 screen.

IPO windows are used for any new dialag panel introduced in SELCOPY/i which currently includes SELCOPY/i DB2 panels, Compare File, SDE Edit and Create Filter. Future development will see existing panel windows converted to IPO panels.

1. An FSU command line parameter is ignored if it immediately follows an OUTPUT, REPORT or USING parameter that specifies a quoted fileid. e.g. FIND is ignored in the following:

     FSU  REPORT 'JGE.FSURPT'  FIND('ABC') INP(JGE.*)
   

2. If a COBOL/PL1 copybook (not an SDO) is applied for formatted record file update, then the generated SDO report output is not saved when selected to do so by the user.

3. Re-edit of a report generated for a formatted record file compare does not correctly identify record-types by implementing USE WHEN criteria to the report SDO.

4. From the File-Search/Update (FSU) panel, corruption of the generated command occurs when entries in the "Column SELECT" field are of length > 50 characters

5. ZZSD009E Invalid operand occurs if FSU command includes specification of a PDS/PDSE member which is an FSU keyword. e.g. NEW, REPLACE, etc.

Also fixes abend that occurs if SDE edit/browse of a library DSN is specified without a member, invoking a member selection list, and the second or subsequent member is selected.

  select Entry,Org,Trks,Pri,Alu,Sec,*

may be abbreviated to:

  sel e o tr p a s,*

1. INSERT of a new formatted record, which is of a record-type containing zoned decimal fields, no longer primes these fields with X'00' which caused prefix area condition =ERRV> and error ZZSD368I on attempting to modify the record.

2. INSERT of a new formatted record, now primes each field with a value that adheres to the field's defined constraints. e.g. a COBOL field defined with OCCURS 3 TO 7 will be primed with 3 by default.

3. INSERT a record of a specific record-type now implicitly sets DRECTYPE to that record-type.

4. Correct potential loop caused by the distributed SDE edit/browse profile macro, SDEPROF, and macro SDESHRNK.

5. SDEPROF now returns error message ZZSD015E if LOCATE is performed on edit of a non-existant file.

6. In an SDE window view, correct display of variable arrays with dimension size defined by a packed decimal or zoned decimal field. Before this fix was introduced, array was displayed with zero elements.

7. SET UNNAMED OFF option is now reflected in a single record format SDE view.

8. Display of shadow lines are now hidden immediately following execution of SET SHADOW OFF ALL where the focus line is "Top of data" (record 0).

9. SDE selective editing commands ALL, EXCLUDE ALL, LESS, MORE, ONLY, WHERE are no longer erroneously disabled for SDE DB2 table browse/edit.

10. SET DSORG RRDS now works as documented for data in an SDE window view.

Parameters for both DSQL and DCMD:

-SSN <ssn_name>

Specifies the DB2 sub-system to which the SQL statement or DB2 command will be passed. If DB2 Primary Option panel exists with a connection to <ssn_name>, then this connection is used (i.e. no new connection is made.)

Default is the last sub-system to which a connection was made via the DB2 Primary Options panel.

-LIMit <n_rows>

Limit the number of rows to be displayed in the Execute SQL panel following a SELECT transaction or the number of bytes used for the Execute DB2 command response buffer.

<sql_syntax> | <db2_cmd>

The remainder of the DSQL or DCMD input parameter string is treted as the SQL statement or DB2 command stream respectively.

Also increases maximum support SQL command length from 512 to 32000 bytes.

Input parameters are:

1. Selected record type in the structure/copybook from which to generate the EQU statements. Alternatively, specify "ALL" to use all record mapping definitions.
2. Source structure/copybook type ADA/COBOL/PL1/SDO.
   ADA - COBOL or PL1 ADATA data set.
   COBOL - COBOL copy book.
   PL1 - PL1 include file.
   SDO - SELCOPY/i generated structure.
3. Complete DSN of one or more structure/copybook data sets each separated by a comma (,).

e.g.

  PARM='ALL COBOL NBJ.COB(REPLACE), NBJ.COB(CBYBOOK)'

EQUates are written to dataset allocated to ddname SELCEQU

Although only a recommendation in CA-DYNAM/D documentation, in order for this zap to operate successfully ££BDYD££,MOVE must be added to the SET SDL in the ASI procedure.

Same problem in Release 2.02 with Zap 01 applied.

With Zap 09 applied, if no length is specified on an UPDATE statement for an MVS non-KSDS data set, then the length of the update record and not the prevailing LRECL value is used to move data to the I/O buffer. Note that this zap does not apply to KSDS data set records whereby the record length may be altered by an UPDATE-in-place operation.

Same problem in previous release.

Problem also affected FSU with output to an HFS file that didn't already exist.

Solution is for COLSET to set ZONE 1 80 for the SCOLOUR/LCOLOUR commands.

  ALL
  EXCLUDE ALL
  LESS
  MORE
  ONLY
  WHERE

However, this restriction should not be applied when "FOR nnn" is specified, in which case all nnn records are loaded and kept in storage.

e.g. To see only the records containing the character 'M' in position 1, of the first 10000 records of a large file, on the SDE panel specify:

  FOR:     10000 # records

  ONLY c'M' 1

 <SData Edit   _                       \
         VOLUM1:CBL.TEST.FILE          \
   UPDate                              \
    FOR  10000  records                \
 |||||||||||||||||||||||||||||||||||||||

Format:
SelcEqu  rec-type  <ADA|COBOL|PL1|SDO> structure_file
         ALL                      ---

Selection of a member works first time, but second fails, with potential program check at SDEFSEO3+122.

e.g.
<sd e                            CBL.FDD.DATA       \
                   using      cbl.cbli.SDO(FDDOLD)  \
|||||||||||||||||||||||||||||||||||||||||||||||||||||

The same program check can also occur when SDE edit/browse is performed directly from a COBOL/PL1 copybook.

e.g.
<sd e CBL.IQ002689.TEST1                            \
      using cobol CBL.SDE.COPYBOOK.COBOL(IQ002689)  \
|||||||||||||||||||||||||||||||||||||||||||||||||||||

Also, BLKSIZE is incorrectly updated for all PDS library or DISP=MOD/SHR sequential data set output if CBLNAME option SError582=No is set.

 <Fsu _                                    \
  CHANGE (                                 \
          (TEXT ALL  'Nicholas' 'Nick'  )  \
           AND                             \
          (TEXT ALL  'Jim'      'James' )  \
         )                                 \
  INPUT  (CBL.IQ002623.ORIG)               \
  OUTPUT  CBL.IQ002623.UPDATED             \
 |||||||||||||||||||||||||||||||||||||||||||

Output data set allocated record format and maximum length restrictions still apply.

Therefore, where a search string has multiple hits in the same record, the replace string will overwrite incorrect locations for the second and subsequent hits. e.g.

   FSU  INP(CBL.TEST)  C('IN' '1234' ALL TEXT)

           <---+----1----+----2----+----3----+
 Before -> * BEGIN WHEN ITS TIME TO BEGIN
 After  -> * BEG1234 WHEN ITS TIME TO B1234IN

FIRSTUSE is executed automatically the first time a user starts SELCOPY/i following an upgrade. Prior to this PTF, a non-scrollable message window identifying new facilities would be displayed which exceeded the 24 line depth. The effect was that the user could not continue normally and the TSO session became unresponsive.

The report field, VTot, has also been introduced for these types of lists in order to display the total number of volumes on which the file is allocated.

See cataloged procedure ZZSPVTAM for execution of SELCOPY/i as a stand-alone VTAM application (CBLIVTAM).

For batch address spaces the default action of the DB2 connection process is to use the JOB level user id, rather than any task associated ACEE user id, as the primary authorisation id of the connection.

This PTF introduces a new sample library member, ZZS3SATH, which may be used to update the DB2 connection authorisation exit, DSN3@ATH.

The modification implemented in ZZS3SATH only changes the default processing of the authorisation exit when the DB2 connection is attempted in a batch address space from a subtask of the program CBLAVTAM. (i.e. SELCOPY/i under VTAM.)

The basic source for ZZS3SATH was copied from DSN910.SDSNSAMP(DSN3SATH) and modified. No lines have been changed or deleted. Added lines have IQ002629 in column 64.

The DB2 administrator should first verify whether this exit has already been modified on operational DB2 subsystems. If so, the inserted lines in ZZS3SATH sample member should be carefully merged with the existing, tailored source.

Installation specific DB2 exit management standards (e.g. SMP/E USERMOD) should be used to assemble and link edit the exit source as DSN3@ATH (as required by DB2) into the appropriate DB2 subsystems' user exit libraries.

Note that exit DSN3@ATH must be available to the DB2 master address space and the DB2 subsystems must be restarted in order that changes take effect.

 <SData Fsu _                         \
   FIND   (                           \
           SEO_FsuInp                 \
          )                           \
   INPUT  (                           \
           CBL.CBLI310.ASM(sdef*)     \
          )                           \
 ;sd sel z HOLD,*  from Hit           \
 ||||||||||||||||||||||||||||||||||||||

 +-----------------------------------------------------+
 | CBLi System Command                               x |
 |                                                     |
 |  !  Command SdeShrnk                  ended with    |
 |     return code 20.                                 |
 |                                                     |
 |                         OK                          |
 |                                                     |
 +-----------------------------------------------------+

This is now automatically applied if SELCOPY sysprint output is recognised.

VTOC and VTOC Extent lists generated from VOLSATS menu items do not open as MDI child windows.

'File' menu items:
Execute SELCOPY ...
Execute CBLVCAT ...

replaced with
SELCOPY Debug/Dev ...
CBLVCAT Interactive ...

Previously, no action was taken unless the INI variable %user.SDE.ZCols% was set. This variable was only ever set by the SDE panel on releases of SELCOPY/i prior to 3.00. (e.g. "Window Rows: 50 x Columns: 124") Therefore, any 1st-time user on SELCOPY/i 3.00 would never benefit from this feature.

FCOPY now allows the user to update the Type field to be SEQ. Previously, FCOPY would only allow the same DSORG as the source data set. (i.e. PDS or PDSE.)

Condition arose on an attempt by the installer to follow a non-standard upgrade path from SELCOPY/i 1.70 to SELCOPY Product Suite 3.00.

SELCOPY/i has been corrected to first detect whether the data set is migrated and, if so, recall it before performing the dynamic allocation.

Use of FORMAT CHAR or FORMAT HEX to display DB2 table rows without column formatting is no longer permitted.

Previously this condition would return the following error message...

   ZZSD007E Operator ) cannot follow operator =.

B	-	(exists) Now starts Browse dialog (like E).
BI	-	(new) Browse Immediately bypassing panel.
EI	-	(new) Edit Immediately bypassing panel.

XL

-

List indexes.

For inserted rows, the primary key column may be updated regardless of whether EDITPRIMEKEY is specified. This specification has now been extended to include duplicated table rows.
i.e. rows inserted using the 'R' prefix command.

CL

-

List columns for that particular index. (Previously displayed all columns for the associated table.)

The same highlighting has been applied to data displayed in FORMAT SINGLE mode.

This also addresses the problem whereby a long field entry in a zoomed view did not wrap or scroll. The contents of these fields may now be scrolled left and right.

1. Maximsed/Restored mode is maintained across SELCOPY/i sessions. Independent Maximsed/Restored mode settings are maintained for CBLe child windows and SELCOPY Debug child windows. This feature utilises the following INI option variable:

      <windowclass>.InitialState=MAX.
   

2. When in Restored mode, The 'CBLe' parent window title bar is removed so that user gains an extra line in the display area.
3. When a CBLe child window is in Maximised mode, the minimise and restore buttons are no longer displayed in the title bar. This is so the user doesn't accidentally restore the CBLe parent window when restore of the CBLe child window is intended.
4. The prefix displayed in the title bar of a Maximised CBLe child window has been updated to be 'SELCOPY/i' instead of 'CBLe'.
5. When operating in Maximised mode, the 'Wr' button (executes WinX), MW and SZW commands and SET WINPOS/SIZE edit commands no longer switches the window out of Maximised mode. These window manipulation features now only affect windows in Restored mode.
6. The SELCOPY Debug application no-longer rigidly starts in Maximised mode if window width<=80. The message box to this effect removed.
7. The SELCOPY Debug application default window arrangement has been improved.
8. Problems fixed that relate to unintended switching between Restored and Maximised mode.

Note: IPO DROP is not a published command and its use is not recommended.

  <windowclass>.PFn<n>DELAY=YES/NO
  <windowclass>.PFn<n>BEFORE=YES/NO

This allows the PFKeys set for particular window classes to be maintained across SELCOPY/i sessions.
Default values are "NO".

This gives the user control of the <Enter> key and so protect against accidental execution of a DROP statement.

Additionally, direct definition of these types of field is supported via additional sub-parameters to SIGNED. e.g.

  <sd create struct                                 \
                  CBL.CBLI.SDO(IQDI2583)            \
    ( DIRECT-01  struct                             \
      (                                             \
       PROD           char(3)                       \
      ,SIGN-XXXX      zoned(13,2)                   \
      ,SIGN-LEAD      zoned(13,2) signed(lead)      \
      ,SIGN-TRAI      zoned(13,2) signed(trail)     \
      ,SIGN-LEAD-SEP  zoned(13,2) signed(lead,sep)  \
      ,SIGN-TRAI-SEP  zoned(13,2) signed(trail,sep) \
      )                                             \
    ) rep names(cobol)

See ammended help for SDE command CREATE STRUCTURE.

In character (unformatted) view these commmands now scroll <n_cols> columns.

Previously, cursor was positioned within the list display area and so immediately hitting <Enter> did nothing. Commands LL and LJQ (i.e. those that have only one input prompt) do not suffer the same problem.

Previously, altering the length of a record using SDE EDIT was deliberately prohibited in order to preserve record data structure.

This restriction has been removed so that the length of a record may be altered if the following conditions are true:

1. File contains variable length records.
2. The SDE Edit technique in use is Full Edit, Auxiliary Edit, KSDS Edit or Read-Only Edit.
3. No record structure (RTO) is associated with the record or the record display is unformatted.

If all these conditions are met, then the length of a record may be altered via the following methods:

1. Overtype the Length field in the Record Information area.
2. Execute SDE command SET LENGTH.
3. Execute SDE command CHANGE where the replace and search strings are of a different length.

In order to support this feature, the following changes have been introduced:

• SDE CHANGE command now supports mutually exclusive keyword parameters, DATA and TEXT, to control the effect of the change operation when the replace and search strings are of a different length.
  CHANGE TEXT will cause the change to operate as for ISPF style text edit with blanks being absorbed or added as appropriate.
  CHANGE DATA will simply change the data with no special treatment of blanks.
• Re-evaluate the record type (RTO) associated with a record if either of the following conditions occur:
  1. A field included in a "USE WHEN" condition is updated (by overtyping it or as a result of a CHANGE command.)
  2. The record length is altered.
• Introduce support for the SDE SET/QUERY/EXTRACT PAD option to maintain the pad character used when the length of a variable length record is increased or a new record is inserted.

  
    Syntax:
  
     }}-+-------+- PAD ---+- NUll ----+--------}{
        |       |         |           |
        +- SET -+         +- BLank ---+
                          |           |
                          +-- char ---+
                          |           |
                          +- 'char' --+
                          |           |
                          +- "char" --+
                          |           |
                          +- hexstr --+
                          |           |
                          +- binstr --+
  
    where:
      char  is a single character.
     'char' is a single character in apostrophies.
     "char" is a single character in quotes.
      hexstr is a hexadecimal string (x'00'-x'FF')
      binstr is a binary string b'00000000'-b'11111111'
  

• Rename the record length column heading from "Lrecl" to "Length".
• Introduce the SDE RECLEN command to control display of the record Length column. This is a synonym for SDE SET RECINFO ON/OFF LENGTH.
• Introduce support for the SDE SET/QUERY/EXTRACT LENGTH option to update/display the length of the record occupying the focus line.

For batch execution only, changes made to strucutures are now saved automatically without requiring a specific SAVESTRUCTURE command.

  CHANGE  10  16  (#3)  all

"ZZSD219E File <fname> does not exist" should be the immediate response.

FORMAT SINGLE behaves differently depending on whether the data is formatted or unformatted.

SDEZOOMW updated to format the record data prior to switching to FORMAT SINGLE.

The 0C4 occurs when one of the SDE edit views are closed and processing is continued in the SDE edit view for the other DB2 table.

SYSMOD QS00004 causes a unique temporary structure (SDO) to be generated for each SDE BROWSE or EDIT of a DB2 table.

This fix ensures that a VARCHAR length field is set to zero for NULL values.
Same problem in previous release.