MVSFORUMS.com Forum Index MVSFORUMS.com
A Community of and for MVS Professionals
 
 FAQFAQ   SearchSearch   Quick Manuals   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Determine Current Setting of OPTCD.

 
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> TSO and ISPF
View previous topic :: View next topic  
Author Message
David Briars
Beginner


Joined: 03 Jul 2003
Posts: 5
Topics: 2

PostPosted: Mon Sep 15, 2008 10:52 am    Post subject: Determine Current Setting of OPTCD. Reply with quote

How can I obtain the current setting of the Optional Services Code (OPTCD) for a given dataset?

I've checked the Data Set Utility panel (3.2) and performed a LISTCAT ENTRIES(dsname) ALL, and neither appears to give the OPTCD value.

Background: We have a utility (USCCOPY) that does not support certain OPTCD values. 'Something' is changing the OPTCD value of a dataset we have, to a value that is unsupported by the utility.
_________________
===========================
David Briars
Sr. Applications Programmer
Northern Trust Company
Chicago, IL
David_Briars@ntrs.com
===========================
Back to top
View user's profile Send private message
expat
Intermediate


Joined: 01 Mar 2007
Posts: 475
Topics: 9
Location: Welsh Wales

PostPosted: Tue Sep 16, 2008 3:30 am    Post subject: Reply with quote

Take a look HERE to read about OPTCD values.
_________________
If it's true that we are here to help others,
then what exactly are the others here for ?
Back to top
View user's profile Send private message
Bill Dennis
Advanced


Joined: 03 Dec 2002
Posts: 579
Topics: 1
Location: Iowa, USA

PostPosted: Tue Sep 16, 2008 8:52 am    Post subject: Reply with quote

I don't usually think of a dataset having an assigned OPTCD. It's more of an option you choose when you OPEN a file for processing.

What do you think is the OPTCD causing the problem?
_________________
Regards,
Bill Dennis

Disclaimer: My comments on this foorum are my own and do not represent the opinions or suggestions of any other person or business entity.
Back to top
View user's profile Send private message
David Briars
Beginner


Joined: 03 Jul 2003
Posts: 5
Topics: 2

PostPosted: Wed Sep 17, 2008 11:26 am    Post subject: Reply with quote

Bill Dennis wrote:

What do you think is the OPTCD causing the problem?


The OPTCD was 'C' (chained scheduling).

The OPTCD is now 'Z' (search-direct for sequential datasets).

USCCOPY does not support OPTCT = Z.
Back to top
View user's profile Send private message
jgr
Beginner


Joined: 22 Sep 2008
Posts: 3
Topics: 0

PostPosted: Tue Sep 23, 2008 11:31 am    Post subject: Reply with quote

It would require some code to locate and interpret the DS1OPTCD byte in the format-1 DSCB for the dataset...
Back to top
View user's profile Send private message
David Briars
Beginner


Joined: 03 Jul 2003
Posts: 5
Topics: 2

PostPosted: Tue Sep 23, 2008 1:01 pm    Post subject: Reply with quote

1. Thank you expat, for the link to the MVS JCL Reference. I found the section that listed and defined OPTCD values. That was helpful.

2. Thank you jgr for information on how to pull the OPTCD value for a given dataset by looking at the internals of the dataset. I've just been given access to an online utility (Startools) that will display the current OPTCD value for a dataset. So, I'm all set on that front.

Question If by chance, anyone has any thoughts about what process would reset OPTCD values, please feel free to post.

Thank you again,
Dave
Back to top
View user's profile Send private message
jgr
Beginner


Joined: 22 Sep 2008
Posts: 3
Topics: 0

PostPosted: Tue Sep 23, 2008 5:14 pm    Post subject: Reply with quote

Rather than resetting the OPTCD, you should be able to circumvent your problem by adding DCB=OPTCD=C to the applicable USCCOPY DD statement. This should have the effect of overriding the OPTCD in the dataset's DSCB.

If you still in fact do need to reset the DSCB's OPTCD, this can be done via AMASPZAP (error prone and dangerous), or custom code (cleaner and safer).
Back to top
View user's profile Send private message
DavidB
Beginner


Joined: 28 Nov 2007
Posts: 1
Topics: 0

PostPosted: Tue Dec 09, 2008 12:21 pm    Post subject: Reply with quote

I added DCB=OPTCD=C to the input dataset, as shown below:

Code:

//S17GEN EXEC GENERP
//GENR10.SYSUT12  DD DSN=&QUAL1..FOCUS.HPARDIST,
//            DISP=SHR,
//            DCB=OPTCD=C
//GENR10.SYSUT12O DD DSN=&QUAL1..TEST.HPA150.TEST(+1),
//            DISP=(NEW,CATLG,DELETE),
//            SPACE=(CYL,(50,10),,CONTIG),
//            DCB=(RECFM=F,LRECL=4096,BLKSIZE=4096)
//GENR10.SYSUT20  DD *
ONLY ONE RECORD
/*
//GENR10.SYSUT20O DD SYSOUT=*


Unfortunately, I sill obtain the following error message from USCCOPY:

Code:

***********************************************************************
*  PROPRIETARY PRODUCT OF UTILITY SOFTWARE COMPANY   --  PGM=USCCOPY
***********************************************************************
   JOB = DMB3OPT1    STEP = S17GEN      GENR10    TIME STAMP - 12-08-08
  ERR MSG19 -- SYSUT12  FILE REJECTED DUE TO OPTCD, DSORG, OR KEYS

***********************************************************************
*  PROPRIETARY PRODUCT OF UTILITY SOFTWARE COMPANY   --  PGM=USCCOPY
***********************************************************************
   JOB = DMB3OPT1    STEP = S17GEN      GENR10    TIME STAMP - 12-08-08
INPUT  FILE -- SYSUT20    LRECL =    80   BLKSIZE =    80   RECFM = FB
                          SYSIN
               SYSUT20O *** WARNING *** -- DCB PARAMETER(S) COPIED FROM
OUTPUT FILE -- SYSUT20O   LRECL =    80   BLKSIZE =    80   RECFM = FB
                          SYSOUT DATA SET
             1 RECORDS COPIED TO ALL ACCEPTED OUTPUT FILES.


I appreciate all advice, comments, and suggestions received so far.

If anyone has any additional comments, that would be great.

The fundamental issue is, I think, that USCCOPY is sensitive to a OPTCD of 'Z'.

I don't know what at our shop is setting the OPTCD to Z for this one dataset.

If there is a workaround, were I could get USCCOPY to work, that would be fine.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> TSO and ISPF All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


MVSFORUMS
Powered by phpBB © 2001, 2005 phpBB Group