Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Charles Mills]

And the answer is ...

Although it is not so documented, apparently __TIMESTAMP__ is a C (not C++) 
-only feature.

I am further informed that __TIMESTAMP__ is not part of the C standard, so I am 
out of luck.

Charles

On Sat, 1 Jul 2023 16:52:20 -0500, Charles Mills  wrote:

>I am using XLC __TIMESTAMP__ for the first (!) time. The source file is in 
>UNIX and definitely has a timestamp. Here is the code
>
>static const char versionMsg[] = "blah blah, Built " __DATE__ " " __TIME__ ", 
>Source timestamp " __TIMESTAMP__ ; 
>
>The message is displaying as
>
>blah blah, Built Jul  1 2023 14:12:35, Source timestamp Mon Jan  1  0:00:01 
>1990   

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Ed Jaffe]

On 7/2/2023 10:50 AM, Itschak Mugzach wrote:

Yes. We are an is. (IronSphere).


Every zPDT has a unique CPU type/serial. It makes sense IBM could open 
up this entitlement for zPDT users.


I'm still puzzled how RDC customers in Dallas could do so. I'm not 
saying it can't be done, but am interested in knowing how it works...



--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/



This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Itschak Mugzach]

This is the link where I open tickets with IBM (zPDT 1090-L01 box) :
https://www.ibm.com/mysupport/s/createrecord/NewCase?productId=flatitem=en_US

Best,
ITschak

*| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere
Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux
and IBM I **|  *

*|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522 986404 **|*
*Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il  **|*





On Sun, Jul 2, 2023 at 9:03 PM Mike Shaw  wrote:

> Itschak,
>
> Ok. We received no such letter and we are partnerworld members and an ISV
> using the ADCD on a zPDT system. This is news to us.
>
> I see that it is for use only to report defects in the ADCD system.
>
> Thanks for that info.
>
> Mike Shaw
> MVS/QuickRef Support Group
> Chicago-Soft, Ltd.
>
>
> On Sun, Jul 2, 2023 at 1:50 PM Itschak Mugzach <
> 0305158ad67d-dmarc-requ...@listserv.ua.edu> wrote:
>
> > Yes. We are an is. (IronSphere). Last week was not the first time we
> opened
> > a ticket. Below is the letter I received from IBM before opening the
> first
> > ticket:
> >
> > Dear zPDT user,
> >
> > The entitlement of your PartnerWorld location ID has been updated to
> > include the ability to report defects in z/OS products. To report a
> defect,
> > please follow the following steps:
> >
> >Go to the PartnerWorld web site ( www.ibm.com/partnerworld ) and sign
> > in
> >to PartnerWorld.
> >
> >After sign in, go to
> >https://www-304.ibm.com/isv/tech/remoteEmail/entryForm.jsp and
> document
> >your findings in PartnerWorld Remote email support. On the "Select
> area
> > of
> >your question" please choose "System z z/OS ADCD (defect only)" from
> the
> >pull down.
> >
> >If this link does not work start at the IBM PartnerWorld home page (
> >www.ibm.com/partnerworld ); select Technical (at the left); select
> >Support from the list (still at the left); on a new page, select
> Problem
> >Reporting (near the top and in the center); select Entitled email (in
> > the
> >box); on a new page, look for the Remote email support box in the
> > center of
> >the page (scrolling may be required) and select Access Remote Email
> >Support. Document your findings in PartnerWorld Remote email support.
> On
> >the "Select area of your question" please choose "System z z/OS ADCD
> >(defect only)" from the pull down.
> >
> > Please note, this support allows qualified zPDT users with a process to
> > resolve defects only. For other needs such as product configuration
> > questions, usability questions, requirements for IBM product
> enhancements,
> > etc. entitlement through another IBM program such as a PartnerWorld Value
> > Package/Option for technical support is required. ISVs wishing to
> purchase
> > SW "how-to" support can do so through the PartnerWorld "IBM Systems and
> > middleware technical support options for software development" option.
> This
> > covers z/OS and Cross-server IBM middleware products and technologies and
> > interfaces to a wide variety of IBM middleware products. Details are
> > provided at: *http://www.ibm.com/isv/welcome/guide/pub_value.html*
> > 
> >
> >
> > בתאריך יום א׳, 2 ביולי 2023 ב-20:45 מאת Mike Shaw <
> > techsupp...@quickref.com
> > >:
> >
> > > Itschak,
> > >
> > > How? Calling the support center? They always ask for a CPU serial
> number.
> > > Are you an ISV?
> > >
> > > Mike Shaw
> > > MVS/QuickRef Support Group
> > > Chicago-Soft, Ltd.
> > >
> > >
> > > On Sun, Jul 2, 2023 at 1:18 PM ITschak Mugzach 
> > wrote:
> > >
> > > > Not true. ZPDT users can open tickets and access shops for ptfs.
> > > >
> > > > ITschak
> > > >
> > > > בתאריך יום א׳, 2 ביולי 2023 ב-19:59 מאת Mike Shaw <
> > > > techsupp...@quickref.com
> > > > >:
> > > >
> > > > > Ed is correct. If you don't license IBM mainframe hardware, you
> can't
> > > get
> > > > > full z/OS support. ISVs using zPDT as their sole z/OS development
> > host
> > > > > can't report problems OR get formal tech support for z/OS. We
> > adapt...
> > > > >
> > > > > Mike Shaw
> > > > > MVS/QuickRef Support Group
> > > > > Chicago-Soft, Ltd.
> > > > >
> > > > >
> > > > > On Sun, Jul 2, 2023 at 12:33 PM Ed Jaffe <
> > edja...@phoenixsoftware.com>
> > > > > wrote:
> > > > >
> > > > > > On 7/2/2023 7:52 AM, David Crayford wrote:
> > > > > > > That's interesting. I was of the understanding that PDT
> customers
> > > > were
> > > > > > > IBM business partners, in which case had to have access to
> > > > > > > Partnerworld and had full access to services to open cases. I
> now
> > > > > > > that's certainly the case for other ISVs that use Dallas
> systems.
> > > > > >
> > > > > > For as long as I can remember, only the owner of the Designated
> > > Machine
> > > > > > (language from the ICA) was entitled to open new cases.
> > > > > >
> > > > > > I was unaware (and am somewhat surprised) that 

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Mike Shaw]

