|
Can ObjectConnect be used with the SAVRSTxxx between two systems connected to the same token-ring LAN? One box is V4R5 and the other is V3R2. I have FTP and TelNet working, but want to add SAVRSTxxx to the mix instead of creating a SAVF, FTP, and restoring the SAVF. I must be missing a step, because I don't have it working yet. Here is what I did on each machine: - Load 57xx-SS1 option 22 (ObjectConnect) - Ensure QCMN mode QSOCCT exists with default user QUSER - Ensure QSOCCT max request unit lenth is 32767 and max in pacing is *CALC - Ensure ctl ANYNETCTL is online with link type *ANYNW - Run STRMOD RMTLOCNAME(target) MODE(QSOCCT) LCLLOCNAME(*NETATR) RMTNETID(*NETATR) Both systems show DSPMODSTS with QSOCCT status of "Started", with all conversation counts at zero. V3R2 does not have the APING command, but from V4 to the V3R2 box I get CPD3B53 with sense data 10086021 The remote system did not recognize the TP_name. The description of the recovery for this sense code leads me to believe it is because V3R2 does not have an APING equivalent. Going from the V4 box to the V3 box, a SAVRSTOBJ fails with CPFAD93 and a SNA sense code of x'E01508640002320F'. The short description of this is "Excessive Elapsed Time-No Retry: Excessive time has elapsed while waiting for a required action or event." This leads me to believe some communications configuration is wrong, but I don't know what. Going from the V3 box to the V4 box I get CPFAD84, ObjectConnect/400 internal error, function code 00, return code 88. I can't find these documented in my V4 Backup and Recovery manual which now lists only code like SRCx and TGTx. In the online version of the V3R2 manual, all it says is "If you receive a CPFAD84 message on either the source or target system, use the Analyze Problem (ANZPRB) command to report the problem." The closest I can find in the APAR and knowledge base is for function code FF, return code 7F. I've downloaded and applied the V3R2 PTF for it (SF44756) -- V4Rx equivalents only go to V4R2 -- and I still get the same results. Any clues??? Doug +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.