Copymost Software Changes

Update to reflect compatibility with MCP 54.1.

Internal changes to other Metalogic software had a knock-on effect on COPYMOST, causing any specified directories to fail COPYMOST's file matching procedures. The problem caused COPYMOST to reject all directory requests because it considered them as files. This problem is now fixed.

COPYMOST will now restore some granulated privileges when a codefile is loaded back to disk. This privileges currently include PU, SECADMIN and TASKING; previously, none of these options were correctly assigned.

The COPYMOST_BLOCKSIZE variable introduced in 490.04 expected a value in characters but used the value as if it was words. The value specified is now correctly converted to words before being used.

By default, COPYMOST uses a default tape BLOCKSIZE of 122880 bytes for backup generation to DLT drives. However, newer tape drive systems may have smaller BLOCKSIZE requirements requiring an override of the COPYMOST default.

This can be overridden by using the INSTALL utility run with the MAINT option:

					U META/INSTALL MAINT

Add a new variable called COPYMOST_BLOCKSIZE into the 'Variable Name' field and enter the required blocksize into the 'Variable Value' field. Entering 'SET' into the Action field and transmit will save the override value and will be detected automatically by future COPYMOST runs.

COPYMOST would fault with a SEG ARRAY error when trying to report to the FERR report file an attempt to dump a file that was open EXCLUSIVE. This problem is now fixed.

This patch addresses a number of issues with long file names and files with FILESTRUCTURE=STREAM. Previously, a COPYMOST DUMP would not recognize files from a FILECOPY-generated list where the file name had been wrapped on to the next line using '&'. This problem would appear as a MCPDISPLAYTOSTANDARA error 25 in the error listing. Also, COPYMOST would erroneously handle the MYJOB(FAMILY..) and ON RESTART statements from the same file. Both these problems are now fixed.

More seriously, during a DUMP operation, the handling of multiple STREAM files would often generate 'short file' messages causing these files to be dumped incorrectly. This would appear as a random problem since its occurrence would depend on the order of the files being copied. Also, during a RESTORE operation, COPYMOST was not correctly reloading all FILESTRUCTURE=STREAM files because incorrect blocking was being performed on the output files. This problem is now resolved.

Also during RESTORE, files with FILEKIND of CONTAINERDATA or WRAPPEDDATA would give a FILEKIND ERROR leaving the files with a FILEKIND=DATA. To restore wrapped files, special privilege is required by the caller which is nit currently available to COPYMOST so this error message is now suppressed but files will still be created with a FILEKIND=DATA. This does not affect the ability to UNWRAP files from these containers.

COPYMOST did not correctly handle filenames with level identifiers that had more than 17 characters. This caused various warning messages for each long filename encountered and, depending on the number of these files seen, COPYMOST could have faulted with a SEG ARRAY error.

These problems are now resolved.

The internal COPYMOST version has been changed to 48.1 to reflect it's compatibility with that release. No other changes have been needed.

COPYMOST is now qualified for use with MCP 47.

This is an internal Metalogic amendment - no functional changes.

COPYMOST will now correctly compile on MCP 46.1 due to the elimination of reference to the deimplemented BACKUPPUNCH mnemonic.

Creating permanent directories using the MKDIR command creates dummy files with the filekind PERMDIR. COPYMOST fails when trying to open such files, due to an MCP restriction. When scanning for files to copy COPYMOST will now ignore files with filekind PERMDIR.

This change corrects the date displayed in the banner heading and the Directory creation date shown on a DIR response.

This changes all dates displayed to use four digit years. The dates of files held on tape still use two digits. The convention used is that years < 70 are in the century 2000, years > 69 are in the century 1900.

A bug which would cause COPYMOST to abort if the maximum allowable file title was used has also been corrected.

MCP 4.1 significantly increase the maximum number of allowed rows for files. Copymost would previously abort if it encountered a file with more rows than the previous maximum of 1000.

When the LIBRARY option is specified CopyMost will now use a new Print Library namely METALOGIC/COPYMOST/PRINTLIB which is now released with CopyMost. The source file for this Library is also released enabling Users to tailor the report if required.

Previously CopyMost would not parse a Filename following an @USE command correctly, this would then result in a NO FILE condition. This problem has now been corrected.

It has been found that the SKIPOPEN option no longer worked on Systems running with Level 7 Disk Headers. This was due to changes in the Disk File Header layout and a new mechanism is now used to detect Open files. This will now operate correctly on both the old Level 6 and new Level 7 Headers.

However, using SKIPOPEN when attempting to RESTORE files from Dump tapes created by earlier versions of CopyMost on Systems running with Level 7 Headers may give inconsistent results.