Re: Silly C problem adding hex 6C

How do you specify the item size when adding? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Thursday, February 08, 2018 11:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Silly C problem adding hex 6C Isn't

Re: codepages

Why do you need windowing? What you need is to mage the pages, and the same issues exist whether the mapping is windowed or direct into virtual memory. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List

Silly C problem adding hex 6C

I am still trying to crawl my way around C/C++ and am just trying to do one simple thing: add value 0X6C to a pointer address (which was originally supplied by this list as a means to get the jobname). something gets added to the pointer but it is not 0x6c. i tried all different combinations of

Re: Silly C problem adding hex 6C

Yes, pointer arithmetic is scaled by the item size. Works kind of like a subscript. If foo is an int* then foo+1 points to the next integer. (IOW foo+4 if you think in assembler terms.) The basic strategy is to cast it to a char* and then back. If you would like, here are two template functions

Re: Silly C problem adding hex 6C

Isn't pointer arithmetic in C scaled by the item size? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Barkow, Eileen Sent: Thursday, February

Re: Insomnia cure

I've always used the RACROUTE Macro Reference manual as a sleep aid. Nightwatch RenBand February 8, 2018 at 11:49 AM > I greatly appreciate all the input I am receiving as I get through the "Insomnia Cure"I mean the > IBM Red Book on Setting up a Sysplex.

Re: Silly C problem adding hex 6C

I tried the simplest solution of casting ASXB to a CHAR * since I am not familiar with templates and basically got the same value as before. I will try some of the other solutions . Thanks everyone $ jn2 ASCB = FB7A00 ASXBC = FB7BB0 int *PSA;

SMF advice on additional logstreams

It was recently noticed that SMF TYPES 92 and 99 are creating a very high percentage of our overall SMF records. Seems to coincide with the implementation of z/OS 2.2, but that is speculative at the moment. Has anyone considered (or implemented) making one or both into their own logstream(s)?

Re: SMF advice on additional logstreams

I have always thought of SMF92 and SMF99 as data of interest primarily for monitoring products - do you have them enabled because of ISV requirements? If there is ISV software that needs to read this SMF data in real time (eg via IEFU8x) but there is no need for historical storage for these

Re: Silly C problem adding hex 6C

(char *)(ASCB + 0x6C) is going to add 0x6c * 4 since ASCB is a pointer to integer, then that will be recast to a char *. (char *)ASCB + 06C will add 0x6c. Define everything as unsigned char *, since that's what you're really pointing to. Then recast to int or whatever when and as actually

Re: SMF advice on additional logstreams

Rob, > do you have them enabled because of ISV requirements? Not intentionally, but you raise a point I need to consider. I am getting ready to install TMONMVS 4.8 which will now have their former standalone USS product integrated within it. I should probably wait until I review the

Re: Silly C problem adding hex 6C

The size of a char in 1 byte. Try (char *) ASXB = (char *) ASCB + 0x6c; /* lazy version */ But that's not really very nice C code. Rather than using int * variables, it would be preferable to provide a C struct describing the layout of storage and using a pointer (or a pointer to a pointer)

Insomnia cure

> I greatly appreciate all the input I am receiving as I get through the "Insomnia Cure"I mean the > IBM Red Book on Setting up a Sysplex. Thank, Fred G.. For several decades I have kept various IBM manuals by my bed as an "insomnia cure". I suspect I will continue after I retire

Re: Silly C problem adding hex 6C

On Thu, 8 Feb 2018 10:22:40 -0600, Allan Kielstra wrote: >The size of a char in 1 byte. Try > >(char *) ASXB = (char *) ASCB + 0x6c; /* lazy version */ > ANSI says a cast may not be used as an L-value. IBM's C compiler enforces this. I once did something like (IIRC?): *(char * *) ASXB +=

Re: Silly C problem adding hex 6C

On Thu, 8 Feb 2018 16:45:18 +, Barkow, Eileen wrote: >Thank you Charles and Seymore. I thought that the problem had something to do >with adding to pointers but >I could not find any doc about it in the manuals. > In fact, subscripting is defined in terms of addition and dereferencing. So:

