IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

How to browse RECFM=VBS DSORG=PSE sequential extended data?


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Alan Playford

New User


Joined: 22 Aug 2012
Posts: 48
Location: UK

PostPosted: Fri May 10, 2019 2:59 pm
Reply with quote

The usual ISPF "B" or "V" option to browse a VBS file doesn't work.
For these, we use the "BR" ISPF line command which (IIRC?) came from the CBT tape?
We can thus view RECFM=VBS DSORG=PS files happily.

However, we cannot view extended sequential VBS datasets (DSORG=PSE).
The B line command doesn't work of course ("Invalid record length") but BR also gives this same error.
Even IDCAMS PRINT DUMP COUNT(10) cannot open the file:
IDC3300I ERROR OPENING WINBM.DSNDB06.SYSTSIXS.A0070929
IDC3315I ** RECORD SIZE GREATER THAN 32760 NOT SUPPORTED

However, Db2 is happy to load this dataset into a table.

Is there any known way to view these types of datasets?

In case you're interested, sample dataset characteristics are attached below or see the attachment:

Code:
                             Data Set Information                             
Command ===>                                                                 
                                                                             
Data Set Name . . . . : TPCC.W010.DSNDB06.SYSTSIXS.A0059292                   
                                                                             
General Data                           Current Allocation                     
 Management class . . : **None**        Allocated cylinders : 4               
 Storage class  . . . : EXTENDED        Allocated extents . : 4               
  Volume serial . . . : WCKDS9 +                                             
  Device type . . . . : 3390                                                 
 Data class . . . . . : EXTENDED                                             
  Organization  . . . : PS             Current Utilization                   
  Record format . . . : VBS             Used cylinders  . . : 1               
  Record length . . . : 32768           Used extents  . . . : 1               
  Block size  . . . . : 27966                                                 
  1st extent cylinders: 1                                                     
  Secondary cylinders : 9              Dates                                 
  Data set name type  : EXTENDED        Creation date . . . : 2018/12/03     
                                        Referenced date . . : 2019/05/10     
                                        Expiration date . . : ***None***     
  SMS Compressible  . : NO                                                   
  Extended Attributes   OPT                                                   
  Create Jobname        A0059292                                             
  Create Stepname       UNLOAD9                                               
                                                                             
To display multiple volumes press Enter or enter Cancel to Exit.
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 2454
Location: Hampshire, UK

PostPosted: Fri May 10, 2019 3:17 pm
Reply with quote

Attachments are not appreciated especially when the same can be achieved using the code tags. Original post edited to reflect this.
Back to top
View user's profile Send private message
sergeyken

Senior Member


Joined: 29 Apr 2008
Posts: 2145
Location: USA

PostPosted: Fri May 10, 2019 6:06 pm
Reply with quote

Attribute DSORG=POE is not used in zOS; instead, DSORG=PO,DSNTYPE=LIBRARY is common way to define it.
In ISPF 3.4 screen this library is marked under Dsorg as PO-E, but this value is not used when attributes are to be set.

In your case this is regular DSORG=PO library.

The problem is in RECFM=VBS processing, but not in DSORG=POE.
Back to top
View user's profile Send private message
Alan Playford

New User


Joined: 22 Aug 2012
Posts: 48
Location: UK

PostPosted: Fri May 10, 2019 6:09 pm
Reply with quote

Sergeyken,
This is not a PDSE or Library, it is an extended physical sequential file - PSE.
icon_biggrin.gif
Back to top
View user's profile Send private message
sergeyken

Senior Member


Joined: 29 Apr 2008
Posts: 2145
Location: USA

PostPosted: Fri May 10, 2019 6:33 pm
Reply with quote

Alan Playford wrote:
Sergeyken,
This is not a PDSE or Library, it is an extended physical sequential file - PSE.
icon_biggrin.gif

OK, sorry. Steel sleepy this morning.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8700
Location: Dubuque, Iowa, USA

PostPosted: Fri May 10, 2019 9:19 pm
Reply with quote

Quote:
Is there any known way to view these types of datasets?
Not easily -- the MVS JCL Reference manual states (emphasis by me)
Quote:
Subparameter definition bytes Specifies (1) the length, in bytes, for fixed length records or (2) the maximum length, in bytes, for variable-length records. The value of bytes is: • 1 to 32,760 for non-VSAM data sets. • 1 to 32,761 for VSAM key-sequenced (KS), entry-sequenced (ES), or relative record (RR) data sets. (LRECL does not apply to VSAM linear space, RECORG=LS, data sets.) For VSAM key-sequenced (KS) data sets, a record length must be specified, either explicitly with the LRECL or LIKE parameter, or in the data class for the data set. The record length must be greater than the key length
You might be able to cobble up something using LRECL=X (the manual's recommendation for QSAM when LRECL is more than 32760), but maybe not. If you can recreate the data set with LRECL=32760, BR will probably allow you to browse it. The ISPF manual, however, EXPLICITLY states that VBS is not supported so you cannot use B to browse it. The "invalid record length" messages you cited supports the idea that 32760 is the maximum that can be used by QSAM.
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 917
Location: The Universe

PostPosted: Sat May 11, 2019 2:32 am
Reply with quote

Robert Sample wrote:
...You might be able to cobble up something using LRECL=X (the manual's recommendation for QSAM when LRECL is more than 32760), but maybe not. If you can recreate the data set with LRECL=32760, BR will probably allow you to browse it. The ISPF manual, however, EXPLICITLY states that VBS is not supported so you cannot use B to browse it. The "invalid record length" messages you cited supports the idea that 32760 is the maximum that can be used by QSAM.
It is certainly true you cannot specify LRECL=32768 in JCL. However, an Assembler program can specify LRECL=32768 in a DCB macro in the program. This is common with Assembler programs that create and manipulate SMF data. A workaround that often works (at least with real SMF data) is to copy the data set to a data set with RECFM=VB, LRECL=32756, BLKSIZE=32760. This results in horrible space utilization on disk, but might produce a data set you can browse. If this is real SMF data it will not be particularly helpful, but at least you can browse it.
Back to top
View user's profile Send private message
Alan Playford

New User


Joined: 22 Aug 2012
Posts: 48
Location: UK

PostPosted: Sun May 12, 2019 5:46 pm
Reply with quote

Thanks to all who responded.

Unfortunately, this is a DFDSS restore of a Customer dataset, and so the attributes shouldn't really be altered.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts db2 vs static data COBOL Programming 1
No new posts External data queue (changes?) CLIST & REXX 0
No new posts Pull data using date difference betwe... DB2 6
No new posts fast data scrambling PL/I & Assembler 10
No new posts How to save SYSLOG as text data via P... All Other Mainframe Topics 4
Search our Forums:

Back to Top