31-bit
Daniel McLaughlin
the instructions on modifying LE into separate libraries, but that was on a PC
that smoked out.
Do any of you fine people have those instructions? I think it's either CEEDOPT
or CEEUOPT...
Thank you in advance.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Ted MacNEIL
I don't understand your problem!
Most applications run in 31-bit land.
Under z/OS, only data is in 64-bit land.
-
Too busy driving to stop for gas!
Jeffrey Deaver
exists. I've tried every trick I can think of to delete the catalog entry,
nothing is working. Ideas? Ran a Diag on the catalog, got this...
IDC21364I ERROR DETECTED BY DIAGNOSE:
ICFCAT ENTRY: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 (A)
RECORD: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 /00
OFFSET: X'0063'
REASON: 51 - VVDS ENTRY NOT FOUND. SCAN VVDS FAILED.
IDC21365I ICFCAT RECORD DISPLAY:
RECORD: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 /00
000000 007D004D C1000001 2DC7D9D6 E4D74BD7 C3D3C1C9 D4E24BD3 D6C14BE3
D1D1F4F9 *.'.(A....GROUP.PCLAIMS.LOA.TJJ49*
000020 D4C9C74B C4F2F0F0 F2F2F6F2 4BE3F1F4 F3F9F2F5 F5000019 26000007
D7D9C9D4 *MIG.D2002262.T1439255.......PRIM*
000040 C1D9E800 000008E2 E3C1D5C4 C1D9C400 1401FFFF FFFFFFFF FFFF0890
243F0000 *ARY....STANDARD.................*
000060 0C000000 1A0480D7 D9D2F0F0 F1301020 0F880001 00000000 00000020 00
*.......PRK001................ *
Thanks.
Jeffrey Deaver, Engineer
Systems Engineering
jeffrey...@securian.com
651-665-4231(v)
IS - "Creating competitive advantage with technology. Providing service
that excels."
OSS - " Where Innovation Happens"
Don Holstein
Thanks.
-----------------------------------------
The information contained in this e-mail message is intended only
for the personal and confidential use of the recipient(s) named
above. This message may be an attorney-client communication and/or
work product and as such is privileged and confidential. If the
reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are
hereby notified that you have received this document in error and
that any review, dissemination, distribution, or copying of this
message is strictly prohibited. If you have received this
communication in error, please notify us immediately by e-mail, and
delete the original message.
O'Brien, David W. [C] , NIH/CIT
Idcams
Delete dataset.name NSCR
________________________________
From: Jeffrey Deaver [mailto:Jeffrey...@SECURIAN.COM]
Sent: Fri 8/22/2008 4:05 PM
To: IBM-...@BAMA.UA.EDU
Subject: Catalog Error - Can't delete dataset
Jeffrey Deaver
Yep. Got this...
IDCAMS SYSTEM SERVICES TIME: 15
DELETE -
GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 -
PURGE -
NOSCRATCH
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFO-54
IDC0551I ** ENTRY GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 NOT
IDC0551I DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8
O'Brien, David W. [C] , NIH/CIT
________________________________
From: Jeffrey Deaver [mailto:Jeffrey...@SECURIAN.COM]
Johnston, Robert E
| 54 Explanation: DELETE failed because the data set is
being renamed but it has not completed.
| Programmer Response: Rename the data set with the
| IDCAMS ALTER command and then delete it.
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@BAMA.UA.EDU] On
> Behalf Of Jeffrey Deaver
> Sent: Friday, August 22, 2008 3:22 PM
> To: IBM-...@BAMA.UA.EDU
Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Linda Mooney
Linda Mooney
Jeffrey Deaver
>
>| 54 Explanation: DELETE failed because the data set is
> being renamed but it has not completed.
>
> | Programmer Response: Rename the data set with the
> | IDCAMS ALTER command and then delete it.
Sort of. The name tells me that this file is probably left over from a
simple process we have which automates the reallocation of files. People
use it to expand/change the allocation. File is temp copied to the file in
question, original file is deleted and reallocated, temp copy is copied
back and then (suppose to be) deleted.
Problem with the instruction set above - rename it to what?
Jeffrey Deaver, Engineer
Systems Engineering
jeffrey...@securian.com
651-665-4231(v)
IS - "Creating competitive advantage with technology. Providing service
that excels."
OSS - " Where Innovation Happens"
----------------------------------------------------------------------
Jeffrey Deaver
Tried it both ways. I get the same result without the PURGE.
Jeffrey Deaver
So just to try renaming it to something... Seems like everything I try
really wants the physical file there - which doesn't make sense since I've
run into rouge catalog entries before and not had trouble cleaning them up.
This one is being stubborn.
ALTER GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 -
NEWNAME(GROUP.PCLAIMS.LOA.JUNK) -
CAT(ISV.SICF.USERCAT.VSYSP35)
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 94 - REASON CODE IS IGG0CLRN-8
8 Explanation: OBTAIN did not find requested format-1
DSCB on specified volume.
Programmer Response: Ensure that the correct volume is
mounted
Arturo
the file deleted. Since, you didn’t post the commands that you’ve used. I
figure that I send you what has worked for me in the pass. Hope this helps.
Just review the parms in manual before using to make sure that we’ll work for
you.
1.
********************************
//DELNVR EXEC PGM=IDCAMS
//DD1 DD VOL=SER=XXXXXX,UNIT=3390,DISP=OLD
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE DATASET NAME -
FILE(DD1) -
NVR
2.
********************************
//DELNOSC EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE DATASET.NAME.MAR0707 -
PURGE -
CAT(USERCAT.NAME)
3.
************************************
//STEP13 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE DATASET.NAME NSCR
4. For this one you need to leave the ver… as is.
************************************
//SYSIN DD *
ZAP BCS(USERCAT.NAME) -
DELETE(KEY(DATASET.NAME) -
VER(04,C'A'))
********************************
Steve Comstock
> We still have some legacy systems that run in 31-bit land.
Really. So if your legacy systems are AMODE 31, what are your
new systems? All 64-bit all the time?
:-)
Once long ago I had
> the instructions on modifying LE into separate libraries, but that was on a PC
> that smoked out.
>
> Do any of you fine people have those instructions? I think it's either CEEDOPT
> or CEEUOPT...
You can certainly create a CEEUOPT member and link it to
each program that is AMODE 24 (which is what I think you
meant above), since the default now is AMODE 31. Or you
can supply the value at run time in the EXEC statement
PARM field. Or, if you are z/OS 1.7 or later you can
set up members in a PDS and point to the correct one with
a DD statement of CEEOPT. There are even more, but these
seem most practical to me.
>
> Thank you in advance.
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-393-8716
http://www.trainersfriend.com
z/OS Application development made easier
* Our classes include
+ How things work
+ Programming examples with realistic applications
+ Starter / skeleton code
+ Complete working programs
+ Useful utilities and subroutines
+ Tips and techniques
==> Check out the Trainer's Friend Store to purchase z/OS <==
==> application developer toolkits. Sample code in four <==
==> programming languages, JCL to Assemble or compile, <==
==> bind and test. <==
==> http://www.trainersfriend.com/TTFStore/index.html <==
Staller, Allan
DD1 points to the correct UCAT
HTH,
<snip>
So just to try renaming it to something... Seems like everything I try
really wants the physical file there - which doesn't make sense since
I've
run into rouge catalog entries before and not had trouble cleaning them
up.
This one is being stubborn.
ALTER GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 -
NEWNAME(GROUP.PCLAIMS.LOA.JUNK) -
CAT(ISV.SICF.USERCAT.VSYSP35)
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 94 - REASON CODE IS IGG0CLRN-8
8 Explanation: OBTAIN did not find requested format-1
DSCB on specified volume.
</snip>
Programmer Response: Ensure that the correct volume is
----------------------------------------------------------------------
Jeffrey Deaver
>************************************
>//SYSIN DD *
> ZAP BCS(USERCAT.NAME) -
> DELETE(KEY(DATASET.NAME) -
> VER(04,C'A'))
>********************************
Well, I'd love to try the zap, but I don't have CatalogRecovery +. Bummer.
Nothing else is working.
Thanks for all the tips so far, I'll keep trying stuff and let you know
what becomes of this.
Jeffrey Deaver, Engineer
Systems Engineering
jeffrey...@securian.com
651-665-4231(v)
IS - "Creating competitive advantage with technology. Providing service
that excels."
OSS - " Where Innovation Happens"
----------------------------------------------------------------------
Brian Peterson
otherwise un-delete-able data set. The VVDSFIX tool's DELBCSR command did
the trick for me.
//*DELBCSR - DELETE BCS RECORD will erase a BCS record. **
//* The purpose of this command is to erase a catalog **
//* record that has a bad name such as a special **
//* character imbedded within the name that IDCAMS thinks **
//* is bad and prevents the DELETE from working. **
//* **
Google VVDSFIX which shows the following link as the tool source:
www-1.ibm.com/support/docview.wss?uid=isg3S1000618
Brian
On Mon, 25 Aug 2008 10:15:42 -0500, Jeffrey Deaver wrote:
>Well, I'd love to try the zap, but I don't have CatalogRecovery +. Bummer.
>Nothing else is working.
>
>Thanks for all the tips so far, I'll keep trying stuff and let you know
>what becomes of this.
>
>Jeffrey Deaver, Engineer
----------------------------------------------------------------------
Jeffrey Deaver
>otherwise un-delete-able data set. The VVDSFIX tool's DELBCSR command did
>the trick for me.
SHAZAM! It worked. Thanks!
Jeffrey Deaver, Engineer
Systems Engineering
jeffrey...@securian.com
651-665-4231(v)
IS - "Creating competitive advantage with technology. Providing service
that excels."
OSS - " Where Innovation Happens"
----------------------------------------------------------------------
Veilleux, Jon L
Thanks,
Jon
Jon L. Veilleux
veill...@aetna.com
(860) 636-2683
This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna
Itschak Mugzach
structure is much simpler then and bypasses VVDS. You should be familiar
with VTOP dump, zap and format-x DSCBs. Don't try it at home if you are not
familiar with it! If you have CA-Disk, you can use a utility to this for
you.
ITschak
Jeffrey Deaver
>structure is much simpler then and bypasses VVDS. You should be familiar
>with VTOP dump, zap and format-x DSCBs. Don't try it at home if you are
not
>familiar with it! If you have CA-Disk, you can use a utility to this for
>you.
There was no VTOC entry for the dataset on the volume.
Jeffrey Deaver, Engineer
Systems Engineering
jeffrey...@securian.com
651-665-4231(v)
IS - "Creating competitive advantage with technology. Providing service
that excels."
OSS - " Where Innovation Happens"
----------------------------------------------------------------------
Roland Schiradin
will contact oflline. This version will be released in the next few weeks before
z/OS R10 goes GA.
Roland
>Roland, how can I contact you to get the beta version of Showzos?
>Thanks,
>Jon
>
----------------------------------------------------------------------