Deleting MFS

[Mosley, George]

Hello.

Does anyone know how to delete MFS objects from the IMS FORMAT library when a 
transaction retires?

Thanks.

George Mosley
ICBC
433-151 West Esplanade St
North Vancouver, BC
Canada V7M 3H9
604 982-7327

This email and any attachments are intended only for the named recipient and 
may contain confidential and/or privileged material. Any unauthorized copying, 
dissemination or other use by a person other than the named recipient of this 
communication is prohibited. If you received this in error or are not named as 
a recipient, please notify the sender and destroy all copies of this email 
immediately.

Insurance Corporation of British Columbia | 151 W. Esplanade | North Vancouver 
| V7M 3H9
Contact Us

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

Re: Subsystem function code 16, 17, 18, and 19

[esst...@juno.com]

These function calls were briefly discussed in gg66-3131
"The Subsystem Interface in MVS/SP Version 3"

I have never seen these function codes (6, 17, 18, 19) documented anywhere else.

Good luck trying to find a copy.  

-- Original Message --
From: Chip Grantham 
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Subsystem function code 16, 17, 18, and 19
Date: Sun, 22 Jan 2017 14:32:42 +

Good morning listers. 

I've been looking for documentation for writing a subsystem which will respond 
to function code 16 thru 19; open close restart checkpoint.   Can't seem to 
find anything except some brief descriptions in CBTTAPE entries.  Any clues 
would be appreciated. 

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

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

Re: HMC Mail domain

[retired mainframer]

Can't spammers bypass this check by just faking a real domain name in the
FROM: field, something like s...@gmail.com?

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of David Boyes
> Sent: Monday, January 23, 2017 6:20 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: HMC Mail domain
> 
> >I don't understand, do you mean
> >add another MX and A record at
> >the company site domain server,
> 
> In yours. The root problem is actually a good thing - modern mail systems
require that the
> sending domain name actually resolve to something to prevent spammers.
Otherwise, the
> SMTP protocol allows you to put literally anything in the MAIL FROM: part
of the
> transaction. It's possible to turn this feature off by changing the source
(it's one of the things
> in the 'dontblamesendmail' options) but it is a Very Bad Idea.
> 
> As long as the receiving system can resolve whatever the sending system
says to
> *something*, you're good. Thus, an entry in your DNS like this:
> 
> Hmc1 in a 192.168.0.1
>In mx your.mx.server
> 
> will fix it. You don't have to actually be able to connect to it; the name
just has to resolve.
> 
> (In case you care, the error message you posted has only one cause. In the
last few years,
> almost all mail systems have required the sending system to be in DNS to
prevent spammers
> on the theory that it's generally harder to spam if you have to take the
step of registering in
> DNS before you start sending out mail. The NXDOMAIN message is telling you
that the
> receiving system cannot find the sending system in DNS (non-existent
domain) so it's
> bailing.)
> 
> In general, make a practice of putting everything that gets an IP address
into DNS, even if
> you're using DHCP. It's been 35+ years since DNS was invented; it's time.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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

AW: Re: IBM DS8870 3390 EAV and DSCB format 9

[Peter Hunkeler]

