Re: Empty GDG dataset handling question

[Miklos Szigetvari]

Hi

Thank you, it is exactly the problem .
The dataset not opened in the job step at all.
But in DASD the new generation exists, so if someone opens the actual 
new generation, he will get an empty disk dataset, but for TAPE he will 
get the last nonempty  one.
If you know this, it is o.k, if not and you change from DISK to TAPE you 
will get a surprise.


On 2/21/2012 2:25 PM, McKown, John wrote:

If I understand you correctly, you're saying that the +1 generation gets catalogued if on a disk, but not if 
on a tape. In a disk SMS environment, the creating of a disk dataset and cataloging thereof causes no problem 
because SMS usually "initializes" the dataset with an end-of-file. In the case of a tape dataset, 
the dataset is "initialized" only if an OPEN is done on it. I don't know how it is done, but z/OS 
does not catalog a tape dataset which was not OPEN'ed. The "solution" is to OPEN the tape dataset. 
If you can't do it in any other way, you could always use IEBGENER to copy a DD DUMMY (0 records) to the 
tape. Either with DISP=(NEW,CATLG) on a step before the current step, changing the current step to 
DISP=(MOD,CATLG). Or on a subsequent step with DISP=(MOD,CATLG). At least, this is how I do it.

--
John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM




-Original Message-
From: IBM Mainframe Discussion List
[mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Miklos Szigetvari
Sent: Tuesday, February 21, 2012 4:11 AM
To: IBM-MAIN@bama.ua.edu
Subject: Empty GDG dataset handling question

Hi

We generated GDG's from a job. ,
The problem is with EMPTY GDG , for DISK , the dataset exists
, for tape
no new generation
Can we handle this from JCL ?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Empty GDG dataset handling question

[Farley, Peter x23353]

I don't know what your shop standards are in the applications area, but for 
audit and traceability reasons EVERY file in our shop always gets at least a 
header record with origin information (i.e., what program/application wrote it 
and on what date at what time) and frequently also a trailer record with a 
record count and termination time.  That kind of standardization would solve 
your problem immediately, unless the program in the job is vendor code for 
which you do not have source.

An all-JCL solution would be to use DISP=(NEW,PASS) for the GDG "creation" step 
and then an IEBGENER step with the GDG as SYSUT2 with DISP=(MOD,CATLG) and 
SYSUT1 of DUMMY.  You might also need RECFM, LRECL and BLKSIZE on the SYSUT1 
DUMMY to get it to work cleanly.

HTH

Peter

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Miklos Szigetvari
Sent: Tuesday, February 21, 2012 5:11 AM
To: IBM-MAIN@bama.ua.edu
Subject: Empty GDG dataset handling question

Hi

We generated GDG's from a job. ,
The problem is with EMPTY GDG , for DISK , the dataset exists , for tape 
no new generation
Can we handle this from JCL ?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Empty GDG dataset handling question

[McKown, John]

If I understand you correctly, you're saying that the +1 generation gets 
catalogued if on a disk, but not if on a tape. In a disk SMS environment, the 
creating of a disk dataset and cataloging thereof causes no problem because SMS 
usually "initializes" the dataset with an end-of-file. In the case of a tape 
dataset, the dataset is "initialized" only if an OPEN is done on it. I don't 
know how it is done, but z/OS does not catalog a tape dataset which was not 
OPEN'ed. The "solution" is to OPEN the tape dataset. If you can't do it in any 
other way, you could always use IEBGENER to copy a DD DUMMY (0 records) to the 
tape. Either with DISP=(NEW,CATLG) on a step before the current step, changing 
the current step to DISP=(MOD,CATLG). Or on a subsequent step with 
DISP=(MOD,CATLG). At least, this is how I do it.

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

 

> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Miklos Szigetvari
> Sent: Tuesday, February 21, 2012 4:11 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Empty GDG dataset handling question
> 
> Hi
> 
> We generated GDG's from a job. ,
> The problem is with EMPTY GDG , for DISK , the dataset exists 
> , for tape 
> no new generation
> Can we handle this from JCL ?
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> 
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Empty GDG dataset handling question

[Miklos Szigetvari]

Hi

We generated GDG's from a job. ,
The problem is with EMPTY GDG , for DISK , the dataset exists , for tape 
no new generation

Can we handle this from JCL ?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Dataset Handling

[Shmuel Metz (Seymour J.)]

In
<[EMAIL PROTECTED]>,
on 02/13/2007
   at 12:58 PM, "Ward, Mike S" <[EMAIL PROTECTED]> said:

>Hello all, I have a small problem and I hoping to get some opinions
>on how to handle it. We had some datasets that were renamed, some of
>these were loadlib and some proclibs. These were development libs so
>there isn't much restriction on the libs themselves, but since some
>were proclibs, Jes2 had some jcl issues.

It's dangerous to allow your users to have write access to libraries
needed by the system, including JES2. You should RACF protect those
libraries and provide a change-control mechanism for updates. Uses can
test their procs with instream procs or with the use of JCLLIB.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Dataset Handling

[james smith]

Why don't you use RACF or whatever security package you have in place?

1) I don't want anyone to create files with any name they come up with.
Except for the systems staff.

<>

2) I would like to be able to restrict the renaming or deletion of
certain files 
<>

James F. Smith
 

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Ward, Mike S
Sent: 14 February 2007 02:59
To: IBM-MAIN@BAMA.UA.EDU
Subject: Dataset Handling

