Thank you Barry! That is exactly what I was looking for. :-)
Dave Cole
At 8/20/2019 03:50 PM, Barry Lichtenstein wrote:
In reply to David and others, a couple of points that might be of interest:
* I confirm that the MIGRATABLE attribute is just as people have
suggested, to indicate wheth
about a Program Object's MIGRATABLE attribute
In reply to David and others, a couple of points that might be of interest:
* I confirm that the MIGRATABLE attribute is just as people have suggested, to
indicate whether a program can be copied between PDS and PDSE, or saved as a
load module
In reply to David and others, a couple of points that might be of interest:
* I confirm that the MIGRATABLE attribute is just as people have suggested, to
indicate whether a program can be copied between PDS and PDSE, or saved as a
load module in a PDS when it was able to be saved as a program o
On Aug 19, 2019, at 3:30 PM, TenEyck, Peter
wrote:
>
> I to struggled to find documentation to answer Dave's question on the
> MIGRATABLE attribute. Where is the MIGRATABLE attribute documented? I would
> like to see it…
There’s some documentation in “z/OS MVS Program Management: User's Guide
be correctly converted to load module format."
//* Peter Ten Eyck
//* Senior Systems Programmer
//* American National
//
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Dave Cole
Sent: Monday, August 19, 2019 4:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL]Re
Thank you Curtis (and the several others who concurred with Curtis).
This is what people here were thinking,
and certainly it makes good sense.
I was hoping to get a definitive link
(or response from an IBMer),
but this consensus is confirmation enough.
Thank You,
Dave
At 8/19/2019 02:26
On Mon, 19 Aug 2019 at 14:41, Mark Jacobs
<0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote:
> That attribute was also set on a load module I just created too, so what
> Curtis said makes sense to me. The load module/program object can
> exist in ether format depending on where it's stored.
> Mike Schwab
> Sent: Monday, August 19, 2019 2:45 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL]Re: Question about a Program Object's MIGRATABLE attribute
>
> Generated by COBOL 5+, as one example. Long names.
>
> https://www.ibm.com/support/knowledgecenter/
-
From: IBM Mainframe Discussion List On Behalf Of
Mike Schwab
Sent: Monday, August 19, 2019 2:45 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL]Re: Question about a Program Object's MIGRATABLE attribute
Generated by COBOL 5+, as one example. Long names.
https://www.ibm.com/support/
Generated by COBOL 5+, as one example. Long names.
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad400/d4289.htm
On Mon, Aug 19, 2019 at 1:26 PM Pew, Curtis G
wrote:
>
> On Aug 19, 2019, at 12:51 PM, Dave Cole wrote:
> >
> > 1) When a Program Object is MIGRATAB
That attribute was also set on a load module I just created too, so what Curtis
said makes sense to me. The load module/program object can exist in ether
format depending on where it's stored.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonm
On Aug 19, 2019, at 12:51 PM, Dave Cole wrote:
>
> 1) When a Program Object is MIGRATABLE, what can it be migrated from? What
> can it be migrated to?
My understanding is that a MIGRATABLE Program Object can be copied to a PDS
load library where it becomes a load module. (Program Objects live
A question has come up regarding something called the MIGRATABLE
attribute that the Binder can assign to a program object. It's not an
attribute that the user can assign, only the binder can assign it in
response to its own analysis of the structure and needs of the Object.
My question is, wha
13 matches
Mail list logo
