|
View previous topic :: View next topic
|
| Author |
Message |
sgupta9
New User
Joined: 16 Jul 2008
Posts: 12
Location: pune
|
|
|
|
Got the following error during scanning of package:
NON-SMS-MANAGED GDS "DATASET NAME (GDG)" MAY NOT
USE A MODEL DSCB FOR A GDG BASE ON AN SMS-MANAGED VOLUME
Can someone pls assist me. |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
| I don't think it's Endevor related -- it sounds like there's a model DSCB for a GDG on an SMS-managed volume. If your JCL doesn't have a GDG, contact your site support group that handles Endevor to have them clean up the error. |
|
| Back to top |
|
|
sgupta9
New User
Joined: 16 Jul 2008
Posts: 12
Location: pune
|
|
|
|
The dataset for which i am getting the error is a GDG.
The DCB parameter declared is
DCB=(RECFM=FB,LRECL=1000,BLKSIZE=0)
What is the difference between NON-SMS-MANAGED GDG and
SMS-MANAGED GDG
Is it that i need to declare DCB parameter as follows:
DCB=(SYS1.MDSCB,RECFM=FB,LRECL=1000,BLKSIZE=0)
or we need to contact our support group |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
SMS is Storage Management Subsystem. It handles many of the functions of storage management for you; your site support group can set up rules that force certain data sets to be managed by SMS. Some system files cannot be managed by SMS as there could be side effects.
The error message makes it clear that a GDG is involved. You need to contact your site support group since the error message indicates that the model DSCB (in your example SYS1.MDSCB) is already part of the GDG definition and should not be. |
|
| Back to top |
|
|
|
|