Itschak,

Ok. We received no such letter and we are partnerworld members and an ISV
using the ADCD on a zPDT system. This is news to us.

I see that it is for use only to report defects in the ADCD system.

Thanks for that info.

Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.


On Sun, Jul 2, 2023 at 1:50 PM Itschak Mugzach <
0305158ad67d-dmarc-requ...@listserv.ua.edu> wrote:

> Yes. We are an is. (IronSphere). Last week was not the first time we opened
> a ticket. Below is the letter I received from IBM before opening the first
> ticket:
>
> Dear zPDT user,
>
> The entitlement of your PartnerWorld location ID has been updated to
> include the ability to report defects in z/OS products. To report a defect,
> please follow the following steps:
>
>Go to the PartnerWorld web site ( www.ibm.com/partnerworld ) and sign
> in
>to PartnerWorld.
>
>After sign in, go to
>https://www-304.ibm.com/isv/tech/remoteEmail/entryForm.jsp and document
>your findings in PartnerWorld Remote email support. On the "Select area
> of
>your question" please choose "System z z/OS ADCD (defect only)" from the
>pull down.
>
>If this link does not work start at the IBM PartnerWorld home page (
>www.ibm.com/partnerworld ); select Technical (at the left); select
>Support from the list (still at the left); on a new page, select Problem
>Reporting (near the top and in the center); select Entitled email (in
> the
>box); on a new page, look for the Remote email support box in the
> center of
>the page (scrolling may be required) and select Access Remote Email
>Support. Document your findings in PartnerWorld Remote email support. On
>the "Select area of your question" please choose "System z z/OS ADCD
>(defect only)" from the pull down.
>
> Please note, this support allows qualified zPDT users with a process to
> resolve defects only. For other needs such as product configuration
> questions, usability questions, requirements for IBM product enhancements,
> etc. entitlement through another IBM program such as a PartnerWorld Value
> Package/Option for technical support is required. ISVs wishing to purchase
> SW "how-to" support can do so through the PartnerWorld "IBM Systems and
> middleware technical support options for software development" option. This
> covers z/OS and Cross-server IBM middleware products and technologies and
> interfaces to a wide variety of IBM middleware products. Details are
> provided at: *http://www.ibm.com/isv/welcome/guide/pub_value.html*
> 
>
>
> בתאריך יום א׳, 2 ביולי 2023 ב-20:45 מאת Mike Shaw <
> techsupp...@quickref.com
> >:
>
> > Itschak,
> >
> > How? Calling the support center? They always ask for a CPU serial number.
> > Are you an ISV?
> >
> > Mike Shaw
> > MVS/QuickRef Support Group
> > Chicago-Soft, Ltd.
> >
> >
> > On Sun, Jul 2, 2023 at 1:18 PM ITschak Mugzach 
> wrote:
> >
> > > Not true. ZPDT users can open tickets and access shops for ptfs.
> > >
> > > ITschak
> > >
> > > בתאריך יום א׳, 2 ביולי 2023 ב-19:59 מאת Mike Shaw <
> > > techsupp...@quickref.com
> > > >:
> > >
> > > > Ed is correct. If you don't license IBM mainframe hardware, you can't
> > get
> > > > full z/OS support. ISVs using zPDT as their sole z/OS development
> host
> > > > can't report problems OR get formal tech support for z/OS. We
> adapt...
> > > >
> > > > Mike Shaw
> > > > MVS/QuickRef Support Group
> > > > Chicago-Soft, Ltd.
> > > >
> > > >
> > > > On Sun, Jul 2, 2023 at 12:33 PM Ed Jaffe <
> edja...@phoenixsoftware.com>
> > > > wrote:
> > > >
> > > > > On 7/2/2023 7:52 AM, David Crayford wrote:
> > > > > > That's interesting. I was of the understanding that PDT customers
> > > were
> > > > > > IBM business partners, in which case had to have access to
> > > > > > Partnerworld and had full access to services to open cases. I now
> > > > > > that's certainly the case for other ISVs that use Dallas systems.
> > > > >
> > > > > For as long as I can remember, only the owner of the Designated
> > Machine
> > > > > (language from the ICA) was entitled to open new cases.
> > > > >
> > > > > I was unaware (and am somewhat surprised) that the remote
> development
> > > > > contract somehow entitles an ISV using a z/VM guest on IBM's
> hardware
> > > in
> > > > > Dallas to do so.
> > > > >
> > > > > It's certainly not true for ISVs enrolled in the z/OS ETP.
> Everything
> > > > > must be handled by the IBM Dallas team even if you run the
> > <
> https://www.google.com/maps/search/ed+by+the+IBM+Dallas+team+even+if+you+run+the+?entry=gmail=g
> >code
> > on your
> > > > > own Designated Machine...
> > > > >
> > > > >
> > > > > --
> > > > > Phoenix Software International
> > > > > Edward E. Jaffe
> > > > > 831 Parkview Drive North
> > > > > El Segundo, CA 90245
> > > > > https://www.phoenixsoftware.com/
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> 

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[ITschak Mugzach]

