Re: z/OSMF

2023-07-02 Thread Seymour J Metz
24x80 is something that I may have been forced into at work but would never accept on a PC that I conrol. Likewise 14". I currently have a 32" UHD monitor an am considerong 43". YMMV. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Ma

Re: z/OSMF

2023-07-02 Thread Seymour J Metz
Throughout my career, my definitions of large and small monitors kept shifting; where once 17" was something to aspire to, I now consider it to be tiny, and where once 4Kx4K was "if you have to ask you can't afford it", now "8K UHD" is merely expensive. While I have small legacy laptops and am

Re: z/OSMF

2023-07-02 Thread David Purdy
Best investment I made WFH is a $250 43" 4K TV used as a monitor.6 - 8 viewable windows at the same time, plus ergonomic while not having to do a cranium swivel between multiple monitors. .And a tan at the same time... Second best investment was bifocals cut for 18" monitor and closer for readi

Re: Usage of strcasecmp gives implicit function warning even with

2023-07-02 Thread Charles Mills
Not sure what is relevant to your situation and what is not, but FWIW (for C++) I use the following and get no messages on strcasecmp(). #define _LARGE_TIME_API #define _OPEN_SYS_UNLOCKED_EXT 1 #define _POSIX_SOURCE #define _XOPEN_SOURCE_EXTENDED 1 #define

Usage of strcasecmp gives implicit function warning even with

2023-07-02 Thread Eric Erickson
I'm a bit perplexed here. I'm using XL C and the strcasecmp function. I've included and added the #define for _XOPEN_SOURCE_EXTENDED as documented in the library reference, as shown below. But I still get a warning message for it. #define _XOPEN_SOURCE_EXTENDED 1 #include CCN4421 ... I

Re: z/OSMF

2023-07-02 Thread Charles Mills
Bigger monitor + larger 3270 screen format = same size type. Large monitors are under $200. It's your right to stick with 80's display technology but it's not IBM's fault that you then have a problem with more modern screen layouts. Charles On Mon, 3 Jul 2023 01:19:24 +, Shaffer, Terri w

Re: z/OSMF

2023-07-02 Thread David Spiegel
HI Terri, My grandpa drove a Model T ... Should I also drive one? (I'm 67 and have been wearing glasses for almost 55 years. This is irrelevant.) Regards, David On 2023-07-02 21:19, Shaffer, Terri wrote: Amazing for 38 years, I have never used anything bigger than 14" PC monitor. My 24x80 sa

Re: z/OSMF

2023-07-02 Thread Shaffer, Terri
Amazing for 38 years, I have never used anything bigger than 14" PC monitor. My 24x80 saves my eyes at age 60, that I don't need glasses.. So that's a poor excuse. Ms Terri E Shaffer Senior Systems Engineer, z/OS Support: ACIWorldwide - Telecommuter H(412-766-2697) C(412-519-2592) terri.shaf...@

Re: z/OSMF

2023-07-02 Thread David Spiegel
Hi Terri, If you have a 14 inch monitor, it is time to invest in your career and get a proper monitor (e.g. 27 inch minimum). If you're seeing 3-4 lines, it also means that you're probably using Model 2 emulation (24x80). Model 2 for a SysProg wastes a lot of time with unnecessarily scrolling,

Re: z/OSMF

2023-07-02 Thread Shaffer, Terri
Besides having ServerPac back, I want no background checking down. I want batch jobs built to allocate everything, IF a newbie want to trust the process awesome. But in my 38 years, opps doesn’t cut it. Again, just give me a switch. Allow the scripts to build the batch jobs and I will verify

Re: z/OSMF

2023-07-02 Thread Edward Gould
> On Jun 27, 2023, at 6:43 AM, rpinion865 > <042a019916dd-dmarc-requ...@listserv.ua.edu> wrote: > > Remember the days when you could purchase mainframe software? In 1987 we > had UCC-1, UCC-7, and UCC-11. And we had just gotten ACF2, which had just > been acquired by Uccel. The instruct

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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 interes

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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&language=en_US Best, ITschak *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitorin

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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 product

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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 > > ב

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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 problem

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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 1

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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 * -

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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 -- o

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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 understandin

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

2023-07-02 Thread 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 r

Re: A Discussion about RLSE on RAID Drives with Chat GPT-4

2023-07-02 Thread Hobart Spitz
Here goes: Me: Describe the impacts of either disabling the RLSE subparameter of SPACE= in z/OS JCL on RAID drives or having RLSE only release unused extends on RAID drives. Consider the savings in avoiding unnecessary VTOC updates. Which is better, changing RLSE to only release unused extends, or

Re: 0C1 abend

2023-07-02 Thread Binyamin Dissen
On Sun, 2 Jul 2023 06:11:24 -0400 David Spiegel <0468385049d1-dmarc-requ...@listserv.ua.edu> wrote: :>Hi Binyamin AMV"SH, :>My experience with missing DD Statements in HLLs has been x13 ABENDs. A missing DD doesn't directly cause the abend. A READ / WRITE to an unopened file causes a branch t

Re: 0C1 abend

2023-07-02 Thread David Spiegel
Hi Binyamin AMV"SH, My experience with missing DD Statements in HLLs has been x13 ABENDs. Regards, David On 2023-07-02 05:13, Binyamin Dissen wrote: On Sat, 1 Jul 2023 08:03:59 -0500 Bill Giannelli wrote: :>How do I resolve a 0C1 abend. what is normally the cause? For high level languages, u

Re: 0C1 abend

2023-07-02 Thread Binyamin Dissen
On Sat, 1 Jul 2023 08:03:59 -0500 Bill Giannelli wrote: :>How do I resolve a 0C1 abend. what is normally the cause? For high level languages, usually missing DD statement or missing subroutine. -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel -