ECO NUMBER: SNADTFM_E14031 ----------- PRODUCT: DECnet/SNA Data Transfer Facility -------- UPDATED PRODUCT: DECnet/SNA Data Transfer Facility 3.1 ---------------- APPRX BLCK SIZE: 5922 ---------------- Compaq Computer Corporation 550 King Street Littleton, Massachusetts 01460-1289 October 21, 1999 SUBJECT:DTF for MVS V3.1 PUT SERVICE INSTRUCTIONS This ECO contains PTF's for the DECnet/SNA MVS Data Transfer Facility (DTF for MVS V3.1). Note: If this ECO is obtained on tape media, it will be in IBM readable format and ready to install as described in the PTF INSTALLATION INSTRUCTIONS section. If it is obtained electronically, the PTFs are distributed in an OpenVMS saveset. Please refer to the INSTALLATION TO BUILD DTF for MVS PUT TAPE section for instructions on how to build a MVS PUT tape before proceeding to the PTF INSTALLATION INSTRUCTIONS section. PROBLEMS FIXED IN DTF for MVS SINCE DTF V3.1 DTF for MVS will release PTF kits which fix all known problems to date. The kits are cumulative, ie. SNADTFM_E14031 will have all the fixes that SNADTFM_E13031 has in addition to the fixes made to that kit. Note: A description of all corrections are included in the second file on the PTF tape. Details on accessing this file are included in the PTF INSTALLATION INSTRUCTIONS section. This kit includes all of the following: PTF's made for S-kit SNADTFM_S1031.A SD31001, SD31002, SD31003, SD31004 PTF's made for S-kit SNADTFM_S2031.A SD31005, SD31006, SD31007, SD31008, SD31009, SD31010, SD31011, SD31012 PTF's made for MUP SNADTFM_MUPA031.A SD31013, SD31014, SD31015, SD31016, SD31017, SD31018, SD31019, SD31020, SD31021, SD31022, SD31023 PTF's made for ECO kit SNADTFM_ECO3031.A SD31024, SD31025, SD31026, SD31027 PTF's made for ECO kit SNADTFM_ECO4031.A SD31028, SD31029, SD31030, SD31031, SD31032, SD31033 PTF's made for ECO kit SNADTFM_ECO5031.A SD31034, SD31035, SD31036, SD31037 SD31038, SD31039, SD31040, SD31041 SD31042, SD31043, SD31044 PTF's made for ECO kit SNADTFM_ECO6031.A SD31045, SD31046, SD31047, SD31048 SD31049, SD31050, SD31051, SD31052 SD31053, SD31054, SD31055 PTF's made for ECO kit SNADTFM_ECO7031.A SD31056, SD31057, SD31058, SD31059, SD31060 PTF's made for ECO kit SNADTFM_E8031.A SD31061, SD31062, SD31063, SD31064 SD31065, SD31066, SD31067, SD31068 PTF's made for ECO kit SNADTFM_E9031.A SD31069, SD31070, SD31071, SD31072 SD31073, SD31074 PTF's made for ECO kit SNADTFM_E10031.A SD31075, SD31076, SD31077, SD31078, SD31079 PTF's made for ECO kit SNADTFM_E11031.A SD31080, SD31081, SD31082, SD31083 PTF's made for ECO kit SNADTFM_E12031.A SD31084, SD31085, SD31086 PTF's made for ECO kit SNADTFM_E13031.A SD31087, SD31088, SD31089, SD31090 PTF: SD31087 description DTF unable to handle UCB's whose addresses are above the 16 meg line. DTFRSRC abends with 0C4. PTF: SD31088 description IBM Initiated copy command fails with incorrect userid supplied. PTF: SD31089 description SMS Classes are not honored for new dataset allocations. PTF: SD31090 description DTFRSRC fails with an 0C4 Abend when issuing the TRKCALC macro. DTFMSG DTF0305S No UCB Match message appears when doing a volume scan. UCBSCAN macro in R0300 required LOC=ANY on UCBSCAN macro. PTF's made for ECO kit SNADTFM_E14031.A NONE Note: ECO Kit 14 is issued strictly to correct packaging errors when using IBM SMP/E to install ECO Kit 13. The problem descriptions for ECO Kit 13 should remain in this cover letter. INSTRUCTIONS TO BUILD DTF for MVS PUT TAPE FROM THE OpenVMS SAVESET (Assuming tape drive is $2$MUA0 in the following example) $! Move saveset to temporary directory. $! COPY device:SNADTFM_E14031.A [] $ DELETE TMP.TMP;* $ MOUNT $2$MUA0:/FOREIGN/BLOCK=32000/DENSITY=6250 $ BACKUP SNADTFM_E13031.A/SAVE [] $ COPY TMP.TMP;* $2$MUA0: $ SET MAGTAPE $2$MUA0:/REWIND $10: $ F = F$SEARCH( "TMP.TMP;*", 1 ) $ IF F .EQS. "" THEN GOTO 20 $ DIFF 'F' $2$MUA0: $ GOTO 10 $20: $ DISMOUNT $2$MUA0: $ DELETE TMP.TMP;* Then label this tape as follows: +-----------------------------------------------+ | DECnet/SNA DTF for MVS V3.1 PTF TAPE | | FORMAT: SMP PUT CREATE DATE: | | DENSITY: 6250 LABEL: NL | +-----------------------------------------------+ PTF INSTALLATION INSTRUCTIONS All steps listed here assume the existence of cataloged procedure SMPDTF which should have been created during the installation of DTF for MVS. Note: File 2 on the PTF tape contains descriptions for each of the PTFs. Use the sample JCL listed below to print this file. //PRTPTF JOB ,'PRINT PTF',MSGCLASS=X,CLASS=A //STEP1 EXEC PGM=IEBGENER,REGION=1024K //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=DTF.TAPE, // UNIT=TAPE,VOL=SER=DTFTPE, // DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200), // DISP=(OLD,KEEP),LABEL=(2,NL) //SYSUT2 DD SYSOUT=* //SYSIN DD DUMMY // STEP 1 - RECEIVE The DTF for MVS PTF'S Use the sample JCL listed below to receive DTF for MVS service. //RECVDTF JOB ,RECEIVE,MSGCLASS=X,CLASS=A //***** //***** RECEIVE DTF SERVICE //***** //STEP1 EXEC SMPDTF //SMP.SMPCNTL DD * SET BDY(GLOBAL). RECEIVE SYSMODS LIST. /* //SMP.SMPPTFIN DD DSN=SMPPTFIN,DISP=(OLD,KEEP), // VOL=SER=DTFTPE,LABEL=(1,NL),UNIT=TAPE, // DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200) // STEP 2 - CHECK FOR APPLICABLE HOLDDATA DTF for MVS uses SMP HOLDDATA to inform you when a compo- nent that requires special maintenance handling is be- ing changed. These components are treated as requiring HOLDDATA: o Changes to DTF for MVS/ISPF panels, messages or CLISTs which will require an update to the ISPF libraries. o Changes to DTF exits that may have been customized by the installation. STEP 3 - APPLY THE DTF for MVS PTF'S Use the sample JCL listed below to apply DTF for MVS cor- rective service. //APPLPTF JOB ,'APPLY DTF',MSGCLASS=X,CLASS=A //***** //***** APPLY DTF CORRECTIVE SERVICE //***** //STEP1 EXEC SMPDTF //SMP.SMPCNTL DD * SET BDY(DTFTZN) . APPLY PTFS . // If any PTFs are held then the BYPASS keyword must be used on the APPLY command to allow those PTFs to be applied. STEP 4 - COPY DTF for MVS/VTAM and DTF for MVS TSO CORRECTIVE SERVICE TO SYSTEM LIBRARIES If your site executes DTF for MVS/VTAM and/or DTF for MVS TSO from STEPLIB datasets to the DTFVLOAD and DTFTLOAD datasets then skip this step. If your site modified the installation jobs to include SMP usermods to update the DTF target zone for the new location of the DTF for MVS load modules, then skip this step. Otherwise, you must now re-submit the jobs to copy DTF/VTAM and DTF/TSO components to system libraries. These are located in the original DTF for MVS installation dataset. STEP 5 - DO HOLDDATA REQUIREMENTS If there were any PTFs with HOLDDATA you must do the special requirements of those PTFs at this time. STEP 6 - STOP AND RESTART DTF for MVS JOBS DTF for MVS/VTAM must be stopped and restarted so that an up- dated version of the programs gets loaded. Any current TSO users will not have the updated DTF for MVS TSO pro- grams unless they logoff and log back on. STEP 7 - TEST DTF for MVS Always test the production jobs which use DTF for MVS to insure that the corrective service fixes the prob- lems. Do not proceed to the next step if the existing problem is not corrected or if a new problem has been introduced. STEP 8 - ACCEPT DTF for MVS PTF'S Only do this step after you have verified that DTF for MVS performs in a satisfactory manner. Use the sample JCL listed below to accept DTF for MVS corrective service. //ACCPTF JOB ,'ACCEPT DTF',MSGCLASS=X,CLASS=A //***** //***** ACCEPT DTF CORRECTIVE SERVICE //***** //STEP1 EXEC SMPDTF //SMP.SMPCNTL DD * SET BDY(DTFTZN) . ACCEPT PTFS . // If any PTFs are held then the BYPASS keyword must be used on the ACCEPT command to allow those PTFs to be accepted. Copyright Digital Equipment Corporation 1996. All Rights reserved. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. This ECO has not been through an exhaustive field test process. Due to the experimental stage of this ECO/workaround, Digital makes no representations regarding its use or performance. The customer shall have the sole responsibility for adequate protection and back-up data used in conjunction with this ECO/workaround.