Mike

Since then I opened tickets directly at ibm support portal and not from
partner world

ITschak

בתאריך יום א׳, 2 ביולי 2023 ב-20:50 מאת Itschak Mugzach <
i_mugz...@securiteam.co.il>:

> Yes. We are an is. (IronSphere). Last week was not the first time we
> opened a ticket. Below is the letter I received from IBM before opening
> the first ticket:
>
> Dear zPDT user,
>
> The entitlement of your PartnerWorld location ID has been updated to
> include the ability to report defects in z/OS products. To report a defect,
> please follow the following steps:
>
>Go to the PartnerWorld web site ( www.ibm.com/partnerworld ) and sign
>in to PartnerWorld.
>
>After sign in, go to
>https://www-304.ibm.com/isv/tech/remoteEmail/entryForm.jsp and
>document your findings in PartnerWorld Remote email support. On the "Select
>area of your question" please choose "System z z/OS ADCD (defect only)"
>from the pull down.
>
>If this link does not work start at the IBM PartnerWorld home page (
>www.ibm.com/partnerworld ); select Technical (at the left); select
>Support from the list (still at the left); on a new page, select Problem
>Reporting (near the top and in the center); select Entitled email (in the
>box); on a new page, look for the Remote email support box in the center of
>the page (scrolling may be required) and select Access Remote Email
>Support. Document your findings in PartnerWorld Remote email support. On
>the "Select area of your question" please choose "System z z/OS ADCD
>(defect only)" from the pull down.
>
> Please note, this support allows qualified zPDT users with a process to
> resolve defects only. For other needs such as product configuration
> questions, usability questions, requirements for IBM product enhancements,
> etc. entitlement through another IBM program such as a PartnerWorld Value
> Package/Option for technical support is required. ISVs wishing to purchase
> SW "how-to" support can do so through the PartnerWorld "IBM Systems and
> middleware technical support options for software development" option. This
> covers z/OS and Cross-server IBM middleware products and technologies and
> interfaces to a wide variety of IBM middleware products. Details are
> provided at: *http://www.ibm.com/isv/welcome/guide/pub_value.html*
> 
>
>
> בתאריך יום א׳, 2 ביולי 2023 ב-20:45 מאת Mike Shaw <
> techsupp...@quickref.com>:
>
>> Itschak,
>>
>> How? Calling the support center? They always ask for a CPU serial number.
>> Are you an ISV?
>>
>> Mike Shaw
>> MVS/QuickRef Support Group
>> Chicago-Soft, Ltd.
>>
>>
>> On Sun, Jul 2, 2023 at 1:18 PM ITschak Mugzach 
>> wrote:
>>
>> > Not true. ZPDT users can open tickets and access shops for ptfs.
>> >
>> > ITschak
>> >
>> > בתאריך יום א׳, 2 ביולי 2023 ב-19:59 מאת Mike Shaw <
>> > techsupp...@quickref.com
>> > >:
>> >
>> > > Ed is correct. If you don't license IBM mainframe hardware, you can't
>> get
>> > > full z/OS support. ISVs using zPDT as their sole z/OS development host
>> > > can't report problems OR get formal tech support for z/OS. We adapt...
>> > >
>> > > Mike Shaw
>> > > MVS/QuickRef Support Group
>> > > Chicago-Soft, Ltd.
>> > >
>> > >
>> > > On Sun, Jul 2, 2023 at 12:33 PM Ed Jaffe > >
>> > > wrote:
>> > >
>> > > > On 7/2/2023 7:52 AM, David Crayford wrote:
>> > > > > That's interesting. I was of the understanding that PDT customers
>> > were
>> > > > > IBM business partners, in which case had to have access to
>> > > > > Partnerworld and had full access to services to open cases. I now
>> > > > > that's certainly the case for other ISVs that use Dallas systems.
>> > > >
>> > > > For as long as I can remember, only the owner of the Designated
>> Machine
>> > > > (language from the ICA) was entitled to open new cases.
>> > > >
>> > > > I was unaware (and am somewhat surprised) that the remote
>> development
>> > > > contract somehow entitles an ISV using a z/VM guest on IBM's
>> hardware
>> > in
>> > > > Dallas to do so.
>> > > >
>> > > > It's certainly not true for ISVs enrolled in the z/OS ETP.
>> Everything
>> > > > must be handled by the IBM Dallas team even if you run the
>> code
>> on your
>> > > > own Designated Machine...
>> > > >
>> > > >
>> > > > --
>> > > > Phoenix Software International
>> > > > Edward E. Jaffe
>> > > > 831 Parkview Drive North
>> > > > El Segundo, CA 90245
>> > > > https://www.phoenixsoftware.com/
>> > > >
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> 
>> > > > This e-mail message, including any attachments, appended messages
>> and
>> > the
>> > > > information contained therein, is for the sole use of the intended
>> > > > recipient(s). If you are not an intended recipient or have otherwise
>> > > > received this email message in 

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Itschak Mugzach]

