home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!usenet.ins.cwru.edu!agate!dog.ee.lbl.gov!ucbvax!MCIMAIL.COM!0003751365
- From: 0003751365@MCIMAIL.COM ("Thomas J. Klotzbach")
- Newsgroups: comp.os.vms
- Subject: DECserver 300 V2.2 TSM Get_char file doesn't work w/ TSM V1.6
- Message-ID: <80921223135508.0003751365NA1EM@mcimail.com>
- Date: 23 Dec 92 13:55:00 GMT
- Sender: usenet@ucbvax.BERKELEY.EDU
- Organization: The Internet
- Lines: 77
-
-
- Just to let folks know of a problem with the TSM$DS3_V22_GET_CHAR.COM
- command file that is supplied with the DECserver 300 for VMS V2.2 software
- release. This problem started after I upgraded from DECserver 300 for VMS 2.1
- to V2.2. We are currently running TSM V1.6.
-
- Here's what happens...
-
- $ @TSM$DS3_V22_GET_CHAR D200B password
- %TSM-I-CREATE, Creating TSM output file
- SYS$SYSROOT:[DECSERVER]TSM$DS3_VXX_TEMP_OUTFILE.TMP;1 22-DEC-1992 19:33:23.45
- Checking TSM version for compatibility with DS300 software version V2.2.
- Version V2.2 software on the target server not supported by this procedure.
-
-
- I have identified the following sections in
- SYS$COMMON:[DECSERVER]TSM$DS3_V22_GET_CHAR.COM as causing the problem and have
- also added the fixes...
- .
- .
- .
- $get_TSM_version:
- $ If Ver Then write sys$output " Checking TSM version for compatibility
- with DS300 software version ''software_version_string'."
- $read_TSM_version:
- $ read /end=done in line
- $ clue = f$extract(0, 8, line)
- $ IF clue .nes. "Terminal" then goto read_TSM_version
- $ version_string = f$element(3," ",line)
- $ IF software_version_string .eqs. "V2.0" then goto clear_v1
- $ IF software_version_string .eqs. "V2.1" then goto clear_v2
- $ !
- $ ! Next line added to fix DS300 V2.2 software compatibility problem
- $ !
- $ IF software_version_string .eqs. "V2.2" then goto clear_v2
- $ write sys$output " Version ''software_version_string' software on the
- target server not supported by this procedure."
- $ goto done
- $!
- $clear_v1:
- $ IF version_string .eqs. "V1.4" then goto TSM_ver_ok
- $ write sys$output ""
- $ write sys$output " ** Warning - This procedure requires TSM version
- V1.4 **"
- $ write sys$output " ** for full compatibility with the target
- server. **"
- $ write sys$output ""
- $ goto DS300_ok
- $clear_v2:
- $ !
- $ ! Added tests for TSM V1.6 and V1.6A to fix TSM version warning message
- $ !
- $ IF (version_string .eqs. "V1.5") .or. -
- (version_string .eqs. "T1.5") .or. -
- (version_string .eqs. "V1.6") .or. -
- (version_string .eqs. "V1.6A") then goto TSM_ver_ok
- $ write sys$output ""
- $ write sys$output " ** Warning - This procedure requires TSM version
- V1.5 **"
- $ write sys$output " ** for full compatibility with the target
- server. **"
- $ write sys$output ""
- $ goto DS300_ok
- .
- .
- .
-
-
- DEC states that they will address the above problem(s) in some sort of
- article in the LAT-DECSERVER DSNlink database.
-
- *******************************************************************************
- Thomas J. Klotzbach MCI Mail: 375-1365
- Genesee Community College Internet: 3751365@mcimail.com
- Batavia, NY 14020 klotzbtj@snybufva.cs.snybuf.edu
- Work: (716) 343-0055 x358
-
-