> Peter, do you think that if I did a DFDSS DUMP with DELETE PURGE against
> Steve file and then DFDSS RESTORE,
> ISPF I for that restored file (i'm assuming to also an EAV dasd volume)
> ?will be different = not showing job and step names ??



>From what I have read this may be. It depends on where on the EAV volume the 
>data set gets its space allocated upon restore: From the track managed or from 
>the cylinder managed space. If the former, it will have a format-1 DSCB, and 
>there is no place to store this new information. If the latter, I would expect 
>DSS to restore the new attributes from the backup. Unfortunately, I cannot 
>test myself.


--
Peter Hunkeler



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

Re: IBM DS8870 3390 EAV and DSCB format 9

[Toni Cecil]

Hi Peter and Steve,
many thx for your posts.

Peter, do you think that if I did a DFDSS DUMP with DELETE PURGE against
Steve file and then DFDSS RESTORE,
ISPF I for that restored file (i'm assuming to also an EAV dasd volume)
will be different = not showing job and step names ??

Regards, A.Cecilio.

2017-01-23 15:41 GMT+00:00 Steve Smith :

> ISPF I:
>
> Data Set Name . . . . : MHEAV.DUMP.CAT17181.TRS
>
> General Data   Current Allocation
>  Management class . . : **None**Allocated cylinders : 173
>  Storage class  . . . : **None**Allocated extents . : 1
>   Volume serial . . . : EAVNS0
>   Device type . . . . : 3390
>  Data class . . . . . : **None**
>   Organization  . . . : PS Current Utilization
>   Record format . . . : FB  Used cylinders  . . : 173
>   Record length . . . : 1024Used extents  . . . : 1
>   Block size  . . . . : 27648
>   1st extent cylinders: 173
>   Secondary cylinders : 10 Dates
>   Data set name type  : LARGE   Creation date . . . : 2015/06/08
> Referenced date . . : 2015/06/10
> Expiration date . . : ***None***
>   SMS Compressible  . : NO
>   Extended Attributes   OPT
>   Create JobnameMH#TERS
>   Create Stepname   TERSE
>
> sas
>
> On Mon, Jan 23, 2017 at 10:01 AM, Peter Hunkeler  wrote:
>
> > > - I've no EAVs defined so far but dscb format 9 has available new
> fields
> > > like jobname, stepname for each dataset created on a EAV dasd volume.
> >
> >
> > I don't have access to EAV volumes here, so I cannot verify what I'm
> > writing below. I'm sure someone who can will correct me shuold I be
> wrong.
> >
> >
> > Probably, DFdss' PRINT VTOC will display this ionformation. There
> probably
> > are other tools. However, I would not build anything that relies on the
> new
> > fields for production use. It is my understanding that data sets on EAV
> > volumes
> >
> >
> > - Will be represented by an old format-1 DSCB if the data set happens to
> > be allocated in track managed space on the EAV volume, even if the data
> set
> > is EAS-eligible.
> > - The format-1 DSCB will be converted to a format-8/9 pair on the fly,
> > when the data set expands and tghe new extent happens to be in cylinder
> > managed space.
> > - A data set represented by a format-8/9 pair might again be represented
> > by a format-1 DSCB after migrate/recall or backup/revocer, if is is
> > allocated wholely in track managed space.
> >
> >
> > The net: The additional information may get lost.
> >
> >
> > --
> > Peter Hunkeler
> >
> >
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
>
>
>
> --
> sas
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

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

Re: HMC Mail domain

[Rick Troth]

Seconding what David said.
And the beauty here is that this doesn't break anything and doesn't 
expose you to risk.



On 01/23/17 09:20, David Boyes wrote:

I don't understand, do you mean
add another MX and A record at
the company site domain server,

In yours. The root problem is actually a good thing - modern mail systems 
require that the sending domain name actually resolve to something to prevent 
spammers. Otherwise, the SMTP protocol allows you to put literally anything in 
the MAIL FROM: part of the transaction. It's possible to turn this feature off 
by changing the source (it's one of the things in the 'dontblamesendmail' 
options) but it is a Very Bad Idea.


Of all the methods employed to fight spam, some good, some not so good, 
some really counter-productive, this one is great! And it's easy (for 
legitimate senders), downright trivial.




As long as the receiving system can resolve whatever the sending system says to 
*something*, you're good. Thus, an entry in your DNS like this:

Hmc1 in a 192.168.0.1
In mx your.mx.server

will fix it. You don't have to actually be able to connect to it; the name just 
has to resolve.


I like to repeat the entry name, but otherwise David's example is 
perfect except for auto-mis-correct.


   hmcl  in A  192.168.0.1
   hmcl  in  MX  10 your.mx.server.yourdomain.
   hmcl  in  MX  20  alt.mx.server.yourdomain.


Numeric priority is the norm, especially if you have multiple mail 
exchangers.
Optional dot at the end tells resolvers to stop there (and not tack-on 
foreign local domains which would stop the search next iteration, you 
hope).




(In case you care, the error message you posted has only one cause. In the last 
few years, almost all mail systems have required the sending system to be in 
DNS to prevent spammers on the theory that it's generally harder to spam if you 
have to take the step of registering in DNS before you start sending out mail. 
The NXDOMAIN message is telling you that the receiving system cannot find the 
sending system in DNS (non-existent domain) so it's bailing.)


There are other tricks you can try, like SPF records.

I'm also (nominally) a fan of zone signing, but it's not always 
practical. And zone signing would not help this. (And there are storms 
brewing in PKI space.)




In general, make a practice of putting everything that gets an IP address into 
DNS, even if you're using DHCP. It's been 35+ years since DNS was invented; 
it's time.


And it's easy!
DNS is just /not rocket surgery/.

If you're using one of the fancier tools like QIP to handle your DNS, it 
may seem complicated. But it's not.
I recommend people have one or more sub-domains not managed by a formal 
tool. It's just too easy, and frequently really helpful, to have a zone 
or two served by plain ole BIND  
flat files. You don't need a database.


-- R; <><




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

Re: IBM DS8870 3390 EAV and DSCB format 9

[Steve Smith]

ISPF I:

Data Set Name . . . . : MHEAV.DUMP.CAT17181.TRS

General Data   Current Allocation
 Management class . . : **None**Allocated cylinders : 173
 Storage class  . . . : **None**Allocated extents . : 1
  Volume serial . . . : EAVNS0
  Device type . . . . : 3390
 Data class . . . . . : **None**
  Organization  . . . : PS Current Utilization
  Record format . . . : FB  Used cylinders  . . : 173
  Record length . . . : 1024Used extents  . . . : 1
  Block size  . . . . : 27648
  1st extent cylinders: 173
  Secondary cylinders : 10 Dates
  Data set name type  : LARGE   Creation date . . . : 2015/06/08
Referenced date . . : 2015/06/10
Expiration date . . : ***None***
  SMS Compressible  . : NO
  Extended Attributes   OPT
  Create JobnameMH#TERS
  Create Stepname   TERSE

sas

On Mon, Jan 23, 2017 at 10:01 AM, Peter Hunkeler  wrote:

> > - I've no EAVs defined so far but dscb format 9 has available new fields
> > like jobname, stepname for each dataset created on a EAV dasd volume.
>
>
> I don't have access to EAV volumes here, so I cannot verify what I'm
> writing below. I'm sure someone who can will correct me shuold I be wrong.
>
>
> Probably, DFdss' PRINT VTOC will display this ionformation. There probably
> are other tools. However, I would not build anything that relies on the new
> fields for production use. It is my understanding that data sets on EAV
> volumes
>
>
> - Will be represented by an old format-1 DSCB if the data set happens to
> be allocated in track managed space on the EAV volume, even if the data set
> is EAS-eligible.
> - The format-1 DSCB will be converted to a format-8/9 pair on the fly,
> when the data set expands and tghe new extent happens to be in cylinder
> managed space.
> - A data set represented by a format-8/9 pair might again be represented
> by a format-1 DSCB after migrate/recall or backup/revocer, if is is
> allocated wholely in track managed space.
>
>
> The net: The additional information may get lost.
>
>
> --
> Peter Hunkeler
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>



-- 
sas

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

Re: REXX (was How to calculate the JES2 Checkpoint and Spool Space)

[Steve Smith]

Well, REXX goes its own way... I was trying to figure out how to parse "not
4k", and fortunately, just read to the end before investing time in
research.  Working with both REXX and C, the /, %, and // operators give me
a headache.

sas

On Mon, Jan 23, 2017 at 10:09 AM, Robert Prins 
wrote:

> On 2017-01-23 00:13, Dale R. Smith wrote:
>
>> On Sun, 22 Jan 2017 15:00:08 -0700, Lizette Koehler <
>> stars...@mindspring.com>
>> wrote:
>>
> 
>
>> Please note that "variables" like "!4k" start with an exclamation point
>> (!).
>> I would have liked to use just "4k", but REXX does not allow "variable"
>> names
>> that start with a number.
>>
>
> That would bring you in the territory of TRAC, where you can happily
> assign 3 to 4...
>
> Robert
> --
> Robert AH Prins
> robert.ah.prins(a)gmail.com
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>



-- 
sas

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

AW: IBM DS8870 3390 EAV and DSCB format 9

[Peter Hunkeler]

> - I've no EAVs defined so far but dscb format 9 has available new fields
> like jobname, stepname for each dataset created on a EAV dasd volume.


I don't have access to EAV volumes here, so I cannot verify what I'm writing 
below. I'm sure someone who can will correct me shuold I be wrong.


Probably, DFdss' PRINT VTOC will display this ionformation. There probably are 
other tools. However, I would not build anything that relies on the new fields 
for production use. It is my understanding that data sets on EAV volumes


- Will be represented by an old format-1 DSCB if the data set happens to be 
allocated in track managed space on the EAV volume, even if the data set is 
EAS-eligible.
- The format-1 DSCB will be converted to a format-8/9 pair on the fly, when the 
data set expands and tghe new extent happens to be in cylinder managed space.
- A data set represented by a format-8/9 pair might again be represented by a 
format-1 DSCB after migrate/recall or backup/revocer, if is is allocated 
wholely in track managed space.


The net: The additional information may get lost.


--
Peter Hunkeler



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

HMC Mail domain

[David Boyes]

>I don't understand, do you mean 
>add another MX and A record at 
>the company site domain server, 

In yours. The root problem is actually a good thing - modern mail systems 
require that the sending domain name actually resolve to something to prevent 
spammers. Otherwise, the SMTP protocol allows you to put literally anything in 
the MAIL FROM: part of the transaction. It's possible to turn this feature off 
by changing the source (it's one of the things in the 'dontblamesendmail' 
options) but it is a Very Bad Idea.

As long as the receiving system can resolve whatever the sending system says to 
*something*, you're good. Thus, an entry in your DNS like this:

Hmc1 in a 192.168.0.1
   In mx your.mx.server

will fix it. You don't have to actually be able to connect to it; the name just 
has to resolve.

(In case you care, the error message you posted has only one cause. In the last 
few years, almost all mail systems have required the sending system to be in 
DNS to prevent spammers on the theory that it's generally harder to spam if you 
have to take the step of registering in DNS before you start sending out mail. 
The NXDOMAIN message is telling you that the receiving system cannot find the 
sending system in DNS (non-existent domain) so it's bailing.)

In general, make a practice of putting everything that gets an IP address into 
DNS, even if you're using DHCP. It's been 35+ years since DNS was invented; 
it's time. 

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

Re: How to calculate the JES2 Checkpoint and Spool Space

[Robert Prins]

On 2017-01-23 00:13, Dale R. Smith wrote:

On Sun, 22 Jan 2017 15:00:08 -0700, Lizette Koehler 
wrote:



Please note that "variables" like "!4k" start with an exclamation point (!).
I would have liked to use just "4k", but REXX does not allow "variable" names
that start with a number.


That would bring you in the territory of TRAC, where you can happily assign 3 to 
4...


Robert
--
Robert AH Prins
robert.ah.prins(a)gmail.com

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

Re: DFDSS DUMP ADR497E RC246 REAS HA-004

[Toni Cecil]

Hi all,
first of all many thx for your suggestions, here is what probably happened:
- one of my team mates is moving some old DS83K dasd volumes using TDMF to
a new DS8870 and one of the usercats that was opened was also moved (he
didn't noticed). So, catalog address space had the old UCAT location. This
ucat problem was solved after the job run.

But I'll work on DFDSS DUMP INCLUDE filters to avoid a wide catalog search.

Many thx to you all, A.Cecilio.

2017-01-22 21:22 GMT+00:00 Allan Staller :

> Try increasing the region via JCL. You are obtaining the default region
> for your installation.
>
> You *ARE* invoking the CSI interface (under the covers).
>
> You could get this result if there is insufficient storage to return the
> results of the CSI.
>
> HTH,
>
> 
> I'm getting the following error:
> ADR497E (001)-CATLG(08), A CATALOG ERROR OCCURRED WHILE SEARCHING FOR DATA
> SETS BEGINNING WITH 'P'. RETURN CODE IS 246, REASON CODE IS
> HA-004
>
> ADR459E (001)-FILTC(01), ERROR ENCOUNTERED WHILE FILTERING ON THE CATALOG
> ADR415W (001)-DTDSC(04), NO DATA SETS WERE COPIED, DUMPED, OR RESTORED FROM
> ANY VOLUME
>
> I've no REGION specified on jobcard.
>
> I'm running z/Os V2.1
>
> ANy hint is apreciated.
>
> Many thx in advance, A.cecilio
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> ::DISCLAIMER::
> 
> 
> 
>
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only.
> E-mail transmission is not guaranteed to be secure or error-free as
> information could be intercepted, corrupted,
> lost, destroyed, arrive late or incomplete, or may contain viruses in
> transmission. The e mail and its contents
> (with or without referred errors) shall therefore not attach any liability
> on the originator or HCL or its affiliates.
> Views or opinions, if any, presented in this email are solely those of the
> author and may not necessarily reflect the
> views or opinions of HCL or its affiliates. Any form of reproduction,
> dissemination, copying, disclosure, modification,
> distribution and / or publication of this message without the prior
> written consent of authorized representative of
> HCL is strictly prohibited. If you have received this email in error
> please delete it and notify the sender immediately.
> Before opening any email and/or attachments, please check them for viruses
> and other defects.
>
> 
> 
> 
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

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