US POSTAL SERVICE 475 L'Enfant Plaza, SW Room 4541 Washington DC 20260-6238

99 -- VSAM SOFTWARE UTILITY PACKAGE POC Contact Point, Diane Matthews, 202/268-2492, Contracting Officer, Kathleen A. Duffey, 202/268-2662 (No Collect calls). The United States Postal Service is looking for sources that can provide VSAM software utility package. The package should have the following functional product requirements: 1) Must support the VSAM KSDA format and be able to reorganize this type of data set more efficiently than IDCAMS. 2) The product must provide the ability to change the size and VOLSER, of any component, of the VSAM data set during reorganization. 3) In data set reorganization and movement, the product must recognize if a given VSAM data set has any PATHs or AIXs and handle them appropriately. 4) The product must be able to make intelligent decisions on whether or not a data set requires reorganization and take the appropriate actions. 5) The product must support both volume level scans and scans based off a DSN mask, without the need to specify a volume (i.e. a catalog scan). 6) During scans for finding data sets to reorganize, the product must provide the ability to make and keep backups of data sets, even if they do not require reorganization. 7) In providing the ability to keep a backup of a VSAM data set, there must be at least an option if it is not the functional default, to keep the backup in IDCAMS REPRO format. In addition, the following functions are desirable: 1) A strongly preferred option would be for the product to work with all VSAM data sets (not only KSDS's). This would give us the capability to use one utility to do most, if not all, of our VSAM work. This VSAM work includes, but is not limited to: backups, renames, re-sizing, and data set movement. 2) As an option, allow us to trap IDCAMs syntax cards for the VSAM data set that is being worked on and stop the processing on the data set after we have trapped the cards so we can make any modifications we want. We have found that some of our data sets are being updated via the IDCAMs ALTER command and therefore our cataloged DELETE/DEFINE statements for a given VSAM data set, do not always match the data set. This capability should be provided for all types of VSAM data sets and provide all the necessary cards for AIX, PATHs, and anything else that would be required to define a VSAM data set exactly the way it currently exists on DASD. 3) Provide the ability to rename, any component, of any component, of any VSAM (KS, ES, RR, LI, etc.) data set during reorganization. (NOTE: This number could be taken further to allow us to change 'any' IDCAMs parm via input statements, but this one, and the requirements to allow us to change volumes and data set sizes, are the most important.) This is for informational purposes only. No solicitation is available. Information should be sent to Diane Matthews, Room 4541, 475 L'Enfant Plaza, West, SW, Washington, DC 20260-6238. If this results in a solicitation, no additional synopsis will appear. Responses should be received at this office by April 8, 1996. (0081)

Loren Data Corp. http://www.ld.com (SYN# 0290 19960322\99-0002.SOL)