×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I am doing the full system save after an upgrade to V6R1. I did a SAVSYS
and an IPL prior to this (and after loading the cume and various groups).
The SAV abends with CPD3823
Cause . . . . . : File "&2" was not saved because it has an associated
Java
program that could not be saved. The error code is &3. Common error
codes
are:
-- 0001: The Java program is in use and could not be locked.
-- 0002: The Java program target release is more recent than the
target
release on the SAV command.
There is no target release specified on the SAV command. Doesn't look
like anyone changed the command defaults to allow objects to be promoted
from our v6r1 development machine to our V5R4 production machine.
Sample file is:
"/QIBM/ProdData/ServExp/classes/QSF547005769DG10004R03M00505000000001"
Cause: They are all old V4 ptf's that are hanging around.
Cure =
RMVLNK '/QIBM/ProdData/ServExp/classes/QSF*'
Rob Berendt
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.
midrange.com