Yes. We are an is. (IronSphere). Last week was not the first time we opened
a ticket. Below is the letter I received from IBM before opening the first
ticket:

Dear zPDT user,

The entitlement of your PartnerWorld location ID has been updated to
include the ability to report defects in z/OS products. To report a defect,
please follow the following steps:

   Go to the PartnerWorld web site ( www.ibm.com/partnerworld ) and sign in
   to PartnerWorld.

   After sign in, go to
   https://www-304.ibm.com/isv/tech/remoteEmail/entryForm.jsp and document
   your findings in PartnerWorld Remote email support. On the "Select area of
   your question" please choose "System z z/OS ADCD (defect only)" from the
   pull down.

   If this link does not work start at the IBM PartnerWorld home page (
   www.ibm.com/partnerworld ); select Technical (at the left); select
   Support from the list (still at the left); on a new page, select Problem
   Reporting (near the top and in the center); select Entitled email (in the
   box); on a new page, look for the Remote email support box in the center of
   the page (scrolling may be required) and select Access Remote Email
   Support. Document your findings in PartnerWorld Remote email support. On
   the "Select area of your question" please choose "System z z/OS ADCD
   (defect only)" from the pull down.

Please note, this support allows qualified zPDT users with a process to
resolve defects only. For other needs such as product configuration
questions, usability questions, requirements for IBM product enhancements,
etc. entitlement through another IBM program such as a PartnerWorld Value
Package/Option for technical support is required. ISVs wishing to purchase
SW "how-to" support can do so through the PartnerWorld "IBM Systems and
middleware technical support options for software development" option. This
covers z/OS and Cross-server IBM middleware products and technologies and
interfaces to a wide variety of IBM middleware products. Details are
provided at: *http://www.ibm.com/isv/welcome/guide/pub_value.html*



בתאריך יום א׳, 2 ביולי 2023 ב-20:45 מאת Mike Shaw :

