I don't understand why everyone seems to cast to int * and not void *.
Chasing control blocks is simple in C just using a basic macro.
#include
#include
#include
#include
#define ptr(addr) (void *)((char *)addr)
char * userid(void)
{
void ** ascb; // -> ASCB - address space cont
On 10/02/2018 6:30 AM, Kirk Wolf wrote:
Yes - edcdsect.rexx is something that I wrote many years ago.
I'm happy to share it off-list with anyone - I didn't post it as to avoid
attacks on my my crappy REXX hackery.
There's nothing wrong with that REXX. I use it all the time!
---
On Fri, 9 Feb 2018 17:39:00 -0800, retired mainframer wrote:
>Since pointer arithmetic is performed in terms of object size, you want to
>do the arithmetic on a char pointer because sizeof(char) is guaranteed to be 1.
>
For (some?) members of the Scientific Data Systems (SDS) Sigma Family
http
Since pointer arithmetic is performed in terms of object size, you want to
do the arithmetic on a char pointer because sizeof(char) is guaranteed to be
1.
So replace your statement
ASXB=ASCB+0x6c;
with
ASXB=(int*)((char*)ASCB+0x6c);
which means
convert the type of the address in ASCB
You could fake what you want and/or work around the proposed IBM change by
using DDNAME and a symbol, right?
// SET OPTF=SQLOPTS or one of the other names below
//* Or could be a parm on the PROC invocation
...
//SYSOPTF DD DDNAME=&OPTF
//SQLOPTS DD ...
//OPTCOMP DD ...
//DEBUGCMP DD ...
//NOOP
That is how the C/C++ compiler works. PARM='OPTF(DD:SYSOPTF)' or any other
valid DD name, or DSN, or zFS name. Only one name, though.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Frank Swarbrick
Sent: Friday, February 9, 20
Sure. I know.
Sometimes you want the "right" union organization, not just the elementary
names (which would be sufficient for my trivial example). LayoutA.foo might be
more meaningful than just foo. Does not work if CDSECT has made hash out of
LayoutA.
Charles
-Original Message-
From
On Fri, 9 Feb 2018 23:23:15 +, Frank Swarbrick wrote:
>
>My personal wish would be that OPTFILE have an option to specify one or more
>DD names that it would open, rather than SYSOPTF being the only name. If that
>had been available we'd probably use OPTFILE(DB2OPTF) or some such thing.
>
G
Our shop currently uses OPTFILE in conjunction with the SQL compiler option in
order to supply particular SQL "compile" options to the SQL precompiler for
those COBOL program that have EXEC SQL statements. This allows us to 1) avoid
having a separate "DB2 batch" and "DB2 CICS" procs. We simply
On Fri, 9 Feb 2018 20:51:41 +, Barkow, Eileen wrote:
>... I do not think that we have rexx installed on Unix. ...
>
Rexx is standard on z/OS UNIX; no install necessary.
*However*, IBM supplies some EXECs in UNIX directories, clumsy to access
from batch or TSO. (Use BPXBATCH or BPXWUNIX). O
Charles,
If you look at how EDCDSECT handles ORG/redefines, it will also #defines
symbols that wash the unions out (for convenience).
Yes - edcdsect.rexx is something that I wrote many years ago.
I'm happy to share it off-list with anyone - I didn't post it as to avoid
attacks on my my crappy REX
I think it is local to Kirk.
CDSECT or EDCDSECT is part of the C/C++ compiler package. Search for it in
the User's or Programming Guide -- I forget which. Works decently although
less than perfectly wonderfully.
- Good for MVS data areas because while the result may not be pretty, it is
technical
Has anyone documented the JOBGROUP interaction with existing schedulers?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
If I issue IARV64 something like this
IARV64 REQUEST=GETSTOR,
SEGMENTS=SEGMENTS,
ORIGIN=ORIGIN64,
GUARDSIZE=0,
COND=YES,
FPROT=NO,
USERTKN=NO_USERTKN,
TTOKEN=NO_TTOKEN,
I do not see edcdsect.rexx anywhere. I do not think that we have rexx installed
on Unix.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Seymour J Metz
Sent: Friday, February 09, 2018 3:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re
Manage the pages, e.g., PGRLSE. The typos was the keyboards fault; that's my
story and I'm sticking to it.
OTOH, "mage the pages" would work well if I were into, e.g., D&D.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Dis
Just that issue, or the whole question of what paradigms to use for maintenance
and rollout? Will your presentation be available online?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of Tom
Conle
First, he didn't provide the script, only illustrated its use. Second CLIST and
REXX are two very different languages.
Kirk was showing the OMVS commands to use edcdsect.rexx.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe
Usually when I did a new zOS upgrade I used the /var filesystem that shipped
with that release, as well as the /etc file system. Made whatever necessary
changes to the new /etc that we needed and moved along. Cloned the new /var and
/etc file systems to each system in the sysplex.
Mark Jacobs
I use the Unix diff command to review and differences between what's in my
order and what we have customized on prod
4) Compare the two filesystems and direct output to a file by issuing the shell
command:
diff -r /ServerPac/etc /Service/TST1/etc >
/u/jistxxx/TST1_etc_compare_zos112.txt
Car
Thanks. That seems obvious, but I generally use the SMPE dialog, which lists
only one DDDEF at a time. I did a batch LIST DDDEF and found the same result:
no reference to /etc or /var. I feel much better.
OTOH I think we're remiss in looking for new or modified /etc or /var values in
a new rele
I found this from a PMR I opened about 10 years ago asking about /etc or /var
updates, the response from IBM then was and I believe still is fact;
IBM will not via SMP/E apply place anything in either the /etc or
/var directories, thus it is not necessary to mount them for the
SMP/E apply po
Just did the LIST DDDEF. As suspected, there are no references in my V2.3
target zones for anything /etc or /var or /Service/etc or /Service/var
_
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
david.jou...@53.c
Based on my first-hand experience, the CA SMF DIRECTOR solution is nothing like
any predecessor - has not been for nearly 10 years, possibly more. Any sizable
z/OS site looking at SMF Logstreams should consider this solution, as an
opportunity to help with easing migration and also going forwar
I would like to investigate this issue here, but I don't know how to find a
DDDEF that might point to the /etc or /var file system. As I said previously,
our /etc and /var file systems in production are 'permanent' in that they are
not updated by our maintenance migration. But I am concerned abo
Scott B.,
All good points. However, has CA-SMF Director, nee CA-JARS SMF, nee ManageSMF
come down in price? IIRC, it was less than $30K in 1985. Last I checked it was
closer to 10 times that and that was 10 years ago. And it had basically the
same functionality. For the record, I loved ManageS
>We don't mount the IBM provided /etc /var file systems for actual use. We
>use those to compare with what we have.
>AFAIK, there is NOT any SMPE that updates those anyway, its just what
>Serverpac provides.
>I never mount those filesystems for SMPE maintenance and never get any errors.
SMP/
Review IBM APAR, II11661
http://www-01.ibm.com/support/docview.wss?uid=isg1II11661
It has the same RC & Diagnostic string.
Al Nims
Systems Admin/Programmer 3
UFIT
University of Florida
(352) 273-1298
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU
Also, for consideration, might there also be "frequency of reference", such as
security (ACF2, RACF, etc.) and/or DB2 TRACE (SMF 102 types) -- both of which
may require near real-time access directly from the SMF Logstream, as well as
after the SMF historical offload occurs?
Maintaining separ
Thanks. That lets me know that I need to go back and retest to see if I
am missing something.
Tony Thigpen
Dana Mitchell wrote on 02/09/2018 10:09 AM:
Tony,
I whipped up a quick test, and I'm not seeing that on z/OS 2.1. Here's the
output I get from my DEBUG rexx:
$HASP534 OFF1.STIN
Bernd Oppolzer wrote:
>.. in fact, the original source contains some parts, which are not ANSI C, for
>example cout (which is C++) and iostream.h (which is also part of the C++
>library).
>Because I don't like C++ ... and the program claims to be a C program, I would
>(as a QA person) force th
Tony,
I whipped up a quick test, and I'm not seeing that on z/OS 2.1. Here's the
output I get from my DEBUG rexx:
$HASP534 OFF1.STINACTIVE
REXX DEBUG Detected Message
JOB:4 JES2
JOBID:8
On Fri, Feb 9, 2018 at 6:01 AM, Jantje. wrote:
> On Thu, 8 Feb 2018 08:34:36 -0600, John McKown <
> john.archie.mck...@gmail.com> wrote:
>
> >
> >I think what you are wanting is a way for a step in a batch job to
> "invoke"
> >a REST service. Yes, you can write REXX to do this. But it is basicall
Lionel,
We don't mount the IBM provided /etc /var file systems for actual use. We use
those to compare with what we have. AFAIK, there is NOT any SMPE that updates
those anyway, its just what Serverpac provides. I never mount those
filesystems for SMPE maintenance and never get any errors.
On Feb 9, 2018, at 7:16 AM, Richards, Robert B. wrote:
>
> At what point or percentage (records written/space used) would it be
> advisable to split out 92s, 99s, 120s into their own logstreams? Right now
> they are all in Default. A coworker tested turning on 120s in WebSphere for
> an hour a
I looked at JZOS.
The only jzos samples I have is for 32 bit addressing - I cannot find 64 bit
samples to use with 64 bit java.
IBM gives you a run-around. They point to a non-existent or useless link in
the java jzos readme file and there are no 64 bit samples.
Where are the new JZOS samples if
Have you looked at the JZOS Toolkit? It makes this easy.
String jobName = ZUtil.getCurrentJobname();
WtoMessage msg = new WtoMessage(jobName);
MvsConsole.wto(msg);
Regards
Ray
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Barkow,
On Thu, Feb 8, 2018 at 8:23 PM, zMan wrote:
> "mage the pages"?
>
You need to be a wizard to do that. Or maybe "manage 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 w
Actually I do not like C or C++ very much -
I am just including some c routines in a java program I am writing because
there are a lot of things that cannot be done in
Java, or least I do not know how to do them. But I know java little better than
I know c/c++. In this case, I am using the C cons
I am having a strange error using the MPFEXIT process to call SysRexx
via the MPFTREXX interface.
The following message is issued by JES2:
$HASP534 OFF3.STINACTIVE
but, SysRexx is receiving the following data in MPF2REXXMSG.1:
$HASP534INACTIVE
Notice that the OFF3.ST is missing
How do you run this script?
I tried it under UNIX and MVS as a rexx clist and get all kinds of errors.
$ ccsect
psa.h:: ccsect 1: FSUM7351 not found
edcdsect.rexx: ccsect 4: FSUM7351 not found
$
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Be
Scott,
I am the OP.
I definitely appreciate your comments (and everyone else's too), but no one was
commented on the other half of my questions.
At what point or percentage (records written/space used) would it be advisable
to split out 92s, 99s, 120s into their own logstreams? Right now the
We use XPLINK for our C++ code, and our assembler routines generally use
EDCXPRLG/EDCXEPLG.
There are a bunch of options on these macros that allow you to customize
the kind of XPLINK entry/exit code that you need.
Our prototypes use "C" linkage (which is slightly different and a little
better IMO
It is better IMO to use EDCDSECT and create C header files for the system
DSECTS (PSA, ASCB, ASXB, etc), then you don't have to hard code offsets
into your code.
We have a little rexx shell script that we have been using for a dozen
years that invokes the assembler + EDCDSECT. It is simple to add
Remember when looking at SMF volume, record counts are interesting, but the
bigger issue is the number of bytes written.
We (Peter Enrico and myself) recommend collecting at least 99 subtypes 6, 10,
11, 12, and 14.
6 is especially important as it's the summary service class period information
More simple ... the pointers don't need to be int pointers;
char pointers are just as good:
#include
#include
#include
#include
int main (int argc, char **argv)
{
char *PSA;
char *ASCB;
char *ASXB;
char *ASXBP;
char *JNPI;
char jobname[9];
PSA = (char *) 0x224; /* ad
On Thu, 8 Feb 2018 08:34:36 -0600, John McKown
wrote:
>
>I think what you are wanting is a way for a step in a batch job to "invoke"
>a REST service. Yes, you can write REXX to do this. But it is basically
>doing "low level" sockets programming in REXX using REXX Sockets.
Not necessarily. Using
This is a slightly modified version of jn2.c:
#include
#include
#include
#include
int main (int argc, char **argv)
{
int *PSA;
int *ASCB;
int *ASXB;
int *ASXBP;
int *JNPI;
char jobname[9];
PSA = (int *) 0x224; /* address of PSAAOLD */
ASCB = (int *) *PSA;
printf
.. in fact, the original source contains some parts,
which are not ANSI C, for example cout (which is C++)
and iostream.h (which is also part of the C++ library).
Because I don't like C++ ... and the program claims to be
a C program, I would (as a QA person) force the coder to
eliminate these par
Am 09.02.2018 um 07:45 schrieb Elardus Engelbrecht:
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 igno
50 matches
Mail list logo