Re: Silly C problem adding hex 6C

Let's say foo is a struct with some variable length, typical of various MVS data areas. struct foo *pFoo; If you say pFoo++ it increments pFoo by the declared static length of a foo, not by 1. Increments by the declared length of struct foo. If bar is an integer that has the actual length of

Re: Silly C problem adding hex 6C

On Thu, Feb 8, 2018 at 11:39 AM, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Thu, 8 Feb 2018 10:22:40 -0600, Allan Kielstra wrote: > > >The size of a char in 1 byte. Try > > > >(char *) ASXB = (char *) ASCB + 0x6c; /* lazy version */ > > > ANSI says a cast may

Re: Silly C problem adding hex 6C

Now you ran into another problem (((char *)pointer) + offset) is how you want to bind that expression. (And I still think using structs is better) (and you may have to add (int*) in front of the line above) -- For IBM-MAIN

Re: SMF advice on additional logstreams

Not sure about SMF92, but SMF99 are "WLM decision records". Yes they are large volume, but somewhat indispensable. Generally when there is a WLM problem it is extremely difficult or impossible to reproduce. If the SMF99's are not available "during the problem" it is virtually impossible to

Re: Silly C problem adding hex 6C

You use an appropriate type when you declare the pointer. ISAGN for unspec. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Barkow, Eileen Sent:

Re: Silly C problem adding hex 6C

Will not win any prizes from your Computer Science professor but may well be the best way to skin the cat. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richard Rogers Sent: Thursday, February 8, 2018 10:30 AM To:

Re: Delete dataset catch-22

What do you get if you try this in IDCAMS: DEFINE NONVSAM(NAME(MARPACE.GODADDY.CERT) - DEVT(3390) VOLUME(STDL09)) -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Pace Sent: Thursday,

Re: Silly C problem adding hex 6C

To be more pedantic, use additional parantheses: ASXB = (int *) (((char *) ASCB) + 0x6c); Kind regards Bernd Am 08.02.2018 um 20:47 schrieb Bernd Oppolzer: int *ASCB; int  *ASXB; ASXB = ASCB + 0x6c; because ASCB is a pointer to int, and int has sizeof = 4, you are in fact adding 4 *

Re: [EXTERNAL] Re: Delete dataset catch-22

Have you considered using IEHPROGM ? -- Lionel B. Dyck < Mainframe Systems Programmer - TRA -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Pace Sent:

Re: Delete dataset catch-22

Did you specify the FILE when using IDCAMS DEL NVR? // //* DELETES NON-CATALOGED DATASETS WITH IDCAMS //* USE VVR FOR VSAM DATASETS //* USE NVR FOR SAM DATASETS //* CHANGE VOLSER TO MATCH VOLUME THAT DATASET RESIDES ON

Re: Best Practices for z/OS Maintenance

SMP should not be pointing at the live Unix directories. The real question is how to merge new/changed files in the target file system with production files, whether in /etc and /var or elsewhere. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3

Re: Silly C problem adding hex 6C

int *ASCB; int *ASXB; ASXB = ASCB + 0x6c; because ASCB is a pointer to int, and int has sizeof = 4, you are in fact adding 4 * 0x6c to ASCB, that's your problem. use the following notation, and it will work: ASXB = (int *) ((char *) ASCB + 0x6c); first you cast the ASCB to a char *,

Re: [EXTERNAL] Re: Delete dataset catch-22

Or a BR14? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Dyck, Lionel B. (TRA) Sent: Thursday, February 08, 2018 3:21 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: Delete dataset catch-22 Have you considered using

Best Practices for z/OS Maintenance

A question was asked what the best practices are for installing z/OS maintenance to make sure that the /etc and /var files are not replaced by IBM maintenance? (cross posting to MVS OpenEdition and IBM-Main Listservs) Thank you

Re: Delete dataset catch-22