> Itschak,
>
> How? Calling the support center? They always ask for a CPU serial number.
> Are you an ISV?
>
> Mike Shaw
> MVS/QuickRef Support Group
> Chicago-Soft, Ltd.
>
>
> On Sun, Jul 2, 2023 at 1:18 PM ITschak Mugzach  wrote:
>
> > Not true. ZPDT users can open tickets and access shops for ptfs.
> >
> > ITschak
> >
> > בתאריך יום א׳, 2 ביולי 2023 ב-19:59 מאת Mike Shaw <
> > techsupp...@quickref.com
> > >:
> >
> > > Ed is correct. If you don't license IBM mainframe hardware, you can't
> get
> > > full z/OS support. ISVs using zPDT as their sole z/OS development host
> > > can't report problems OR get formal tech support for z/OS. We adapt...
> > >
> > > Mike Shaw
> > > MVS/QuickRef Support Group
> > > Chicago-Soft, Ltd.
> > >
> > >
> > > On Sun, Jul 2, 2023 at 12:33 PM Ed Jaffe 
> > > wrote:
> > >
> > > > On 7/2/2023 7:52 AM, David Crayford wrote:
> > > > > That's interesting. I was of the understanding that PDT customers
> > were
> > > > > IBM business partners, in which case had to have access to
> > > > > Partnerworld and had full access to services to open cases. I now
> > > > > that's certainly the case for other ISVs that use Dallas systems.
> > > >
> > > > For as long as I can remember, only the owner of the Designated
> Machine
> > > > (language from the ICA) was entitled to open new cases.
> > > >
> > > > I was unaware (and am somewhat surprised) that the remote development
> > > > contract somehow entitles an ISV using a z/VM guest on IBM's hardware
> > in
> > > > Dallas to do so.
> > > >
> > > > It's certainly not true for ISVs enrolled in the z/OS ETP. Everything
> > > > must be handled by the IBM Dallas team even if you run the
> code
> on your
> > > > own Designated Machine...
> > > >
> > > >
> > > > --
> > > > Phoenix Software International
> > > > Edward E. Jaffe
> > > > 831 Parkview Drive North
> > > > El Segundo, CA 90245
> > > > https://www.phoenixsoftware.com/
> > > >
> > > >
> > > >
> > > >
> > >
> >
> 
> > > > This e-mail message, including any attachments, appended messages and
> > the
> > > > information contained therein, is for the sole use of the intended
> > > > recipient(s). If you are not an intended recipient or have otherwise
> > > > received this email message in error, any use, dissemination,
> > > distribution,
> > > > review, storage or copying of this e-mail message and the information
> > > > contained therein is strictly prohibited. If you are not an intended
> > > > recipient, please contact the sender by reply e-mail and destroy all
> > > copies
> > > > of this email message and do not otherwise utilize or retain this
> email
> > > > 

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Mike Shaw]

Itschak,

How? Calling the support center? They always ask for a CPU serial number.
Are you an ISV?

Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.


On Sun, Jul 2, 2023 at 1:18 PM ITschak Mugzach  wrote:

> Not true. ZPDT users can open tickets and access shops for ptfs.
>
> ITschak
>
> בתאריך יום א׳, 2 ביולי 2023 ב-19:59 מאת Mike Shaw <
> techsupp...@quickref.com
> >:
>
> > Ed is correct. If you don't license IBM mainframe hardware, you can't get
> > full z/OS support. ISVs using zPDT as their sole z/OS development host
> > can't report problems OR get formal tech support for z/OS. We adapt...
> >
> > Mike Shaw
> > MVS/QuickRef Support Group
> > Chicago-Soft, Ltd.
> >
> >
> > On Sun, Jul 2, 2023 at 12:33 PM Ed Jaffe 
> > wrote:
> >
> > > On 7/2/2023 7:52 AM, David Crayford wrote:
> > > > That's interesting. I was of the understanding that PDT customers
> were
> > > > IBM business partners, in which case had to have access to
> > > > Partnerworld and had full access to services to open cases. I now
> > > > that's certainly the case for other ISVs that use Dallas systems.
> > >
> > > For as long as I can remember, only the owner of the Designated Machine
> > > (language from the ICA) was entitled to open new cases.
> > >
> > > I was unaware (and am somewhat surprised) that the remote development
> > > contract somehow entitles an ISV using a z/VM guest on IBM's hardware
> in
> > > Dallas to do so.
> > >
> > > It's certainly not true for ISVs enrolled in the z/OS ETP. Everything
> > > must be handled by the IBM Dallas team even if you run the code on your
> > > own Designated Machine...
> > >
> > >
> > > --
> > > Phoenix Software International
> > > Edward E. Jaffe
> > > 831 Parkview Drive North
> > > El Segundo, CA 90245
> > > https://www.phoenixsoftware.com/
> > >
> > >
> > >
> > >
> >
> 
> > > This e-mail message, including any attachments, appended messages and
> the
> > > information contained therein, is for the sole use of the intended
> > > recipient(s). If you are not an intended recipient or have otherwise
> > > received this email message in error, any use, dissemination,
> > distribution,
> > > review, storage or copying of this e-mail message and the information
> > > contained therein is strictly prohibited. If you are not an intended
> > > recipient, please contact the sender by reply e-mail and destroy all
> > copies
> > > of this email message and do not otherwise utilize or retain this email
> > > message or any or all of the information contained therein. Although
> this
> > > email message and any attachments or appended messages are believed to
> be
> > > free of any virus or other defect that might affect any computer system
> > > into
> > > which it is received and opened, it is the responsibility of the
> > recipient
> > > to ensure that it is virus free and no responsibility is accepted by
> the
> > > sender for any loss or damage arising in any way from its opening or
> use.
> > >
> > > --
> > > 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
> >
> --
> ITschak Mugzach
> *|** IronSphere Platform* *|* *Information Security Continuous Monitoring
> for z/OS, x/Linux & IBM I **| z/VM coming soon  *
>
> --
> 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: Where am I going wrong with XLC __TIMESTAMP__ ?

