Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
MS-WORD All attached modules are in TSO transmitted binary format
2. From the ISPF TSO Option, or native TSO command prompt: Upload (SEND) the file (as a binary a file ) to the mainframe output data set allocated above: example 'yourID.XMIT.DATA'
CMS-XML InstallShield Wizard
... the mainframe product files are unloaded from ... the compressed product files to your local ... and installs the file transfer software ( ... ... to transfer these files to the mainframe where the product files are put back ... ... installation of these files . ... ) The product can't run on the ... only run when uploaded and installed on ... ... "Uninstall" process accessible through the Control Panel "Add/Remove Programs". This 'uninstall' process will delete the mainframe product files that were placed on the PC by the 'installshield process".
CMS-XML z/OS 2.5 Compatibility with ChangeMan ZMF, ChangeMan ZMF Client Pack, ChangeMan SSM, Comparex, StarTool FDM and StarTool IOO
... . Download the file named 'ZMF ... 2. Unzip the downloaded file . 3. The extracted file will generate a folder named 'ZMF8.2.5.031' that will contain files named 'README.txt' and 'H157001.LOD.BIN'. 4. Transfer 'H157001.LOD.BIN' as a binary file to your mainframe into a LRECL=80/RECFM=FB sequential dataset or member. 5. Issue a TSO RECEIVE on your mainframe against the uploaded dataset or member.
CMS-XML Inability to Recover DELTA=Y file after MOVEGRP processing.
When a group is moved using the MOVEGRP command any objects which are defined as DELTA=Y, the DELTA's associated to an object in the GROUP are not moved when the MOVEGRP is executed. This causes orphaned DELTA records in the MASTER files . So the processing of the MOVEGRP needs to take into account of the objects DELTA's and there needs to be a way of recovering the orphaned DELTA's which are referencing the OLD GROUP.
HTML Serena® ChangeMan® SSM Version 8.2.2 Readme File Last updated on 14 July 2005
6.0 Fixes 5000473 Unable to see Permitted Groups 5000487
CMS-XML Attempting to delete components getting SSV error HPS0104E '** Put failure ** on SM file cluster''
Today they could not delete components from two packages which were created after the upgrade. Here are the error messages: HPS0104E
HTML Serena ChangeMan SSM Version 8.2.3 Readme File Last updated on 18 October 2005
1.3 Miscellaneous Enhancements Extended Sequential files are now supported by the Change Tracking component and Detection and Synchronization component, with the following limitation: New multi-volume data sets cannot be allocated when applying a change basket; new data sets are allocated to a single volume.
CMS-XML Inaccurate message HPS1484I being issued during DEFINEDS of uncataloged test file
HPS1484I HPSTRACK 13:39:18 Multi-volume data set SYS3.DR.SSM.TEST.SEQ.N1 cannot be defined using the VOL parameter. HPS1484I HPSTRACK 13:39:18 Multi-volume data set SYS3.DR.SSM.TEST.SEQ.N2
CMS-XML Unable to REPRO MASTER datasets whilst SSM 834 RTO is running on SYSPLEX.
They save all of the three MASTER datasets and the MRTAUX3 dataset whilst the STCs of all four images in that SYSPLEX which are up and running. This work fine when all of the RTO's of the SYSPLEX are running SSM833. However, if you install and run SSM 834 on one image on that SYSPLEX you get the above error for all MASTER files on a regular daily basis.
CMS-XML LIC0022E License file location is unknown message when the license key data set is unavailable
LIC0055E Unable to complete license check. Product terminating.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs