×
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.
On 02-Feb-2012 12:46 , John Allen wrote:
It may be, however this states that this error occurs when they
specify *N for the User Id where I have actually specified the
correct user id
FWiW, per no followup seen, neither with regard to "It may be"
relevant nor about investigation if there really are duplicate jobs.
The APAR MA41459 at the below link in the quoted text from Sean [<ed>
title added] is decidedly more unpredictable than the APAR title\text
might suggest, according to other discussions; e.g. the following
message for a discussion thread involving error message CPF3344 instead,
was noted to have been resolved by that PTF:
Subject: RE: SEU error when pulling up complile spool file listing
http://archive.midrange.com/midrange-l/201202/msg00441.html
That APAR suggests the origin is a side effect of some "new
enhancement to speed up" processing for locating a selected job\SPLF
"had a problem in the implementation." As such, the APAR might better
have included the UNPRED symptom keyword. That, and also given some
discussions on the web have already tracked resolution of difficulties
to the PTFs for that APAR [¿a 7.1 equivalent may exist?; I could not
find, although the APAR includes that release by name], the APAR might
best also have been marked HIPer.
That is to suggest, the applicable LIC VRM ["Release" level R61#] PTF
may provide resolution to the error in this discussion thread [if the
message has not since been found to have been issued properly per
existence of duplicate jobs and splf names], irrespective of what the
APAR claims [very narrowly\specifically] to prevent or correct:
R610 MF54288 1000
R611 MF54289 1000
Regards, Chuck
Porterfield, Sean on Thursday, February 02, 2012 3:09 PM wrote:
Is this relevant?
https://www.ibm.com/support/docview.wss?uid=nas28b2374ff1de127268625791c003c7cda
<ed> APAR title\"abstract": "OSP-MSGCPF3340 CPYSPLF WITH *N FOR USER
NAME RESULTS IN"
John Allen on Thursday, February 02, 2012 14:58 wrote:
I believe I found a PTF to fix this in the past but cannot find
anything using google. Thought maybe someone would remember
this.
I am executing a CPYSPLF command with ALL pertinent parms (file,
job name, user, job nbr and spl number)
CPYSPLF FILE(FR101AP) TOFILE(QTEMP/AROUT)
JOB(518480/CINDY/PRP300) SPLNBR(000072) MBROPT(*ADD)
CTLCHAR(*FCFC)
I get CPF3340 "More than one file with specified name found in
job&5/&4/&3."
I did not think (and still do not think) there can be two spooled
files on a system with the same prtf name, job name, user id, job
nbr and spool number.
I am running this on V6R1
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.