Code Download Tips
Code downloads, patches and firmware are available on SunSolve for Sun Storage and Sun StorageTek products. Review the tips below to assist you.
General Instructions for Downloading Sun Patches
- Using your web browser, download the Sun patch file to your workstation or PC by clicking on the "Download Patch HTTP" link at the top of the patch description web page. All patch files are downloaded as binary .zip files.
- When the download is complete, you'll need to extract the patch file. Double-click the patch file to launch an extractor, which should extract the patch file contents to a folder.
- Upload the extracted PTF file and cover letter file to the target mainframe system using FTP in binary mode. Use an 80-byte record length for z/OS hosts and a 1024-byte record length for z/VM hosts.
Example for z/OS:
ftp> lcd <PTF directory>
ftp> quote site QUOTESOVERRIDE
ftp> quote site DATASETMODE
ftp> quote site CYLINDERS
ftp> quote site filetype=SEQ
ftp> quote site blksize=0
ftp> quote site recfm=FB
ftp> quote site lrecl=80
ftp> binary
ftp> put XXXXXXX.ptf your.fixed80.dataset
ftp> quit
(Or: you may preallocate the dataset with the desired attributes)
Note: Use ASCII mode ftp if uploading extracted README and LEGAL_LICENSE.TXT files.
See additional instructions that follow for specific products if applicable.
- Always reference the README and the PTF Cover Letter for specific instructions.
Note: File Size Alert: The patch file size displayed on our web site may differ from the size of the downloaded patch file. This difference is caused by space calculation methods; for example, our web site displays bytes and MS Explorer displays kilobytes
Instructions to Download and Apply Cumulative Maintenance for VTCS, NCS and Ex Products
1. Download to your workstation or PC the Cumulative Maintenance patch file for your product, platform and release (example: Cumulative Maintenance for HSC 6.1 for MVS).
2. Download to your workstation or PC the associated Cumulative Maintenance HOLDDATA patch file for your product, platform and release.
3. Extract the Cumulative Maintenance patch file and the Cumulative Maintenance HOLDDATA patch file by double-clicking each of these patch files to launch an extractor.
4. Upload both the PTF file and HOLDDATA file to your host using a binary transfer.
5. Perform the SMP/E RECEIVE of both the PTF and HOLDDATA files.
6. Perform an SMP/E APPLY CHECK with GROUPEXTEND and address any issues indicated.
7. Perform an SMP/E APPLY with GROUPEXTEND.
8. Perform an SMP/E ACCEPT per your installations policies.
Reminder:
It is extremely important that you download the associated Cumulative Maintenance HOLDDATA (if available) whenever you download PTFs for a product. Note that the HOLDDATA in a Cumulative Maintenance patch may be outdated by that in the current Cumulative Maintenance HOLDDATA patch. Omitting current HOLDDATA during the SMP/E Receive step may expose you to known operational issues that are addressed in the current HOLDDATA.
Important notes:
If HOLDDATA does not exist for your product, ensure the SMP/E RECEIVE control statement does not reference HOLDDATA.
Performing an APPLY for selective PTFs in the Cumulative Maintenance PTF file may expose you to known operational issues that are addressed by other PTFs in that Cumulative Maintenance PTF file.
Instructions to Download and Apply Cumulative Maintenance for VM/HSC
The following process will copy all the PTF files to the DELTA disk for subsequent application using VMFMERGE.
There is a PTF coverletter that is copied to your A-Disk that will contain a list of all of the PTFs downloaded.
It is recommended that you apply individual PTFs for specific problems that you are attempting to resolve.
The holddata file for VM products is for information only; the VMFMERGE process includes an EXCLIST.
Note: In the following examples, replace the product_id
value with the product ID affected (e.g.; SMS4100).
- Upload the PTF file and HDD file from you local working directory to a destination
userid on your VM host system.
- ftp> open hostname
- ftp>user and password
- ftp> binary
- ftp> quote site fixrecfm 1024
- ftp> put product_id.ptf
- ftp> put product_id.hdd (if applicable)
- ftp> quit
- Once the files have been moved to the target VM System they should be copied
to the MAINTSTK 191 disk. The holddata file (*.hdd) is for information only. The
PTF file (*.ptf) is a Fixed 1024 byte file in CMS VMFPLCD format.
- Unpack the PTF file using COPYFILE as follows:
- COPYFILE product_id PTF A (REPLACE UNPACK
- Unload the individual VMFPLCD files to the A-disk and I-disk. This is assuming
that the DELTA disk is accessed as I (e.g. ACCESS 251 I )
- VMFPLCD LOAD * * A ENV= product_id PTF A (SELECT DATE
- VMFPLCD LOAD * * I ENV= product_id PTF A (SELECT DATE EOD
- Apply individual PTF maintenance or a list of PTFs using VMFMERGE.
- VMFMERGE product_id PTF ptf_number EXCLUDE product_id (for
a single PTF)
- OR
- VMFMERGE product_id PTFLIST product_id EXCLUDE product_id (for
a list of PTFs)
- Regenerate the product using specific product generation exec.
- Recycle the software product for the PTF maintenance to take affect
Instructions for Upload and Apply of VM SVAA Maintenance
The following process will copy all the PTF files to the DELTA disk for subsequent
application using VMFMERGE. There is a PTF coverletter that is copied to your A-Disk
that will contain a list of all of the PTFs downloaded. You may want to apply individual
PTFs for specific problems that you are attempting to resolve.
Note: In the following examples, replace the product_id
value with the pseudo product ID affected (e.g.; SVAA310V).
- Upload the PTF file from your local working directory to a destination userid
on your VM host system.
- ftp> open hostname
- ftp>user and password
- ftp> binary
- ftp> quote site fixrecfm 1024
- ftp> put product_id.ptf
- ftp> quit
- Once the file has been moved to the target VM System it should be copied to the
MAINTSTK 191 disk. The PTF file (*.ptf) is a Fixed 1024 byte file in CMS VMFPLCD
format.
- Unload the VMFPLCD file using the service exec:
- EXEC SSSIB310
- The service exec will prompt before initiating the VMFMERGE step.
- If you wish to decline the prompt you may apply individual PTF maintenance or
a list of PTFs using VMFMERGE.
- VMFMERGE product_id PTF ptf_number EXCLUDE product_id (for
a single PTF)
- OR
- VMFMERGE product_id PTFLIST product_id EXCLUDE product_id (for
a list of PTFs)
- Regenerate the product using specific product generation exec.
- Recycle the software product for the PTF
maintenance to take affect
SVAA JCL: Instructions for Processing OS/390 SVAA Installation JCL
After the JCL file has been uploaded to the host system use the following procedure
to load to a PDS. The installation JCL will be applicable to either the Base SVAA
or SNAPSHOT product.
//***************************************************************
//jobname JOB accounting,'name',MSGCLASS=H,MSGLEVEL=(1,1),
// NOTIFY=&SYSUID,CLASS=A
//PS010 EXEC PGM=IEBUPDTE,PARM=NEW
//SYSPRINT DD SYSOUT=*
//SYSUT2 DD DSN=hlq.install.jcl.pds,DISP=(,CATLG,DELETE),
// UNIT=SYSDA,SPACE=(CYL,(10,2,10)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=23440,DSORG=PO)
//SYSIN DD DSN=product_name.JCL,DISP=OLD,
//***************************************************************
DIAG: Troubleshooting the Upload Process
If problems occur in the download/upload process, please gather information as
follows:
- After downloading the PTF, note and record all possible information about it,
particularly its size in bytes if available.
- After the FTP upload and before the COPYFILE (UNPACK), issue the following commands
on the VM host and save the output:
- LISTFILE product_id PTF * (LABEL
- LISTFILE product_id HDD * (LABEL
- Be prepared to report the output of:
- The unzip or uncompress and tar commands
- The FTP commands
- The LISTFILE commands
- The COPYFILE ... (UNPACK command
- The VMFPLCD command
RTV: Generate Real Tape Volume Download Instructions
Standalone Usage
This executable version of RTV is intended to be used on MVS hosts that do not
have VTCS software installed. RTV is an integral part of VTCS, and can be executed
directly from the same load library used to run the various SWSADMIN utilities.
If you downloaded this version of the RTV utility for use at a site which does
not have NCS/VTCS software installed, you must do the following:
- Install the standalone version of RTV per instructions on the CRC.
- APF authorize the RTV load library you just created.
- In the JCL Examples in the ICAG, substitute the DSN you picked for the RTV load
library for DSN hlq.SLSLINK on the STEPLIB DD statement(s).
The RTV software packaged for standalone use is identical to the RTV software
distributed with the NCS/VTCS executable libraries.
NOTE: make sure all FTP operations are performed using binary mode
- Allocate a dataset on MVS
to hold theSWSRTV.ftpfile.ItshouldhavethefollowingDCBattributes:RECFM=FB,LRECL=80,BLKSIZE=3120 and be at least 3 tracks in size.
- FTP the SWSRTV.ftp file to the mainframe into the dataset allocated above.
- From the MVS mainframe receive the file that was just sent via FTP by issuing
"RECEIVE INDS('ftp.dataset')"
This will create a load library containing the executable version of SWSRTV.
Before running SWSRTV, make sure the dataset containing the load modules is APF
authorized.
For information on JCL to run the utility, reference your VTCS Installation,
Configuration and Administration Guide.
Sample Output from RECEIVE operation:
RECEIVE INDS(SWSRTV.FTP)
Dataset SWS100.SWSRTV.LINKLIB from SPBR on LSTC3MVS,
Enter restore parameters or 'DELETE' or 'END' +,
dsn(swsrtv.linklib)
IEBCOPY MESSAGES AND CONTROL STATEMENTS PAGE 1,
IEB1135I IEBCOPY FMID HDZ11E0 SERVICE LEVEL UW62382 DATED 20000308 DFSMS 1.5.0 MVS SP6.0.7 JBB6607 CPU 9672,
IEB1035I SPBR $STCTSO1 $STCTSO1 11:12:42 WED 17 JAN 2001 PARM='',
IEB1064I STANDARD DD NAMES- SYSIN SYSPRINT SYSUT1 SYSUT2 SYSUT3 SYSUT4,
IEB1065I OVERRIDING DD NAMES- SYS00066 SYS00067 SYSUT1 SYSUT2 SYSUT3 SYS00068,
IEB1057I VL GETMAIN REQUESTED 280K TO 1M BYTES. OBTAINED 1M.,
COPYINDD=((SYS00065,R)),OUTDD=SYS00064,
IEB1038I ORIGINAL PDS (BEFORE UNLOAD) WAS RECFM=U BLKSIZE=32760 LRECL=0 KEYLEN=0 OPTCD=X'00' UCBTYPE=X'3030200F',
INDC=X'00',
IEB1058I ALLOCATED 2 CONTIGUOUS BUFFERS EACH 111K BYTES. WORK AREA HAS 757K BYTES AVAILABLE.,
IEB1013I COPYING FROM PDSU INDD=SYS00065 VOL=MVS3WK DSN=SYS01017.T111242.RA000.SPBR.R0125022,
IEB1014I TO PDS OUTDD=SYS00064 VOL=TSO005 DSN=SPBR.SWSRTV.LINKLIB,
IEB1106I CONTROL TABLE IS 70 BYTES LONG. WORK AREA HAS 757K BYTES AVAILABLE.,
IEB1059I ALLOCATED SECOND BUFFER OF 745K BYTES. FIRST BUFFER IS NOW 221K BYTES. WORK AREA HAS 11970 BYTES AVAILABLE.,
IEB167I FOLLOWING MEMBER(S) LOADED FROM INPUT DATA SET REFERENCED BY SYS00065,
IEB154I SLSSDATI HAS BEEN SUCCESSFULLY LOADED,
IEB154I SLSSPARS HAS BEEN SUCCESSFULLY LOADED,
IEB154I SLUIO HAS BEEN SUCCESSFULLY LOADED,
IEB154I SLUPERR HAS BEEN SUCCESSFULLY LOADED,
IEB154I SWSRTV HAS BEEN SUCCESSFULLY LOADED,
IEB154I SWSRVDRV HAS BEEN SUCCESSFULLY LOADED,
IEB154I SWURVST HAS BEEN SUCCESSFULLY LOADED,
IEB1098I 7 OF 7 MEMBERS LOADED FROM INPUT DATA SET REFERENCED BY SYS00065,
IEB144I THERE ARE 19 UNUSED TRACKS IN OUTPUT DATA SET REFERENCED BY SYS00064,
IEB149I THERE ARE 5 UNUSED DIRECTORY BLOCKS IN OUTPUT DIRECTORY,
IEB1056I RELEASED 1016K ADDITIONAL BYTES.,
IEB147I END OF JOB - 0 WAS HIGHEST SEVERITY CODE,
Restore successful to dataset 'SPBR.SWSRTV.LINKLIB',