Hello all, I have a small problem and I hoping to get some opinions on
how to handle it. We had some datasets that were renamed, some of these
were loadlib and some proclibs. These were development libs so there
isn't much restriction on the libs themselves, but since some were
proclibs, Jes2 had some jcl issues. What I would like to do or restrict
is: 
1. Unless it's a known prefix that we use, I don't want anyone to create
files with any name they come up with. Except for the systems staff. 
2. I would like to be able to restrict the renaming or deletion of
certain files.

Please, if you would give some feedback on how you would do this it
would be appreciated. 

Thanks

Mike
==
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity
to whom they are addressed.If you have received this email in error please
notify the system manager. This message
contains confidential information and is intended only for the individual
named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please notify the
sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system. If you are
not the intended recipient you are notified that
disclosing, copying, distributing or taking any action in reliance on the
contents of this information is strictly prohibited.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Dataset Handling

[Ed Gould]

On Feb 13, 2007, at 12:58 PM, Ward, Mike S wrote:


Hello all, I have a small problem and I hoping to get some opinions on
how to handle it. We had some datasets that were renamed, some of  
these

were loadlib and some proclibs. These were development libs so there
isn't much restriction on the libs themselves, but since some were
proclibs, Jes2 had some jcl issues. What I would like to do or  
restrict

is:
1. Unless it's a known prefix that we use, I don't want anyone to  
create

files with any name they come up with. Except for the systems staff.
2. I would like to be able to restrict the renaming or deletion of
certain files.

Please, if you would give some feedback on how you would do this it
would be appreciated.

Thanks

Mike

Mike,

I think that your security package is the place to do this.

Ed

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Dataset Handling

[Ward, Mike S]

We are at Z/os V1.7

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Lizette Koehler
Sent: Tuesday, February 13, 2007 1:10 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Dataset Handling

If you are having issues with JES2, what level of JES2 are you at.

There are $PROCLIB statements available that allow you to specify the
files without allocating them in the JES2 PROC.

Second, is to have your customers/users JCL changed to use JCLLIBs.
That way they can control their own proclib data sets without impacting
JES2.

By having everyone use JCLLIBs then you do not need to worry about
standards other than what is already in place.


Just let us know what level of JES2 and then we can see what best fits
your environment.
JCLLIBs have been around since OS/390.  $PROCLIB is fairly recent
addition (z/OS V1.4???)


Lizette

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
==
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity
to whom they are addressed.If you have received this email in error please 
notify the system manager. This message
contains confidential information and is intended only for the individual 
named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please notify the 
sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system. If you are not 
the intended recipient you are notified that
disclosing, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Dataset Handling

[Imbriale, Donald (Exchange)]

To avoid the JES2 JCL issues with missing or renamed proclibs, remove
ALL of them from the JCL and uses the dynamic proclib facility.  This
will allow JES2 to come up even if some of the libraries are missing and
also provides the added benefit of displaying and dynamically changing
your proclib concatenations.

Your security system is your best to place restrictions on data set
names and the actions that can be taken on those data sets.

Don Imbriale

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Ward, Mike S
Sent: Tuesday, February 13, 2007 1:59 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Dataset Handling

Hello all, I have a small problem and I hoping to get some opinions on
how to handle it. We had some datasets that were renamed, some of these
were loadlib and some proclibs. These were development libs so there
isn't much restriction on the libs themselves, but since some were
proclibs, Jes2 had some jcl issues. What I would like to do or restrict
is: 
1. Unless it's a known prefix that we use, I don't want anyone to create
files with any name they come up with. Except for the systems staff. 
2. I would like to be able to restrict the renaming or deletion of
certain files.

Please, if you would give some feedback on how you would do this it
would be appreciated. 



***
Bear Stearns is not responsible for any recommendation, solicitation, 
offer or agreement or any information about any transaction, customer 
account or account activity contained in this communication.
***

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Dataset Handling

[Lizette Koehler]

If you are having issues with JES2, what level of JES2 are you at.

There are $PROCLIB statements available that allow you to specify the files 
without allocating them in the JES2 PROC.

Second, is to have your customers/users JCL changed to use JCLLIBs.  That way 
they can control their own proclib data sets without impacting JES2.

By having everyone use JCLLIBs then you do not need to worry about standards 
other than what is already in place.


Just let us know what level of JES2 and then we can see what best fits your 
environment.
JCLLIBs have been around since OS/390.  $PROCLIB is fairly recent addition 
(z/OS V1.4???)


Lizette

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Dataset Handling

[Ward, Mike S]

Hello all, I have a small problem and I hoping to get some opinions on
how to handle it. We had some datasets that were renamed, some of these
were loadlib and some proclibs. These were development libs so there
isn't much restriction on the libs themselves, but since some were
proclibs, Jes2 had some jcl issues. What I would like to do or restrict
is: 
1. Unless it's a known prefix that we use, I don't want anyone to create
files with any name they come up with. Except for the systems staff. 
2. I would like to be able to restrict the renaming or deletion of
certain files.

Please, if you would give some feedback on how you would do this it
would be appreciated. 

Thanks

Mike
==
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity
to whom they are addressed.If you have received this email in error please 
notify the system manager. This message
contains confidential information and is intended only for the individual 
named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please notify the 
sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system. If you are not 
the intended recipient you are notified that
disclosing, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html