[ITschak Mugzach]

Not true. ZPDT users can open tickets and access shops for ptfs.

ITschak

בתאריך יום א׳, 2 ביולי 2023 ב-19:59 מאת Mike Shaw :

> Ed is correct. If you don't license IBM mainframe hardware, you can't get
> full z/OS support. ISVs using zPDT as their sole z/OS development host
> can't report problems OR get formal tech support for z/OS. We adapt...
>
> Mike Shaw
> MVS/QuickRef Support Group
> Chicago-Soft, Ltd.
>
>
> On Sun, Jul 2, 2023 at 12:33 PM Ed Jaffe 
> wrote:
>
> > On 7/2/2023 7:52 AM, David Crayford wrote:
> > > That's interesting. I was of the understanding that PDT customers were
> > > IBM business partners, in which case had to have access to
> > > Partnerworld and had full access to services to open cases. I now
> > > that's certainly the case for other ISVs that use Dallas systems.
> >
> > For as long as I can remember, only the owner of the Designated Machine
> > (language from the ICA) was entitled to open new cases.
> >
> > I was unaware (and am somewhat surprised) that the remote development
> > contract somehow entitles an ISV using a z/VM guest on IBM's hardware in
> > Dallas to do so.
> >
> > It's certainly not true for ISVs enrolled in the z/OS ETP. Everything
> > must be handled by the IBM Dallas team even if you run the code on your
> > own Designated Machine...
> >
> >
> > --
> > Phoenix Software International
> > Edward E. Jaffe
> > 831 Parkview Drive North
> > El Segundo, CA 90245
> > https://www.phoenixsoftware.com/
> >
> >
> >
> >
> 
> > This e-mail message, including any attachments, appended messages and the
> > information contained therein, is for the sole use of the intended
> > recipient(s). If you are not an intended recipient or have otherwise
> > received this email message in error, any use, dissemination,
> distribution,
> > review, storage or copying of this e-mail message and the information
> > contained therein is strictly prohibited. If you are not an intended
> > recipient, please contact the sender by reply e-mail and destroy all
> copies
> > of this email message and do not otherwise utilize or retain this email
> > message or any or all of the information contained therein. Although this
> > email message and any attachments or appended messages are believed to be
> > free of any virus or other defect that might affect any computer system
> > into
> > which it is received and opened, it is the responsibility of the
> recipient
> > to ensure that it is virus free and no responsibility is accepted by the
> > sender for any loss or damage arising in any way from its opening or use.
> >
> > --
> > 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
>
-- 
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon  *

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Mike Shaw]

Ed is correct. If you don't license IBM mainframe hardware, you can't get
full z/OS support. ISVs using zPDT as their sole z/OS development host
can't report problems OR get formal tech support for z/OS. We adapt...

Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.


On Sun, Jul 2, 2023 at 12:33 PM Ed Jaffe 
wrote:

> On 7/2/2023 7:52 AM, David Crayford wrote:
> > That's interesting. I was of the understanding that PDT customers were
> > IBM business partners, in which case had to have access to
> > Partnerworld and had full access to services to open cases. I now
> > that's certainly the case for other ISVs that use Dallas systems.
>
> For as long as I can remember, only the owner of the Designated Machine
> (language from the ICA) was entitled to open new cases.
>
> I was unaware (and am somewhat surprised) that the remote development
> contract somehow entitles an ISV using a z/VM guest on IBM's hardware in
> Dallas to do so.
>
> It's certainly not true for ISVs enrolled in the z/OS ETP. Everything
> must be handled by the IBM Dallas team even if you run the code on your
> own Designated Machine...
>
>
> --
> Phoenix Software International
> Edward E. Jaffe
> 831 Parkview Drive North
> El Segundo, CA 90245
> https://www.phoenixsoftware.com/
>
>
>
> 
> This e-mail message, including any attachments, appended messages and the
> information contained therein, is for the sole use of the intended
> recipient(s). If you are not an intended recipient or have otherwise
> received this email message in error, any use, dissemination, distribution,
> review, storage or copying of this e-mail message and the information
> contained therein is strictly prohibited. If you are not an intended
> recipient, please contact the sender by reply e-mail and destroy all copies
> of this email message and do not otherwise utilize or retain this email
> message or any or all of the information contained therein. Although this
> email message and any attachments or appended messages are believed to be
> free of any virus or other defect that might affect any computer system
> into
> which it is received and opened, it is the responsibility of the recipient
> to ensure that it is virus free and no responsibility is accepted by the
> sender for any loss or damage arising in any way from its opening or use.
>
> --
> 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: Where am I going wrong with XLC __TIMESTAMP__ ?

[ITschak Mugzach]

zPDT clients can open tickets and order PTFs. I just did it last week for
the certificate issue we had.

ITschak




-- 
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon  *

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Ed Jaffe]

On 7/2/2023 7:52 AM, David Crayford wrote:
That's interesting. I was of the understanding that PDT customers were 
IBM business partners, in which case had to have access to 
Partnerworld and had full access to services to open cases. I now 
that's certainly the case for other ISVs that use Dallas systems.


For as long as I can remember, only the owner of the Designated Machine 
(language from the ICA) was entitled to open new cases.


I was unaware (and am somewhat surprised) that the remote development 
contract somehow entitles an ISV using a z/VM guest on IBM's hardware in 
Dallas to do so.


It's certainly not true for ISVs enrolled in the z/OS ETP. Everything 
must be handled by the IBM Dallas team even if you run the code on your 
own Designated Machine...



--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/



This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Charles Mills]

Yes, @David, perhaps the PDT entitles us to search cases. I shall look into 
that.

I am pretty certain that we cannot open cases nor even order PTFs. We have to 
wait for the "bucket" that comes out from time to time.

I am also quite certain that a Dallas contract give us no access to APARs -- 
other than to open a case with Dallas and ask them to look into it.

Charles

On Sun, 2 Jul 2023 22:52:32 +0800, David Crayford  wrote:

>On 2/7/2023 8:41 pm, Charles Mills wrote:
>> @David:
>>> Looks like a but with XL C++. I would open a case with IBM
>> Alas, I am but a red-headed stepchild. Dallas and PDT customers cannot even 
>> search APARs (which makes NO sense to me) much less open cases.
>That's interesting. I was of the understanding that PDT customers were
>IBM business partners, in which case had to have access to Partnerworld

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[David Crayford]

On 2/7/2023 8:41 pm, Charles Mills wrote:

@David:

Looks like a but with XL C++. I would open a case with IBM

Alas, I am but a red-headed stepchild. Dallas and PDT customers cannot even 
search APARs (which makes NO sense to me) much less open cases.
That's interesting. I was of the understanding that PDT customers were 
IBM business partners, in which case had to have access to Partnerworld 
and had full access to services to open cases. I now that's certainly 
the case for other ISVs that use Dallas systems.


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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Paul Gilmartin]

Thanks for merging replies.  It's irritating when a contributor replies to
multiple plies, in sequence, oblivious that the question has already
been subsequently answered.

On Sun, 2 Jul 2023 07:41:11 -0500, Charles Mills wrote:

>It is a user header. They are both uploaded more or less at the same time, 
>with FileZilla, which I think sets a new timestamp rather than preserving the 
>old (at least by default).
>
Pax, or even zip, might solve that for you.  However, pax might be CRLF
ignorant and zip is notoriously timezone ignorant.


>Alas, I am but a red-headed stepchild. Dallas and PDT customers cannot even 
>search APARs (which makes NO sense to me) much less open cases.
>
That appears to be a guarantee of non-merchantability.  Shame on IBM!


-- 
gil

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Charles Mills]

Thanks all. Attempting to reply to everyone in one note so as not to add to the 
noise.

@Gil:
> 8 seconds after the source.  That's astonishing if it's a system header.

It is a user header. They are both uploaded more or less at the same time, with 
FileZilla, which I think sets a new timestamp rather than preserving the old 
(at least by default).

@David:
> Looks like a but with XL C++. I would open a case with IBM

Alas, I am but a red-headed stepchild. Dallas and PDT customers cannot even 
search APARs (which makes NO sense to me) much less open cases.

If some kind soul wanted to look for an APAR that would be much appreciated. 
z/OS V2R5. 5650-ZOS

Also I tried moving the char[] before any #includes. No better. (It can't be 
the very first line of the program because there are #pragma RUNOPTS that have 
to be before any C code.)

Charles

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Paul Gilmartin]

On Sat, 1 Jul 2023 21:34:25 -0500, Charles Mills wrote:
>
>Seriously, the IBM doc lists it as the value returned if no timestamp is 
>available.
> 
They should specify which timestamp: ISPF, UNIX, FAMS, ... and which dominates
if they disagree.  RCF.

>>What is the timestamp of the "one i#include"?
>
>2023/07/01 14:09:52
>
8 seconds after the source.  That's astonishing if it's a system header.
Is it generated on-the-fly?

>FWIW, the timestamp of the source file is 2023/07/01 14:09:44 

Many years ago, I discovered hat for various settings of the TZ environment
variable there was inconsistency among the __TME__ macro, strftime(),
and the page heading in the SYSPRINT file.  SR.  WAD.  Some years later
it was much mitigated.  I can assume only that a cu$tomer more influential
than I escalated the matter.

-- 
gil

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[David Crayford]

Looks like a but with XL C++. I would open a case with IBM

> xlC -o  posts posts.cpp && ./posts
blah blah, Built Jul  2 2023 10:51:48, Source timestamp Mon Jan  1  0:00:01 1990

> ibm-clang++64 -o  posts posts.cpp && ./posts
blah blah, Built Jul  2 2023 10:52:08, Source timestamp Sun Jul  2 10:49:43 2023

> On 2 Jul 2023, at 5:52 am, Charles Mills  wrote:
> 
> I am using XLC __TIMESTAMP__ for the first (!) time. The source file is in 
> UNIX and definitely has a timestamp. Here is the code
> 
> static const char versionMsg[] = "blah blah, Built " __DATE__ " " __TIME__ ", 
> Source timestamp " __TIMESTAMP__ ; 
> 
> The message is displaying as
> 
> blah blah, Built Jul  1 2023 14:12:35, Source timestamp Mon Jan  1  0:00:01 
> 1990   
> 
> There is one i#include ahead of the char[] and it is also a UNIX file with a 
> timestamp. 
> 
> The exact same code works as expected on Windows.
> 
> What am I doing wrong or missing?
> 
> Charles
> 
> --
> 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: Where am I going wrong with XLC __TIMESTAMP__ ?

[Charles Mills]

On Sat, 1 Jul 2023 20:24:04 -0500, Paul Gilmartin  wrote:

>Does "Mon Jan  1  0:00:01 1990 mean anything to you?

I was in Paris for New Year's. It was fantastic. We drank champagne until it 
ran out, and then moved on to homemade grappa. We sang songs from West Side 
Story. I slept until noon.

Seriously, the IBM doc lists it as the value returned if no timestamp is 
available.

>What is the timestamp of the "one i#include"?

2023/07/01 14:09:52

FWIW, the timestamp of the source file is 2023/07/01 14:09:44 

>What happens with a minimal test such as:

Have not tried.

Charles

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Paul Gilmartin]

On Sat, 1 Jul 2023 21:00:34 -0500, Paul Gilmartin  wrote:

>On Sun, 2 Jul 2023 11:52:43 +1000, Attila Fogarasi wrote:
>
>>Jan 1 1990 is POSIX epoch start in USS, so you are getting 0 for the time
>>value somehow.
>>
>WTF?!  
>
>
Also: 


-- 
gil

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Paul Gilmartin]

On Sun, 2 Jul 2023 11:52:43 +1000, Attila Fogarasi wrote:

>Jan 1 1990 is POSIX epoch start in USS, so you are getting 0 for the time
>value somehow.
>
WTF?!  


-- 
gil

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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

[Attila Fogarasi]

Jan 1 1990 is POSIX epoch start in USS, so you are getting 0 for the time
value somehow.

On Sun, Jul 2, 2023 at 11:24 AM Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:

> On Sat, 1 Jul 2023 16:52:20 -0500, Charles Mills  wrote:
> >...
> >The message is displaying as
> >
> >blah blah, Built Jul  1 2023 14:12:35, Source timestamp Mon Jan  1
> 0:00:01 1990
> >
> >There is one i#include ahead of the char[] and it is also a UNIX file
> with a timestamp.
> >
> Does "Mon Jan  1  0:00:01 1990 mean anything to you?
>
> What is the timestamp of the "one i#include"?
>
> What happens with a minimal test such as:
>
> char *t1 =__TIMESTAMP__;
> #include 
>
> int main( void ) {
> printf( "%s\n", t1 );
> return( 0 ); }
>
> --
> gil
>
> --
> 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: Where am I going wrong with XLC __TIMESTAMP__ ?

[Paul Gilmartin]

On Sat, 1 Jul 2023 16:52:20 -0500, Charles Mills  wrote:
>...
>The message is displaying as
>
>blah blah, Built Jul  1 2023 14:12:35, Source timestamp Mon Jan  1  0:00:01 
>1990   
>
>There is one i#include ahead of the char[] and it is also a UNIX file with a 
>timestamp. 
>
Does "Mon Jan  1  0:00:01 1990 mean anything to you?

What is the timestamp of the "one i#include"?

What happens with a minimal test such as:

char *t1 =__TIMESTAMP__;
#include 

int main( void ) {
printf( "%s\n", t1 );
return( 0 ); }

-- 
gil

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