On Thu, Feb 8, 2018 at 1:38 PM, Mark Pace wrote: > I'm trying to delete a dataset that is not cataloged any longer. I'm not > sure why it is not in a catalog, but it is not. I've tried to re-catalog > the dataset, but it doesn't catalog. > > So I have tried to every

Delete dataset catch-22

I'm trying to delete a dataset that is not cataloged any longer. I'm not sure why it is not in a catalog, but it is not. I've tried to re-catalog the dataset, but it doesn't catalog. So I have tried to every combination of IDCAMS DELETE I can think of. NONVSAM NVR etc.. All return ** VSAM

Re: Delete dataset catch-22

Please post the results from idcams DEF RECATALOG. I have seen *VERY FEW* cases that could not be resolved via some combination of DEF RECATALOG, DEL NSCR, DEL VVR, DEL NVR. HTH, -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark

Re: Delete dataset catch-22

Doing the define NONVSAM - got me a little closer - the dataset is now cataloged. But when I use D to delete the datset - IEC614I SCRATCH FAILED - RC 008, DIAGNOSTIC INFORMATION IS (04060020), IKJACCNT,STDL09,MARPACE.GODADDY.CERT 04060020 - Verification of SMS flags failed; caller indicates

Re: Delete dataset catch-22

Yes, I did specify FILE *DELETE MARPACE.GODADDY.CERT FILE(DD1) * IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 102 - REASON CODE IS IGG0CLFM-2 IDC0551I ** ENTRY MARPACE.GODADDY.CERT NOT DELETED IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8 On Thu, Feb 8, 2018

Re: Delete dataset catch-22

The DEFINE NONVSAM(NAME(MARPACE.GODADDY.CERT) - DEVT(3390) VOLUME(STDL09)) got it cataloged again, but I still could not delete the file. So I did DELETE MARPACE.GODADDY.CERT NOSCRATCH to get it removed from the catalog again. Then did a DEFINE NONVSAM -

Re: Silly C problem adding hex 6C

Thank you John, Charles, Seymour, Allan,Paul and everyone else for their help with this. I finally got the program to work and display the job name. Of course there are more efficient ways of coding this using struct and templates, but this is the way I can best understand the strange workings

Re: Best Practices for z/OS Maintenance

For us, both /etc and /var live their own respective file systems that are not touched by standard migration from SMPE install to prod. Hence there's no danger of overlaying installation values. OTOH, as Shmuel says, the problem is how to propagate an updated install value into production.

Re: codepages

"mage the pages"? On Thu, Feb 8, 2018 at 11:15 AM, Seymour J Metz wrote: > Why do you need windowing? What you need is to mage the pages, and the > same issues exist whether the mapping is windowed or direct into virtual > memory. > > > -- > Shmuel (Seymour J.) Metz >

Re: Best Practices for z/OS Maintenance

On 2/8/2018 3:22 PM, Seymour J Metz wrote: SMP should not be pointing at the live Unix directories. The real question is how to merge new/changed files in the target file system with production files, whether in /etc and /var or elsewhere. -- Shmuel (Seymour J.) Metz

Re: FICON PTP CTC & GDPS

Thanks. It's Not my decision... I'll definitely be testing. We have two directors, and I'll be removing one at a time... I'd still like someone to confirm what I want to do is even possible... -- For IBM-MAIN subscribe /

Re: So long and thanks for all the fish

Mark Jacobs wrote: >Sometime this year all existing mainframe processes will be moved to another >fulfillment house(non-mainframe) for Time Inc (now Meredith Corporation) and >Time Customer Service will be shut down. It's been a great 22.5 years here for >me, I might make it to 23 in August

Re: Silly C problem adding hex 6C

Bernd Oppolzer wrote: >To be more pedantic, use additional parantheses: >ASXB = (int *) (((char *) ASCB) + 0x6c); I C ( "I see" ;-D ) Seriously, I find this whole thread very interesting. Just a question please and please excuse my ignorance. Are these discussions about C or C++?

