> Must the host environment be SYSTEM?
That's just one of the example it was convenient to copy. The token after
address must be a symbol or a string literal that matches a registered
environment.
> Regina's "popen" is just one of the ADDRESS ... STEM variants;
ITYM that it is equivalent. Of
It does seem implausible, but who knows. It is all in the parsing and for now
we can only really be sure that it means what it means. Therefore I emailed
the DFSMS architect I spoke with and requested clarification. I will share
when/if she responds.
HTH,
Mike
-Original Message-
On Sun, 17 May 2020 02:13:16 +, Seymour J Metz wrote:
>> What does it lack?
>
>ADDRESS SYSTEM "myprog" WITH INPUT STEM somefood. ,
>OUTPUT STREAM 'prg.out' ERROR STEM oops.
>
Ah! I had seen that in Regina but didn't know it is ANSI.
Must the host environment be SYSTEM?
Extended format (VSAM and non-VSAM)
Or
(Extended format VSAM) and (non-VSAM)
?
The former is redundant or overly wordy: why not just say "extended format
datasets"?
The latter, OTOH, seems implausible to me. Why would they do all non-VSAM
but only extended format VSAM?
Charles
> What does it lack?
ADDRESS SYSTEM "myprog" WITH INPUT STEM somefood. ,
OUTPUT STREAM 'prg.out' ERROR STEM oops.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List
Hi Paul,
//DSSMOVE EXEC PGM=ADRDSSU,REGION=0M
//SYSPRINT DD SYSOUT=*
//ODD DD DISP=SHR,UNIT=SYSALLDA,VOL=SER=ZFSU01
//SYSIN DD *
COPY -
DS( -
INCL( -
ZFS.LOCAL -
) -
) -
ODD(ODD) -
ALLX -
ALLD(*)
> Semicolon is not a command separator in TSO;
That depends on whether you consider CLIST to be TSO.
At the READY prompt, ; ends the line - except when it doesn't.
> there is no facility to put more than one command on a line.
Are you a betting man?
> Semicolon does end the command,
Except
Is that applicable to linear, which is what zFS uses?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Mike Schwab [mike.a.sch...@gmail.com]
Sent: Friday, May 15, 2020
> (which is vaguely analogous to allocating a dd in TSO),
It's more like opening a file. Think of a file descriptor as a short DCB
address.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List
How do you parse "Restriction: This field is only valid for extended format
VSAM and non-VSAM data sets."?
Does that mean extended format VSAM and any format non-VSAM, or extended format
VSAM extended format non-VSAM?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
Could it be permissions? RACF? The userid that youre using in production
doesnt have permissions to load some element in the XML schema?
Joe
On Sat, May 16, 2020 at 3:59 PM Roberto Halais
wrote:
> Listers:
> I am already at the end of searches and reading.
> We have a batch job that connects
Listers:
I am already at the end of searches and reading.
We have a batch job that connects to an external site using XML.
It works well in our test environment but we are getting an error when we
execute in production.
I have googled but haven't had any luck.
Any idea would be welcomed.
Thank
There shouldn't be any harm in using the SPHERE option on a VSAM dataset copy
operation.
SPHERE specifies that, for any VSAM cluster copied, all associated AIX®
clusters and paths are to be copied. Individual names of sphere components do
not need to be specified. Only the base cluster name is
Sounds like a KSDS. Are there any alternate indexes? Is the dataset
multi-volume? Is not, you should be OK specifying just the base cluster name.
Steve Gorham, Baltimore
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
esst...@juno.com
Sent: Saturday, May 16,
I am Not a DASD Administrator -
.
However I used the following JCL to move a PDS -
//STEP1EXEC PGM=ADRDSSU
//SYSPRINT DDSYSOUT=A
//DASD1DDUNIT=3390,VOL=(PRIVATE,SER=USER12),DISP=OLD
//DASD2DD
Best regards,
*Jon Bathmaker,*
Senior z/OS Systems Programmer,
SYS1 Consulting Inc.
519-577-9661
On 5/15/2020 2:10 PM, Kirk Wolf wrote:
Tip: this is one way to trace your login profiles:
//SHELL EXEC PGM=BPXBATCH,PARM='PGM /bin/sh -Lx'
//STDIN DD DUMMY
//STDOUT DD SYSOUT=*
//STDERR
On Fri, 15 May 2020 19:25:52 +, Farley, Peter x23353 wrote:
>... the requirement is for a CICS COBOL program to pass the file size for a
>dynamically configurable file name in a communications area to a generalized
>CICS subroutine (written and maintained by another team) that will send the
17 matches
Mail list logo