AW: Delete dataset catch-22

Mark, try this, it worked for me to delete uncataloged SMS managed datasets: //STEP1 EXEC PGM=ADRDSSU,PARM='LINECNT=72' //SYSPRINT DD SYSOUT=* //V1 DD DISP=SHR,UNIT=3390,VOL=SER=?? //AUS1 DD DUMMY //SYSINDD *

Re: [EXTERNAL] Re: Best Practices for z/OS Maintenance

I always kept a SERVICE copy of the filesystems that were IBM related and then applied and that is what SMP/E pointed to. Each shop usually has what works best for them, but below are the two main ways that I have done it. 1) Less Work, but Less Control (from SMP/E that is if someone bypasses

Re: REXX say 'location:https://... in a batch job

If you were not aware there is a REXX list that might also be helpful with this. To join, if you have not done so, use this URL, bottom of webpage I think to sign up TSO REXXhttp://www2.marist.edu/htbin/wlvindex?TSO-REXX Lizette > -Original Message- > From: IBM Mainframe

Re: SMF advice on additional logstreams

Allan, At this time, I am not contemplating using NOTYPE on either of them. My original question was whether I should pull them out of DEFAULT or not due to the frequency in which they are created. Still...all comments appreciated. Bob -Original Message- From: IBM Mainframe Discussion

Re: Silly C problem adding hex 6C

Thank you Charles and Seymore. I thought that the problem had something to do with adding to pointers but I could not find any doc about it in the manuals. I am still not sure that I understand how to fix it but I will try based on your info. -Original Message- From: IBM Mainframe

Re: So long and thanks for all the fish

On Thu, 8 Feb 2018 07:01:36 -0500, Mark Jacobs - Listserv wrote: >The new owners didn't want to be in the fulfillment business so they're moving >all Time Inc fulfillment activities to their current service provider. > >Mark Jacobs > Does Meredith use CDS for

REXX say 'location:https://... in a batch job

Hello, I have two REXXs in USS on z/OS that I execute from a URL. The ‘say’ re-directs to a website. Is it possible to execute these in a batch job? And if yes, how will I know they worked? Thanks, Mary Kay 1. This url:https://mvs.humana.com/HUMcgi/url1.sh executes this REXX to

Re: So long and thanks for all the fish

Yes on the CDS question. Dana Mitchell February 8, 2018 at 8:58 AM Does Meredith use CDS for fulfillment? CDS used to be a mainframe shop here in town, they converted to IBM i years ago. Meredith was also a good sized mainframe shop in the past too, but sadly no

Re: So long and thanks for all the fish

The new owners didn't want to be in the fulfillment business so they're moving all Time Inc fulfillment activities to their current service provider. Mark Jacobs Jackson, Rob February 7, 2018 at 8:55 PM That is a crying, damn shame. Inherently foolish and

Re: REXX say 'location:https://... in a batch job

You might consider executing curl in your rexx to obtain the data from the remote server. You can do that in a batch job. -- Donald Grinsell, Systems Programmer Enterprise Technology Services Bureau SITSD/Montana Department of Administration 406.444.2983 (D) "When they kick out your front

Re: So long and thanks for all the fish

On 2/8/2018 5:01 AM, Mark Jacobs - Listserv wrote: The new owners didn't want to be in the fulfillment business so they're moving all Time Inc fulfillment activities to their current service provider I've found Time Magazine unfulfilling for a number of years already ... :) -- Jack J.

Re: REXX say 'location:https://... in a batch job

On Thu, Feb 8, 2018 at 8:07 AM, Mary Kay Tubello wrote: > Hello, > > I have two REXXs in USS on z/OS that I execute from a URL. The ‘say’ > re-directs to a website. Is it possible to execute these in a batch job? > And if yes, how will I know they worked? > ​Basically,

Re: REXX say 'location:https://... in a batch job

Yes, but they won't do what you want. You'll see the output instead of passing it to a web browser. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@listserv.ua.edu] on behalf of Mary Kay Tubello