Re: rename datasets

[Elardus Engelbrecht]

Ron Thomas wrote:

>we are looking at renaming all of the datasets like the below.

>Old dataset - >  SLXR5V.SAPDB.*
>New dataset - > SLXR5V.SAPDB.X.*

Are they Non-VSAM? Do you have other means to check that they're still in use 
or not? Do you have means to check that the new names are not already in place?

John McKown REXX will help you there. If they'r VSAM, you need to add extra 
steps to ensure the rest of the cluster are also renamed.

Of course you need a sure way to check everything before you run it.

What we're usually doing - RENAME HLQ.??? to X.HLQ.??? (add unused HLQ before, 
and thus move it out of the way) or something like that.

Groete / Greetings
Elardus Engelbrecht

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

Interesting article in IBM System Magazine

[Edward Gould]

http://ibmsystemsmag.com/mainframe/Business-Strategy/Competitive-Advantage/ITR-performance/?utm_source=SilverpopMailing_medium=email_campaign=050917-a_IMFEXTRA%20(1)%20Live%20Send_content=Article%20Title%201=10976090=MTMzMzgyMTE0MjcxS0=1160693124=MTE2MDY5MzEyNAS2
 


(watch the wrap)

Figure 1 

Many people can explain that the z Systems platform has the power to do things 
that other machines can’t. Others express proof of their belief that such 
assertions aren’t true by quoting benchmark results, or showing the power and 
scalability of aggregated clusters of smaller machines. This has been going on 
for a long time, and it’s largely because the participants fall into the 
Internal Throughput Rate (ITR) trap.
To effectively resolve the issue, we need to understand what is meant by 
compute power. This article will explain compute power by defining underlying 
performance and capacity fundamentals:
ITR
External Throughput Rate (ETR)
Response time


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

Re: COBOL compiler CODEPAGE() when inter-operating with C & UNIX.

[Tony Harminc]

On 10 May 2017 at 08:24, John McKown  wrote:

> Finally, to the question: If I am planning to inter-operate with C and/or
> UNIX, should I use CODEPAGE(1047) instead of the default of 1140 (which is
> CP-37 with Euro). I am thinking this would likely be necessary if I use
> some of the C language subroutines which deal with regular expressions.
> This is due to the "wrong" encoding of "[" "]" and others in CP-37.
>

CP 1140 is essentially 037+Euro. I think you want CP 924, which is 1047+Euro.
(Both the "with Euro" CPs also have, so as to encode the same set of
characters as ISO 8859-15, a small number of additional characters for
French and some other Western European languages.)

Tony H.

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

Re: ICSF Again

[Steely.Mark]

Dan - IBM sent my SR to their Q  group. IBM is already had our options and 
wants dumps of the CKDS and the keys.
Hopefully they will have an answer for me.

Thanks 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Dan Little
Sent: Wednesday, May 10, 2017 5:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ICSF Again

Can you show the job output?    And are you able to get into ICSF panels?

What are your installation options?

Dan


--

On May 10, 2017, 12:51 PM -0400, Steely.Mark , wrote:
> I was trying to rename a key in the CKDS. I was using 
> PGM=CSFKGUP,PARM=('SSM').
>
> I received this error:
>
> The master key verification patterns in the CKDS do not match the 
> verification patterns of the active DES and AES master keys.
>
> We do not have any crypto hardware and no coprocessor's defined.
> We do not have an active TKDS. CSF has no error message and starts 
> successfully.
> This is not causing an operational issue - but from the error message 
> something is not in sync.
> Also I was able to perform this function on our sandbox system - so the JCL 
> is correct.
>
> This is the answer from IBM:
>
> The following information should help to get you started. Your 
> displays show that you have no active cryptographic coprocessors. 
> Unless your target CKDS (specified by "CSFCKDS" value in your KGUP 
> data definition
> statement) is configured as a clear-key CKDS, you will need to load 
> and set the appropriate Master Keys (DES and/or AES) under which your 
> CKDS is encrypted to access and alter its contents. This requires the 
> use of cryptographic hardware. (Which we don't have)
>
> This doesn't help me at all. I still don't have any idea's how to start. I am 
> just a rookie with ICSF.
> How do I display the master key verification patterns ?
> Where is this ? specified by "CSFCKDS" value in your KGUP data 
> definition statement
>
> We are z/OS V2.2.
>
> Any help would be appreciated.
>
> Thanks
>
>
>
>
>
>
> --
> 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

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

Re: ICSF Again

[Dan Little]

Can you show the job output?    And are you able to get into ICSF panels?

What are your installation options?

Dan


--

On May 10, 2017, 12:51 PM -0400, Steely.Mark , wrote:
> I was trying to rename a key in the CKDS. I was using 
> PGM=CSFKGUP,PARM=('SSM').
>
> I received this error:
>
> The master key verification patterns in the CKDS do not match the
> verification patterns of the active DES and AES master keys.
>
> We do not have any crypto hardware and no coprocessor's defined.
> We do not have an active TKDS. CSF has no error message and starts 
> successfully.
> This is not causing an operational issue - but from the error message 
> something is not in sync.
> Also I was able to perform this function on our sandbox system - so the JCL 
> is correct.
>
> This is the answer from IBM:
>
> The following information should help to get you started. Your displays
> show that you have no active cryptographic coprocessors. Unless your
> target CKDS (specified by "CSFCKDS" value in your KGUP data definition
> statement) is configured as a clear-key CKDS, you will need to load and
> set the appropriate Master Keys (DES and/or AES) under which your CKDS
> is encrypted to access and alter its contents. This requires the use of
> cryptographic hardware. (Which we don't have)
>
> This doesn't help me at all. I still don't have any idea's how to start. I am 
> just a rookie with ICSF.
> How do I display the master key verification patterns ?
> Where is this ? specified by "CSFCKDS" value in your KGUP data definition 
> statement
>
> We are z/OS V2.2.
>
> Any help would be appreciated.
>
> Thanks
>
>
>
>
>
>
> --
> 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: rename datasets

[Steve Smith]

IDCAMS is happy to do generic renames such as that.

Until you specified that only certain ones should be.  Never mind.

sas

On Wed, May 10, 2017 at 4:59 PM, John McKown 
wrote:

> On Wed, May 10, 2017 at 3:51 PM, Ron Thomas  wrote:
>
> > we are looking at renaming all of the datasets like the below.
> >
> > Old dataset - >  SLXR5V.SAPDB.*
> > New dataset - > SLXR5V.SAPDB.X.*
> >
>
> ​Ah. Not too bad. Something like the following REXX might work (untested
> since it's close to my go-home time)
>
> /* REXX */
> XX=OUTTRAP('DATA.','*')
> LISTC LVL('SLXR5V.SAPDB​')
> XX=OUTTRAP("OFF")
> DO I=1 TO DATA.0
>   LINE=DATA.I
>   IF 'NONVSAM' <> WORD(LINE,1) THEN ITERATE /* ONLY WORKS FOR NON-VSAM */
>   DSN=WORD(LINE,3) /* GET THE DSN */
>   SUFFIX=SUBSTR(DSN,12) /* STRIP OFF THE FRONT */
>   NEWDSN='SLXR5V.SAPDB.X'||SUFFIX
>   "ALTER '"DSN"' NEWNAME('"NEWDSN"')"
> END
>
> ​My example is only for non-VSAM, but you can use something similar by
> checking the first word for "CLUSTER", "INDEX", or "DATA".​
>
>
> > Thanks
> > Ron T
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
>
>
>
> --
> Advertising is a valuable economic factor because it is the cheapest way of
> selling goods, particularly if the goods are worthless. -- Sinclair Lewis
>
>
> Maranatha! <><
> John McKown
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>



-- 
sas

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

Re: rename datasets

[John McKown]

On Wed, May 10, 2017 at 3:51 PM, Ron Thomas  wrote:

> we are looking at renaming all of the datasets like the below.
>
> Old dataset - >  SLXR5V.SAPDB.*
> New dataset - > SLXR5V.SAPDB.X.*
>

​Ah. Not too bad. Something like the following REXX might work (untested
since it's close to my go-home time)

/* REXX */
XX=OUTTRAP('DATA.','*')
LISTC LVL('SLXR5V.SAPDB​')
XX=OUTTRAP("OFF")
DO I=1 TO DATA.0
  LINE=DATA.I
  IF 'NONVSAM' <> WORD(LINE,1) THEN ITERATE /* ONLY WORKS FOR NON-VSAM */
  DSN=WORD(LINE,3) /* GET THE DSN */
  SUFFIX=SUBSTR(DSN,12) /* STRIP OFF THE FRONT */
  NEWDSN='SLXR5V.SAPDB.X'||SUFFIX
  "ALTER '"DSN"' NEWNAME('"NEWDSN"')"
END

​My example is only for non-VSAM, but you can use something similar by
checking the first word for "CLUSTER", "INDEX", or "DATA".​


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



-- 
Advertising is a valuable economic factor because it is the cheapest way of
selling goods, particularly if the goods are worthless. -- Sinclair Lewis


Maranatha! <><
John McKown

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

Re: rename datasets

[Ron Thomas]

Also, all of the files that need to renamed is there in a file . We want only 
those in the file to be renamed .

Thanks
Ron T

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

Re: AW: Re: How are Program Object sections with Defer attribute loaded?

[Clark Morris]

[Default] On 10 May 2017 11:09:25 -0700, in bit.listserv.ibm-main
p...@gmx.ch (Peter Hunkeler) wrote:

> 
>
>
>>> How does one request that "deferred load" section be loaded now? I probably 
>>> was looking for the wrong thing at the wrong place, since I could not find 
>>> it. 
>>>  
>> I believe they're loaded on demand.  If you need them, they' re there; 
>if they're not there, you didn't need them. 
> 
>
>
>This is a function offered by the MVS Binder and the MVS Loader in some way. 
>It is being used by LE, which is the component loading Cobol, well MVS, load 
>modules. 
>
>
>In previous versions of Cobol, the Working Storage section was part of the 
>load module, and it was easier to locate Working Storage variables in dump. 
>Now, they are disconnected from the code section, thus it all looks different 
>in a dump. This is how I became aware of "deferred load" sections.
>
Since VS COBOL II release 1.4 with the RENT option, WORKING-STORAGE
has not been in the load module.  

Clark Morris
>
>I'm a curious MVS guy, and I'm curious to understand this. I'm looking at this 
>from a pure MVS point of view. 

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

Re: rename datasets

[Ron Thomas]

we are looking at renaming all of the datasets like the below.

Old dataset - >  SLXR5V.SAPDB.*
New dataset - > SLXR5V.SAPDB.X.*

Thanks
Ron T

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

Re: rename datasets

[Paul Gilmartin]

On Wed, 10 May 2017 15:38:57 -0500, Ron Thomas wrote:

>Hi . We have around 700 datasets where we need to rename the names , is there  
>a utility by which we can run the same in batch ? I believe i can use IDCAMS , 
>but is there a better way to it with less effort ?  
> 
If the renaming is regular, use a script to generate the IDCAMS SYSIN.

If the renaming is sporadic but you have a list of old-name new-name
pairs, use a script to convert that to IDCAMS SYSIN.

If you haven't this information in any form, you're SoL.

If there is overlap of the new-names with the old-names, rename each
data set twice, first old-name -> neutral name, then neutral-name -> new name.

Have at least two people review the IDCAMS SYSIN before you submit the job.

-- gil

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

Re: How to find Cobol (and C) Working Storage variables in an SVCDUMP

[Allan Kielstra]

Bernd has already started the reply, but I would like to add a little bit.

(First, I should say that most of this stuff IS documented in the PG and MG, 
but...)

To find a specific W-S variable, you will need a listing.  

If you start with a dump, you will find a stack frame for your COBOL program 
and in its register save area, you will find the CAA Anchor in GPR12.  Think of 
the CAA anchor as a thread specific piece of data.  Fortunately, most non OO 
COBOL programs are single threaded so you don't have to worry about that 
subtlety.

Also, if you start with a dump, you'll find the entry point for the COBOL 
program.  From this, you can find the PPA1  (there is one for every sub routine 
in a compilation unit -- using C terminology):

 00 02PROCPGG1
 00  47F0 F014  02BC  R15,20(,R15)  
#  Skip over constant area
 04  01C3 C5C5  02DC  X'01C3C5C5'   
#  Eyecatcher: CEE
 08   0200  02DC  X'0200'   
#  Stack Size
 0C   0690  02DC  X'0690'   
#  Offset to PPA1 <<--
 10  47F0 F001  02BC  R15,1(,R15)   
#  Wrong Entry Point: cause exception

from the PPA1, you can find the PPA2 (there is one for the entire compilation 
unit -- again C terminology):
PPA1:  Entry Point Constants
  000690  1CCEA506   =F'483304710'  
Flags
  000694  0850   =A(PPA2-PGG1)  
  <<
  000698  07C0   =A(PPA3-PGG1)

from the PPA2, you can find the PPA4 (again only one):
 PPA2:  Entry Point Constants
  000850  04002203   =F'67117571'   
Flags
  000854  F7B0   
=A(CEESTART-PPA2)
  000858  0058   =F'88' 
A(PPA4-PPA2)<<---
  00085C  FFB0   
=A(TIMESTMP-PPA2)
  000860  F7B0   
=A(PrimaryEntryPoint-PPA2)
  000864  0220   =F'35651584'   
Flags

The C_WSA is actually the combined writeable static area for all of the 
programs bound into your module (or DLL).  To find the entire C_WSA for the 
module, you need to get the CEECRENT pointer out of the CEE Anchor.  That 
means, getting 500(GPR12).  Now you need to find the bit of the C_WSA for this 
particular program (compilation unit in C terminology).  You can get that from 
the PPA4:
 PPA4:  Entry Point Constants
  0008A8  0800   =F'134217728'  
Flags 1
  0008AC  00020100   =F'131328' 
Flags 2
  0008B0     =F'0'  
A(NORENTstatic)
  0008B4     =F'0'  
Q(RENTstatic)<<-

Add that QCON to the CEECRENT -- 500(GPR12) --  and you have the start of the 
section of the WSA for your program.

Now you need to know if WSOPT was used or not.  For that you need to go back to 
the PPA2 and find the timestamp:
  000844  FFB0   
=A(TIMESTMP-PPA2)

The time stamp is a fixed length and immediately following it is :
Compiler Options and Program Information Section
  000814 0034=X'0034'   
Size of Compiler Options and Prog Info Section
  000816  (+00)  0474=X'0474'   
UNSIGNED BINARY CODE PAGE CCSID VALUE
  000818  (+02)  07  =X'07' 
ARCHITECTURE LEVEL
  000819  (+03)  00  =X'00' 
OPTIMIZATION LEVEL
  00081A  (+04)  1406=X'1406'   
INFO. BYTES 28-29
  00081C  (+06)  =X''   
INFO. BYTES 30-31
  00081E  (+08)  A0C8754C2000
=X'A0C8754C2000'   INFO. BYTES 1-6
  000824  (+14)  00184001
=X'00184001'   INFO. BYTES 7-12

The bit you're looking for is bit 3 of byte 15.  Compare the output above to 
the same program with NOWSOPT
  00080C  (+14)  00084001
=X'00084001'   INFO. BYTES 7-12

If you are using NOWSOPT (which is the default for V4) your W-S data items are 
all in your piece of the module's WSA.  To find a specific item, you need to 
consult the listing looking 

Re: AW: Re: job output into dataset

[Lizette Koehler]

NOTE:  JES2 has a counter in the JCT.  Even if output is spun, it will not 
reduce that counter by what is spun.  The counter will continue to increase.  
And it can increase until, the number of lines, exceeds what JES2 knows that 
should be produced which can cause a task to abend with a S722 abend.  No way 
around that other than cycling the tasks.

I currently have a task that is prone to S722 abends.  It is an STC and it is 
now being cycled monthly to prevent an unexpected S722 abend.



Spin - to copy/route the information in a SYSOUT DD statement to the OUTPUT 
class specified by the SYSOUT statement.

If your JES2 INITDECK says

OUTPUT(A) OUTDISP=(HOLD,HOLD) 

You have
//DDlabel  DD SYSOUT=A

Then the DDlabel:  $Txx,SPIN,DDNAME=DDlabel

The output will show up in the HELD Class A queue.   So the H Panel in SDSF

If you have coded in the JES2 INITDECK 
OUTPUT(A) OUTDISP=(WRITE,WRITE)

And you have
//DDLabel  DD SYSOUT=A

The output will show up in the OUTPUT CLASS A.  So the O Panel in SDSF

Note:  If you do not CODE FREE=CLOSE,SPIN=UNALLOC You will NOT see the 
output 

The SPIN will not be available until TASK end.

The ST panel in SDSF can see everything available on Spool.

NOTE SYSOUT=* in a started task defaults the the STC definition in JES2.

Spin data set processing

z/OS JES2 Initialization and Tuning Guide
SA32-0991-00

Coding FREE=CLOSE or SPIN=UNALLOC in the JCL of a SYSOUT DD statement or 
specifying the DALCLOSE text unit key on a dynamic allocation (SVC99) parameter 
list for a SYSOUT data set causes JES2 to spin the data set for output 
processing when it is closed. JES2 then has the capability of performing output 
processing on the data set while the job continues execution. JESLOG data sets 
can be spun through $T J/S/T,SPIN.

In most cases, JES2 frees spool tracks allocated to the data set after 
printing, canceling, or transmitting the last copy of the data set.

For applications that dynamically allocate a spin SYSOUT data set (unallocation 
at Close - Key X'001C') but fail to issue FREE=CLOSE or SPIN=UNALLOC, JES2 does 
not free spool tracks allocated to the spin data set until the job is purged. 
In this case, end-of-task processing deallocates the data set and job purge 
processing returns the allocated tracks.



NOTE:  There are some DD Statements that are created at job creation time 

   DDNAME   StepName ProcStep DSID  
   JESMSGLG JES2 2  
   JESJCL   JES2 3  
   JESYSMSG JES2 4  

Note:  Sometimes even though you "see" output, the Spin command may provide the 
message:  $HASP138 SPIN rejected, no spinnable data set

Hope this helps.

Lizette



The DD statements with DSID numbers less than 100 are special.



z/OS z/OS 2.2.0  z/OS JES2 z/OS JES2 Initialization and Tuning Guide 
Controlling JES2 processes  Printers and punches 

   Table 1. JES2 system data setsData Set Name  Purpose of data set
   JESJCLIN Indicates the actual JCL submitted.
   JESMSGLG Indicates any system messages for this job.
   JESJCL   Indicates all job control statements in the input stream, that 
is, all JCL statements and JES2 control statements, plus all procedure 
statements from any in-stream or cataloged procedure a job step calls, plus all 
messages about job control statements.
   JESYSMSG Indicates the job's hardcopy log, which contains the JES2 and 
operator messages about the job's processing: allocation of devices and 
volumes, execution and termination of job steps and the job, and disposition of 
data sets.



You should talk to your friendly z/OS system programmer for assistance specific 
to your shop.

Lizette


-Original Message-
>From: venkat kulkarni 
>Sent: May 10, 2017 11:42 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: AW: Re: job output into dataset
>
>Hello Lizette,
>
>Couple of important points,
>
>1) I am still not clear that, what happens when we run spin command  $T
>job(ims12RC1),spin,ddname=JESMSGLG . Where messages goes from DD JESMSGLG  .
>
>In my case, when i run this command, it clear all record from DD JESMSGLG
>but its not storing in output queue. But my requirement is that it should
>keep those record in output queue after this spin command and from output
>queue, we use some way to suck this output and archive it for later use.
>
>2) I have set my outdisp parameter to (write, write)  for this STC class
>but still my records from this DD JESMSGLG  not coming to output queue.
>Please help to provide some reason on this issue.
>
>3) When i run  $T job(ims12RC1),spin,ddname=JESMSGLG command, it start
>processing this DD but i never get message saying successfully completed. I
>waited for long but it never finish but I see my record becomes zero in
>address space for this DD name.
>
>
>I tried reading all document possible for this and couldnt find any help.
>
>
>

--
For IBM-MAIN 

Re: rename datasets

[John McKown]

On Wed, May 10, 2017 at 3:38 PM, Ron Thomas  wrote:

> Hi . We have around 700 datasets where we need to rename the names , is
> there  a utility by which we can run the same in batch ? I believe i can
> use IDCAMS , but is there a better way to it with less effort ?
>

​That's a bit vague. Do you have some sort of "pattern" or algorithm you're
using to convert the old DSN ​to a new DSN? I don't know of any standard
IBM utility which would do a "wildcard" rename. I often use a language such
as REXX or AWK to generate IDCAMS control cards, then run a batch job with
them. I do the "wild card" either by doing an IDCAMS LISTCAT (such as LISTC
LVL('SYS1.LIH1') and then process that output in my REXX program).


>
> Regards
> Ron T
>
> --
Advertising is a valuable economic factor because it is the cheapest way of
selling goods, particularly if the goods are worthless. -- Sinclair Lewis


Maranatha! <><
John McKown

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

Re: rename datasets

[Allan Staller]

Try dfdss:
Pseudo-command below:

CPY DATASET INCLUDE(x.**) RENUNC (x.**, x.**.new)  replace 
recatalog(*) delete   (pseudo-command)

Might need some extra temp space during the copy and there are some limitations 
on the structure of the from and to names when using wild cards.
Check the Fine Manual for details

HTH,

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Ron Thomas
Sent: Wednesday, May 10, 2017 3:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: rename datasets

Hi . We have around 700 datasets where we need to rename the names , is there  
a utility by which we can run the same in batch ? I believe i can use IDCAMS , 
but is there a better way to it with less effort ?  


Regards
Ron T

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


::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.




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

rename datasets

[Ron Thomas]

Hi . We have around 700 datasets where we need to rename the names , is there  
a utility by which we can run the same in batch ? I believe i can use IDCAMS , 
but is there a better way to it with less effort ?  


Regards
Ron T

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

Re: How to find Cobol (and C) Working Storage variables in an SVCDUMP

[Thomas Dunlap]

Bernd and Peter,

What Bernd shows you is the way I have found it in COBOL V5.1.1. I am 
putting up V6 next month and will revisit it again.  I also did the ASM 
map in V5.1.1 and discovered that Working Storage seems to be based on 
Reg. 8.  I do not have V5.2, but I would imagine it would be the same.


Cheers,
Tom



On 5/10/2017 3:29 PM, Bernd Oppolzer wrote:

Two minor errors below:

"addressed by register 13 (aka save area aka dynamic save area aka 
dynamic save area)"


should read

"addressed by register 13 (aka save area aka dynamic save area aka 
dynamic STORAGE area)"


And I forgot to mention:

CEECSA is always address by reg 12, while inside a LE module.

So you get:

reg 12 + 500 = address of the WSA
take this address
add @(Static) from the compiler or prelinker listing
= address of your static section (which should be in some register ...)
add offset of the desired variable
now you have the address

Kind regards

Bernd




Am 10.05.2017 um 21:25 schrieb Bernd Oppolzer:
I guess that this is the same case as finding C  and PL/1 static 
variables

when the C and PL/1 procedures or functions are compiled using the RENT
compiler switch.

Because:

a) auto variables are always part of the "stack" which is addressed 
by register 13

(aka save area aka dynamic save area aka dynamic save area)

b) in the NORENT case the STATIC variables are part of the STATIC CSECT,
which is located inside the load module ... this is, what classical 
COBOL did,
and which is still present in C and PL/1 in the NORENT case ... 
NORENT is

recommended by IBM for PL/1, today :-)

So, let's go:

the static variables in the RENT case are part of the WSA. To locate 
them in

the dump (SYSUDUMP, CEEDUMP, ...), you have several choices:

a) when you are inside the function where the variable is defined,
CEECSA+500 (X'1F4) should point to the WSA, so you have the base
address of the WSA. From the prelinker listing, you can see where the
static section of your particular function starts (Q(@STATIC)), add 
this to the
base address, and then add the offset of the variable from the 
compiler listing ..

voila the address of the variable

b) to speed up the addressing of the variables at run time, a certain 
register
is loaded just after the function prologue with the value CEECSA+500 
+ Q(@STATIC).
Look for this register (may be R4, R5, R6, R7, ...). Then add the 
offset of the

variable to that register.

Sorry, no easier way. In prior releases, the base register of the 
static area

always was register 3 (in PL/1).

The compiler builders could make the jobs of dump readers easier, if 
they

want, but they normally don't have dump readers in mind.

I'm trying to do it differently with my Stanford Pascal compiler:
http://bernd-oppolzer.de/job9.htm

HTH,
have a nice day

Bernd



Am 10.05.2017 um 21:02 schrieb Peter Hunkeler:

  Reposting under a different subject, since the topic has changed

That's actually a trickier question than you might imagine!
I imagine it is! In my current job, I'm getting involved when 
standard application debugging techniques don't help anymore. I 
usually work with IPCS, so SYSMDUMPs and SVCDUMPs. We moved to Cobol 
V5.2 earlier this year, but I still need to find the content of 
Cobol variables in those dumps. The changes to how Working Storage 
is implemented, and the fact that this is mostly undocumented, makes 
it difficult. This is the real reason I'm trying to understand all 
this.

Your comments are most welcome!
There are a number of cases:  the case where your module consists 
of COBOL, PL/I and assembler only and all other cases.  All other 
cases include cases where the COBOL run time support is implemented 
in a language other than the above.  These cases include OO COBOL, 
XML support and a few others.
In the second case (not pure COBOL), the C_WSA is loaded in 
exactly the same way as it is for a C program. Basically, first the 
program is loaded and then the C run time gets control.  It 
determines that you want to start new instance of this program 
(C_WSA is only used for RENT.) So it calls CEEPPOS which is the 
actual routine that gets a WSA and initializes it.
This all happens before main is run. (Or, in the case of C++, 
before any file scope statics are constructed.)

   Yes, this is well understood.
In the first case, your program starts and the COBOL bootstrap 
routine gets control.  That routine is called at the start of every 
PROGRAM.  In most cases, it checks a few things and returns.  But 
for the first program in the run unit, it does some work including 
ensuring that LE is up.  Part of that work is getting storage for 
the WSA.
All of this happens before the first user statement in the 
PROCEDURE DIVISION is executed.
So, no matter how the C_WSA is loaded (by and LE routine or by the 
COBOL run time) it is present before the first user written 
statement in the program is executed.

Yes, again well understood.
Which means that unless you're getting 

Re: JCL null statement (Was: job output into dataset)

[Paul Gilmartin]

On Tue, 9 May 2017 13:38:02 -0500, Tom Marchant wrote:

>On Tue, 9 May 2017 13:25:43 -0500, Paul Gilmartin wrote:
>
>>On Tue, 9 May 2017 18:59:23 +0100, David W Noon wrote:
>>>   i) the job stream arrives at a null statement;
>>>...
>>I'm skeptical about that point since I often submit jobs with noise
>>such as comments after a null statement and SDSF shows me
>>those lines in JESJCLIN, indicating that the job was not spun until
>>the SYSOUT was closed.
>
>I don't believe it.
>
>The behavior that David describes is very old. Back in the 70's, 
>operators would routinely add a null JCL statement to the end of 
>a tray of JCL to be processed so that the last job would be 
>processed immediately. I just submitted such a job and the 
>contents of JESJCLIN ends with the last statement before the
>null JCL statement.
> 
I found it.  Using the Rexx API to SDSF and issuing the SJA prefix
command I see a spool data set that shows the null statement and
any records following it.  (I had no following JOB statement.)

(It has to go somewhere:
https://en.wikipedia.org/wiki/Black_hole_information_paradox
)
-- gil

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

Re: How to find Cobol (and C) Working Storage variables in an SVCDUMP

[Bernd Oppolzer]

Two minor errors below:

"addressed by register 13 (aka save area aka dynamic save area aka 
dynamic save area)"


should read

"addressed by register 13 (aka save area aka dynamic save area aka 
dynamic STORAGE area)"


And I forgot to mention:

CEECSA is always address by reg 12, while inside a LE module.

So you get:

reg 12 + 500 = address of the WSA
take this address
add @(Static) from the compiler or prelinker listing
= address of your static section (which should be in some register ...)
add offset of the desired variable
now you have the address

Kind regards

Bernd




Am 10.05.2017 um 21:25 schrieb Bernd Oppolzer:
I guess that this is the same case as finding C  and PL/1 static 
variables

when the C and PL/1 procedures or functions are compiled using the RENT
compiler switch.

Because:

a) auto variables are always part of the "stack" which is addressed by 
register 13

(aka save area aka dynamic save area aka dynamic save area)

b) in the NORENT case the STATIC variables are part of the STATIC CSECT,
which is located inside the load module ... this is, what classical 
COBOL did,

and which is still present in C and PL/1 in the NORENT case ... NORENT is
recommended by IBM for PL/1, today :-)

So, let's go:

the static variables in the RENT case are part of the WSA. To locate 
them in

the dump (SYSUDUMP, CEEDUMP, ...), you have several choices:

a) when you are inside the function where the variable is defined,
CEECSA+500 (X'1F4) should point to the WSA, so you have the base
address of the WSA. From the prelinker listing, you can see where the
static section of your particular function starts (Q(@STATIC)), add 
this to the
base address, and then add the offset of the variable from the 
compiler listing ..

voila the address of the variable

b) to speed up the addressing of the variables at run time, a certain 
register
is loaded just after the function prologue with the value CEECSA+500 + 
Q(@STATIC).
Look for this register (may be R4, R5, R6, R7, ...). Then add the 
offset of the

variable to that register.

Sorry, no easier way. In prior releases, the base register of the 
static area

always was register 3 (in PL/1).

The compiler builders could make the jobs of dump readers easier, if they
want, but they normally don't have dump readers in mind.

I'm trying to do it differently with my Stanford Pascal compiler:
http://bernd-oppolzer.de/job9.htm

HTH,
have a nice day

Bernd



Am 10.05.2017 um 21:02 schrieb Peter Hunkeler:

  Reposting under a different subject, since the topic has changed

That's actually a trickier question than you might imagine!
I imagine it is! In my current job, I'm getting involved when 
standard application debugging techniques don't help anymore. I 
usually work with IPCS, so SYSMDUMPs and SVCDUMPs. We moved to Cobol 
V5.2 earlier this year, but I still need to find the content of Cobol 
variables in those dumps. The changes to how Working Storage is 
implemented, and the fact that this is mostly undocumented, makes it 
difficult. This is the real reason I'm trying to understand all this.

Your comments are most welcome!
There are a number of cases:  the case where your module consists of 
COBOL, PL/I and assembler only and all other cases.  All other cases 
include cases where the COBOL run time support is implemented in a 
language other than the above.  These cases include OO COBOL, XML 
support and a few others.
In the second case (not pure COBOL), the C_WSA is loaded in 
exactly the same way as it is for a C program.  Basically, first the 
program is loaded and then the C run time gets control.  It 
determines that you want to start  new instance of this program 
(C_WSA is only used for RENT.)  So it calls CEEPPOS which is the 
actual routine that gets a WSA and initializes it.
This all happens before main is run. (Or, in the case of C++, before 
any file scope statics are constructed.)

   Yes, this is well understood.
In the first case, your program starts and the COBOL bootstrap 
routine gets control.  That routine is called at the start of every 
PROGRAM.  In most cases, it checks a few things and returns.  But 
for the first program in the run unit, it does some work including 
ensuring that LE is up.  Part of that work is getting storage for 
the WSA.
All of this happens before the first user statement in the PROCEDURE 
DIVISION is executed.
So, no matter how the C_WSA is loaded (by and LE routine or by the 
COBOL run time) it is present before the first user written 
statement in the program is executed.

Yes, again well understood.
Which means that unless you're getting some sort of a trap during 
the COBOL start up, you should always see the C_WSA somewhere in 
your storage.
 Yep, somewhere. But somewhere is not specific enough if you need 
to find the value of a variable at the time of the dump.
By the way, WORKING STORAGE is another area of complexity.  In the 
case of NOWSOPT (the default for V5) W-S items are directly in 

Re: How to find Cobol (and C) Working Storage variables in an SVCDUMP

[Bernd Oppolzer]

I guess that this is the same case as finding C  and PL/1 static variables
when the C and PL/1 procedures or functions are compiled using the RENT
compiler switch.

Because:

a) auto variables are always part of the "stack" which is addressed by 
register 13

(aka save area aka dynamic save area aka dynamic save area)

b) in the NORENT case the STATIC variables are part of the STATIC CSECT,
which is located inside the load module ... this is, what classical 
COBOL did,

and which is still present in C and PL/1 in the NORENT case ... NORENT is
recommended by IBM for PL/1, today :-)

So, let's go:

the static variables in the RENT case are part of the WSA. To locate 
them in

the dump (SYSUDUMP, CEEDUMP, ...), you have several choices:

a) when you are inside the function where the variable is defined,
CEECSA+500 (X'1F4) should point to the WSA, so you have the base
address of the WSA. From the prelinker listing, you can see where the
static section of your particular function starts (Q(@STATIC)), add this 
to the
base address, and then add the offset of the variable from the compiler 
listing ..

voila the address of the variable

b) to speed up the addressing of the variables at run time, a certain 
register
is loaded just after the function prologue with the value CEECSA+500 + 
Q(@STATIC).
Look for this register (may be R4, R5, R6, R7, ...). Then add the offset 
of the

variable to that register.

Sorry, no easier way. In prior releases, the base register of the static 
area

always was register 3 (in PL/1).

The compiler builders could make the jobs of dump readers easier, if they
want, but they normally don't have dump readers in mind.

I'm trying to do it differently with my Stanford Pascal compiler:
http://bernd-oppolzer.de/job9.htm

HTH,
have a nice day

Bernd



Am 10.05.2017 um 21:02 schrieb Peter Hunkeler:

  Reposting under a different subject, since the topic has changed
  
   

That's actually a trickier question than you might imagine!
  
  
I imagine it is! In my current job, I'm getting involved when standard application debugging techniques don't help anymore. I usually work with IPCS, so SYSMDUMPs and SVCDUMPs. We moved to Cobol V5.2 earlier this year, but I still need to find the content of Cobol variables in those dumps. The changes to how Working Storage is implemented, and the fact that this is mostly undocumented, makes it difficult. This is the real reason I'm trying to understand all this.
  
  
Your comments are most welcome!
  
  

There are a number of cases:  the case where your module consists of COBOL, 
PL/I and assembler only and all other cases.  All other cases include cases 
where the COBOL run time support is implemented in a language other than the 
above.  These cases include OO COBOL, XML support and a few others.
  
  
In the second case (not pure COBOL), the C_WSA is loaded in exactly the same way as it is for a C program.  Basically, first the program is loaded and then the C run time gets control.  It determines that you want to start  new instance of this program (C_WSA is only used for RENT.)  So it calls CEEPPOS which is the actual routine that gets a WSA and initializes it.
  
  

This all happens before main is run.  (Or, in the case of C++, before any file 
scope statics are constructed.)
   
  
  
Yes, this is well understood.
  
  

In the first case, your program starts and the COBOL bootstrap routine gets 
control.  That routine is called at the start of every PROGRAM.  In most cases, 
it checks a few things and returns.  But for the first program in the run unit, 
it does some work including ensuring that LE is up.  Part of that work is 
getting storage for the WSA.
  
  

All of this happens before the first user statement in the PROCEDURE DIVISION 
is executed.
So, no matter how the C_WSA is loaded (by and LE routine or by the COBOL run 
time) it is present before the first user written statement in the program is 
executed.
  
  
Yes, again well understood.
  
  

Which means that unless you're getting some sort of a trap during the COBOL 
start up, you should always see the C_WSA somewhere in your storage.
   
  
Yep, somewhere. But somewhere is not specific enough if you need to find the value of a variable at the time of the dump.
   

By the way, WORKING STORAGE is another area of complexity.  In the case of 
NOWSOPT (the default for V5) W-S items are directly in the C_WSA.  In the case 
of WSOPT (V6) W-S is separately allocated and the WSA contains a pointer to 
that allocation.  (Again, this is all done before the first user statement is 
executed.)
   
  
  
I really which there was a document describing all the variants in detail and how to find variables in a dump in each case. Lack of that document, I'm trying to find out step by step.
  
  
You would seem to be able to be of great help for me on this quest.
  
  


--
For IBM-MAIN subscribe / signoff / archive access 

Re: AW: Re: job output into dataset

[Gibney, Dave]

What are the attributes of MSGCLASS Z? Once you've spun, that would be the next 
part of control?

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of venkat kulkarni
> Sent: Wednesday, May 10, 2017 11:42 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: AW: Re: job output into dataset
> 
> Hello Lizette,
> 
> Couple of important points,
> 
> 1) I am still not clear that, what happens when we run spin command  $T
> job(ims12RC1),spin,ddname=JESMSGLG . Where messages goes from DD
> JESMSGLG  .
> 
> In my case, when i run this command, it clear all record from DD JESMSGLG
> but its not storing in output queue. But my requirement is that it should keep
> those record in output queue after this spin command and from output
> queue, we use some way to suck this output and archive it for later use.
> 
> 2) I have set my outdisp parameter to (write, write)  for this STC class but 
> still
> my records from this DD JESMSGLG  not coming to output queue.
> Please help to provide some reason on this issue.
> 
> 3) When i run  $T job(ims12RC1),spin,ddname=JESMSGLG command, it start
> processing this DD but i never get message saying successfully completed. I
> waited for long but it never finish but I see my record becomes zero in
> address space for this DD name.
> 
> 
> I tried reading all document possible for this and couldnt find any help.
> 
> 
> 
> On Wed, May 10, 2017 at 8:43 PM, Paul Gilmartin < 000433f07816-
> dmarc-requ...@listserv.ua.edu> wrote:
> 
> > On 2017-05-10, at 01:25, Gibney, Dave wrote:
> >
> > > I don't believe attempting to override the three JES files with
> > > a
> > explicit DD definition will work.
> > > I think, but haven't confirmed that you can define the eligibility
> > > to
> > spin those files in the definition of the STC or JOB Class to JES2. It
> > probably take a JES2 command or COLD start to set these attributes.
> > >
> > Many characteristics of the JES data sets can be controlled
> > jointly
> > (JESDS=ALL) or severally by JCL OUTPUT statements.  It's probably not
> > useful to direct any of them to W=INTRDR.
> >
> > If a serious JCL error is detected, OUTPUT statements may be
> > ineffective whereas MSGCLASS would have operated.
> >
> > -- 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

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

How to find Cobol (and C) Working Storage variables in an SVCDUMP

[Peter Hunkeler]

 Reposting under a different subject, since the topic has changed


>That's actually a trickier question than you might imagine!


I imagine it is! In my current job, I'm getting involved when standard 
application debugging techniques don't help anymore. I usually work with IPCS, 
so SYSMDUMPs and SVCDUMPs. We moved to Cobol V5.2 earlier this year, but I 
still need to find the content of Cobol variables in those dumps. The changes 
to how Working Storage is implemented, and the fact that this is mostly 
undocumented, makes it difficult. This is the real reason I'm trying to 
understand all this.


Your comments are most welcome!


> There are a number of cases:  the case where your module consists of COBOL, 
> PL/I and assembler only and all other cases.  All other cases include cases 
> where the COBOL run time support is implemented in a language other than the 
> above.  These cases include OO COBOL, XML support and a few others.
>
>
> In the second case (not pure COBOL), the C_WSA is loaded in exactly the same 
> way as it is for a C program.  Basically, first the program is loaded and 
> then the C run time gets control.  It determines that you want to start  new 
> instance of this program (C_WSA is only used for RENT.)  So it calls CEEPPOS 
> which is the actual routine that gets a WSA and initializes it.


> This all happens before main is run.  (Or, in the case of C++, before any 
> file scope statics are constructed.)



Yes, this is well understood.


> In the first case, your program starts and the COBOL bootstrap routine gets 
> control.  That routine is called at the start of every PROGRAM.  In most 
> cases, it checks a few things and returns.  But for the first program in the 
> run unit, it does some work including ensuring that LE is up.  Part of that 
> work is getting storage for the WSA.


> All of this happens before the first user statement in the PROCEDURE DIVISION 
> is executed.
> So, no matter how the C_WSA is loaded (by and LE routine or by the COBOL run 
> time) it is present before the first user written statement in the program is 
> executed.


Yes, again well understood.


> Which means that unless you're getting some sort of a trap during the COBOL 
> start up, you should always see the C_WSA somewhere in your storage.


Yep, somewhere. But somewhere is not specific enough if you need to find the 
value of a variable at the time of the dump.

> By the way, WORKING STORAGE is another area of complexity.  In the case of 
> NOWSOPT (the default for V5) W-S items are directly in the C_WSA.  In the 
> case of WSOPT (V6) W-S is separately allocated and the WSA contains a pointer 
> to that allocation.  (Again, this is all done before the first user statement 
> is executed.)



I really which there was a document describing all the variants in detail and 
how to find variables in a dump in each case. Lack of that document, I'm trying 
to find out step by step.


You would seem to be able to be of great help for me on this quest.


--
Peter Hunkeler




--
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

AW: Re: PL1 - U4094 Reason=0000002C

[Peter Hunkeler]

> However while googling, the reason for this abend is related to the language 
> environment (LE). We are using the same LE options (CEEUOPT - User override 
> options) that was used in earlier. Does anyone know if any option on the LE 
> causing this problem?



I would try running the program with LE runtime option TRAP(OFF), and see what 
happens. Don't forget to include a //SYSABEND or better //SYSMDUMP DD statement.


If the program still abends, see what MVS says about the cause not that LE is 
not handling the error. Also, if you understand it, have a look at the System 
Trace in the dump, if one is produced.


--
Peter Hunkeler



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

Re: AW: Re: job output into dataset

[venkat kulkarni]

Hello Lizette,

Couple of important points,

1) I am still not clear that, what happens when we run spin command  $T
job(ims12RC1),spin,ddname=JESMSGLG . Where messages goes from DD JESMSGLG  .

In my case, when i run this command, it clear all record from DD JESMSGLG
but its not storing in output queue. But my requirement is that it should
keep those record in output queue after this spin command and from output
queue, we use some way to suck this output and archive it for later use.

2) I have set my outdisp parameter to (write, write)  for this STC class
but still my records from this DD JESMSGLG  not coming to output queue.
Please help to provide some reason on this issue.

3) When i run  $T job(ims12RC1),spin,ddname=JESMSGLG command, it start
processing this DD but i never get message saying successfully completed. I
waited for long but it never finish but I see my record becomes zero in
address space for this DD name.


I tried reading all document possible for this and couldnt find any help.



On Wed, May 10, 2017 at 8:43 PM, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

> On 2017-05-10, at 01:25, Gibney, Dave wrote:
>
> > I don't believe attempting to override the three JES files with a
> explicit DD definition will work.
> > I think, but haven't confirmed that you can define the eligibility to
> spin those files in the definition of the STC or JOB Class to JES2. It
> probably take a JES2 command or COLD start to set these attributes.
> >
> Many characteristics of the JES data sets can be controlled jointly
> (JESDS=ALL) or severally by JCL OUTPUT statements.  It's probably not
> useful to direct any of them to W=INTRDR.
>
> If a serious JCL error is detected, OUTPUT statements may be ineffective
> whereas MSGCLASS would have operated.
>
> -- 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

AW: Re: How are Program Object sections with Defer attribute loaded?

[Peter Hunkeler]

>That's actually a trickier question than you might imagine!


I imagine it is! In my current job, I'm getting involved when standard 
application debugging techniques don't help anymore. I usually work with IPCS, 
so SYSMDUMPs and SVCDUMPs. We moved to Cobol V5.2 earlier this year, but I 
still need to find the content of Cobol variables in those dumps. The changes 
to how Working Storage is implemented, and the fact that this is mostly 
undocumented, makes it difficult. This is the real reason I'm trying to 
understand all this.


Your comments are most welcome!


> There are a number of cases:  the case where your module consists of COBOL, 
> PL/I and assembler only and all other cases.  All other cases include cases 
> where the COBOL run time support is implemented in a language other than the 
> above.  These cases include OO COBOL, XML support and a few others.
>
>
> In the second case (not pure COBOL), the C_WSA is loaded in exactly the same 
> way as it is for a C program.  Basically, first the program is loaded and 
> then the C run time gets control.  It determines that you want to start  new 
> instance of this program (C_WSA is only used for RENT.)  So it calls CEEPPOS 
> which is the actual routine that gets a WSA and initializes it.


> This all happens before main is run.  (Or, in the case of C++, before any 
> file scope statics are constructed.)



Yes, this is well understood.


> In the first case, your program starts and the COBOL bootstrap routine gets 
> control.  That routine is called at the start of every PROGRAM.  In most 
> cases, it checks a few things and returns.  But for the first program in the 
> run unit, it does some work including ensuring that LE is up.  Part of that 
> work is getting storage for the WSA.


> All of this happens before the first user statement in the PROCEDURE DIVISION 
> is executed.
> So, no matter how the C_WSA is loaded (by and LE routine or by the COBOL run 
> time) it is present before the first user written statement in the program is 
> executed.


Yes, again well understood.


> Which means that unless you're getting some sort of a trap during the COBOL 
> start up, you should always see the C_WSA somewhere in your storage.


Yep, somewhere. But somewhere is not specific enough if you need to find the 
value of a variable at the time of the dump.

> By the way, WORKING STORAGE is another area of complexity.  In the case of 
> NOWSOPT (the default for V5) W-S items are directly in the C_WSA.  In the 
> case of WSOPT (V6) W-S is separately allocated and the WSA contains a pointer 
> to that allocation.  (Again, this is all done before the first user statement 
> is executed.)



I really which there was a document describing all the variants in detail and 
how to find variables in a dump in each case. Lack of that document, I'm trying 
to find out step by step.


You would seem to be able to be of great help for me on this quest.


--
Peter Hunkeler




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

Re: AUTOIPL SADUMP LOADPARM flag value

[Jim Mulder]

  Currently, "2" will be treated the same as "0" or " " (blank).There 
is no reason
why you should have specified "2", and a good reason not to - there is  a
possibility that in some future release, we might assign some meaning to 
"2".

  Standalone dump treats this character as a hexadecimal digit 
representing four option bits.  The first bit is an undocumented option 
intended to be used only under my direction.  The second bit is what
is documented for "4".  The third (corresponding to "2") and fourth bits 
are 
currently unused. 

Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. 
Poughkeepsie NY

> Back in 2010 I had a system coded with SADUMP(,SNSYSC2) and 
MVS(LAST).
> 
> When a 
> 
> V, XCF,sysn,OFFLINE,SADUMP,REIPL
> 
> command was issued, the system did take a Stand Alone Dump, and did IPL.
> 
> That is my recollection.
> 
> Today I have no idea why I coded the "2" in the "SSNSYSC2" 
> loadparm, and was hoping someone could explain why it worked.
> 
> The SADUMP manual says that only "0", "4" and " " (blank) are valid 
values.



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

AW: Re: How are Program Object sections with Defer attribute loaded?

[Peter Hunkeler]

> Trust in the COBOL young Luke..  You do not need to understand the COBOL, It
knows what you need.



LOL ! Thanks for amusing me after a long day.


--
Peter Hunkeler




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

AW: Re: How are Program Object sections with Defer attribute loaded?

[Peter Hunkeler]

>> How does one request that "deferred load" section be loaded now? I probably 
>> was looking for the wrong thing at the wrong place, since I could not find 
>> it.
>>
> I believe they're loaded on demand.  If you need them, they' re there;
if they're not there, you didn't need them.



This is a function offered by the MVS Binder and the MVS Loader in some way. It 
is being used by LE, which is the component loading Cobol, well MVS, load 
modules.


In previous versions of Cobol, the Working Storage section was part of the load 
module, and it was easier to locate Working Storage variables in dump. Now, 
they are disconnected from the code section, thus it all looks different in a 
dump. This is how I became aware of "deferred load" sections.


I'm a curious MVS guy, and I'm curious to understand this. I'm looking at this 
from a pure MVS point of view.




--
Peter Hunkeler






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

Re: How are Program Object sections with Defer attribute loaded?

[Allan Kielstra]

That's actually a trickier question than you might imagine!  There are a number 
of cases:  the case where your module consists of COBOL, PL/I and assembler 
only and all other cases.  All other cases include cases where the COBOL run 
time support is implemented in a language other than the above.  These cases 
include OO COBOL, XML support and a few others.

In the second case (not pure COBOL), the C_WSA is loaded in exactly the same 
way as it is for a C program.  Basically, first the program is loaded and then 
the C run time gets control.  It determines that you want to start  new 
instance of this program (C_WSA is only used for RENT.)  So it calls CEEPPOS 
which is the actual routine that gets a WSA and initializes it.  This all 
happens before main is run.  (Or, in the case of C++, before any file scope 
statics are constructed.)

In the first case, your program starts and the COBOL bootstrap routine gets 
control.  That routine is called at the start of every PROGRAM.  In most cases, 
it checks a few things and returns.  But for the first program in the run unit, 
it does some work including ensuring that LE is up.  Part of that work is 
getting storage for the WSA.   All of this happens before the first user 
statement in the PROCEDURE DIVISION is executed.

So, no matter how the C_WSA is loaded (by and LE routine or by the COBOL run 
time) it is present before the first user written statement in the program is 
executed.  Which means that unless you're getting some sort of a trap during 
the COBOL start up, you should always see the C_WSA somewhere in your storage.

By the way, WORKING STORAGE is another area of complexity.  In the case of 
NOWSOPT (the default for V5) W-S items are directly in the C_WSA.  In the case 
of WSOPT (V6) W-S is separately allocated and the WSA contains a pointer to 
that allocation.  (Again, this is all done before the first user statement is 
executed.)

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

Re: JCL System symbols

[Paul Gilmartin]

On Wed, 10 May 2017 13:43:33 -0400, Peter Relson wrote:

>>The table still shows the, at least on z/OS V 2.1 and 
>>up, invalid symbols  and 
>
>Those symbols are not fully "invalid". They are available to IBM-code 
>symbol substituters that choose to allow them. The DUMPDS command 
>processing is such a substituter (I think the only intended one).  The 
>table should mention that (and similarly for , ). Given that 
>they are deprecated, they could certainly be moved out of the table into a 
>separate section.
> 
I suspect this is a consequence of a simple-minded symbol resolution
facility that can't detect or report a buffer overrun when the length
of a symbol's value exceeds the length of its name.

-- gil

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

Re: AW: Re: job output into dataset

[Paul Gilmartin]

On 2017-05-10, at 01:25, Gibney, Dave wrote:

> I don't believe attempting to override the three JES files with a 
> explicit DD definition will work. 
> I think, but haven't confirmed that you can define the eligibility to spin 
> those files in the definition of the STC or JOB Class to JES2. It probably 
> take a JES2 command or COLD start to set these attributes.
>  
Many characteristics of the JES data sets can be controlled jointly
(JESDS=ALL) or severally by JCL OUTPUT statements.  It's probably not
useful to direct any of them to W=INTRDR.

If a serious JCL error is detected, OUTPUT statements may be ineffective
whereas MSGCLASS would have operated.

-- gil

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

Re: JCL System symbols

[Peter Relson]

>The table still shows the, at least on z/OS V 2.1 and 
>up, invalid symbols  and 

Those symbols are not fully "invalid". They are available to IBM-code 
symbol substituters that choose to allow them. The DUMPDS command 
processing is such a substituter (I think the only intended one).  The 
table should mention that (and similarly for , ). Given that 
they are deprecated, they could certainly be moved out of the table into a 
separate section.

>And all the local date/time related symbols are only 
>mentioned in the explanation of other symbols

I have submitted a request to update to have the deprecated symbols put in 
a separate area, and add the "local time" symbols included as their own 
entries, not only as reference from the "UTC time" symbols.

In the future, I encourage you to take the time to help yourself and 
presumably others by sending an appropriate email to the ID folks to ask 
for / suggest updates. 

Peter Relson
z/OS Core Technology Deign


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

Re: How are Program Object sections with Defer attribute loaded?

[Paul Gilmartin]

On Wed, 10 May 2017 19:02:32 +0200, Peter Hunkeler wrote:

>I understand that Cobol V5 and newer is marking the Working Storage sections 
>(C_WSA) with the "deferred load" attribute. I further understand that 
>"deferred load" sections are not loaded automatically when the load module is 
>brought into storage.
>
>How does one request that "deferred load" section be loaded now? I probably 
>was looking for the wrong thing at the wrong place, since I could not find it.
> 
I believe they're loaded on demand.  If you need them, they' re there;
if they're not there, you didn't need them.

>From looking at a dump, I see the CDE does not seem to represent the "deferred 
>load" section of a program object, only the non-deferred part. How do I find 
>such a section in a dump?

-- gil

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

Re: PL1 - U4094 Reason=0000002C

[Manikandan R]

Lizette, Thanks for your response!

Our mainframe support team is also involved in this and they tried some test 
but couldn't identify the root cause. I will certainly check with them to open 
a SR with IBM. 

However while googling, the reason for this abend is related to the language 
environment (LE). We are using the same LE options (CEEUOPT - User override 
options) that was used in earlier. Does anyone know if any option on the LE 
causing this problem?

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

Re: How are Program Object sections with Defer attribute loaded?

[Lizette Koehler]

Trust in the COBOL young Luke..  You do not need to understand the COBOL, It
knows what you need.


Sorry - not even Friday.

I am not sure it is controllable by the user.  But I will do some further
research

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter Hunkeler
> Sent: Wednesday, May 10, 2017 10:03 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: How are Program Object sections with Defer attribute loaded?
> 
> I understand that Cobol V5 and newer is marking the Working Storage sections
> (C_WSA) with the "deferred load" attribute. I further understand that
> "deferred load" sections are not loaded automatically when the load module is
> brought into storage.
> 
> How does one request that "deferred load" section be loaded now? I probably
> was looking for the wrong thing at the wrong place, since I could not find
> it.
> 
> From looking at a dump, I see the CDE does not seem to represent the
> "deferred load" section of a program object, only the non-deferred part. How
> do I find such a section in a dump?
> 
> 
> 
> 
> --
> Peter Hunkeler
> 

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

Re: DFDSS QUESTION :SHARE PARM WHEN DOING COPY

[willie bunter]

I should have clarified it.  The dsn is copied and in the following step it is 
deleted.  Sorry.

On Wed, 5/10/17, retired mainframer  wrote:

 Subject: Re: DFDSS QUESTION :SHARE PARM WHEN DOING COPY
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Wednesday, May 10, 2017, 8:41 AM
 
 You cannot code SHARE and DELETE
 on the same COPY command.  If the dataset is deleted after
 the copy step, then obviously DFDSS has released its enqueue
 and is no longer a factor in the situation you described.
 
 > -Original Message-
 > From: IBM Mainframe Discussion List
 [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On
 > Behalf Of willie bunter
 > Sent: Wednesday, May 10, 2017 5:26 AM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: Re: DFDSS QUESTION :SHARE PARM
 WHEN DOING COPY
 > 
 >
 Thanks for raising the point that the enqueue is caused by
 the initiator and not DFDSS,  I
 > will
 check into this.
 > To answer your
 question about the CICS file.  Yes, the enqueue is
 released.  The dsn is
 > copied and
 deleted and redefined.
 >
 
 --
 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

How are Program Object sections with Defer attribute loaded?

[Peter Hunkeler]

I understand that Cobol V5 and newer is marking the Working Storage sections 
(C_WSA) with the "deferred load" attribute. I further understand that "deferred 
load" sections are not loaded automatically when the load module is brought 
into storage.

How does one request that "deferred load" section be loaded now? I probably was 
looking for the wrong thing at the wrong place, since I could not find it.

>From looking at a dump, I see the CDE does not seem to represent the "deferred 
>load" section of a program object, only the non-deferred part. How do I find 
>such a section in a dump?




--
Peter Hunkeler

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

ICSF Again

[Steely.Mark]

I was trying to rename a key in the CKDS. I was using  PGM=CSFKGUP,PARM=('SSM').

I received this error:

The master key verification patterns in the CKDS do not match the
verification patterns of the active DES and AES master keys.

We do not have any crypto hardware and no coprocessor's defined.
We do not have an active TKDS.  CSF has no error message and starts 
successfully.
This is not causing an operational issue - but from the error message something 
is not in sync.
Also I was able to perform this function on our sandbox system - so the JCL is 
correct.

This is the answer from IBM:

The following information should help to get you started. Your displays
show that you have no active cryptographic coprocessors.  Unless your
target CKDS (specified by "CSFCKDS" value in your KGUP data definition
statement) is configured as a clear-key CKDS, you will need to load and
set the appropriate Master Keys (DES and/or AES) under which your CKDS
is encrypted to access and alter its contents. This requires the use of
cryptographic hardware. (Which we don't have)

This doesn't help me at all. I  still don't have any idea's how to start. I am 
just a rookie with ICSF.
How do I display the master key verification patterns ?
Where is this ?  specified by "CSFCKDS" value in your KGUP data definition 
statement

We are z/OS V2.2.

Any help would be appreciated.

Thanks






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

Re: [EXTERNAL] Re: SoftAudit ?

[Craig Pace]

When IBM picked up Softaudit, they renamed it to Tivoli License Compliance 
Manager for z/OS.

There are some others out there; however, used it up to V4R2 and it was the 
best on the market by far.

http://www-03.ibm.com/software/products/en/tivolilicensecompliancemanagerforzos



Thanks,


Craig


This communication contains information which is confidential and may also be 
privileged. It is for the exclusive use of the intended recipient(s). If you 
are not the intended recipient(s), please note that any distribution, copying 
or use of this communication or the information in it is strictly prohibited. 
If you have received this communication in error, please notify the sender 
immediately and then destroy any copies of it.



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

Re: [EXTERNAL] Re: SoftAudit ?

[Dyck, Lionel B. (TRA)]

Thanks to everyone that responded - I will be passing this along to my 
management (and get out of the way :-)


--
Lionel B. Dyck 
Mainframe Systems Programmer - TRA
Enterprise Operations (Station 200) (005OP6.3.10)
Information and Technology, IT Operations and Services


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lucas Rosalen
Sent: Wednesday, May 10, 2017 9:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: SoftAudit ?

I don't know what kind of contract you need, but I've worked for customers that 
would only gather data for TADz and send to IBM, so their reports would be 
produced at an IBM mainframe instead of a customer-owned one.
I was also able to use TADz Analyzer hosted on an IBM site (but fed with 
customer data), which I found to be a very good tool to discover who/what used 
which software/version when. Very granular data in a distance of a mouse click.

---
*Lucas Rosalen*
Emails: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2017-05-10 16:43 GMT+02:00 Norbert Friemel :

> On Wed, 10 May 2017 09:20:35 -0500, Dyck, Lionel B. (TRA) wrote:
>
> >Whatever happened to SoftAudit from Isogon?  Did IBM pick it up and
> rename it or did it die with the IBM acquisition?
> >
> >Are there any other products that will detect the running programs 
> >and
> identify them back to a vendor and product?
> >
>
> https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/
> common/ssi/rep_sm/4/897/ENUS5698-AA4/index.html
> http://ubs-hainer.com/solutions/p-tracker
>
> Norbert Friemel
>
> --
> 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

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

Re: PL1 - U4094 Reason=0000002C

[Lizette Koehler]

Have you opened an SR with  IBM?

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Manikandan R
> Sent: Wednesday, May 10, 2017 8:18 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: PL1 - U4094 Reason=002C
> 
> Hello,
> 
> The PL1 programs were developed in older version (with LE/370),  now I am
> trying to compile and run in the environment with PL1EN V4 version. While
> running a PL1 program I am getting abend U4094 Reason=002C (Termination
> requested during termination) in CEEROOTA however the output file is created
> (when used CATLG,CATLG Disp parameter) and it is exactly matching with older
> version output file. So it doesnt look like a application program issue.
> While googleing it says Language environment issue. Is there any suggestion
> on how to resolve this abend?
> 
> Thanks in advance for the help!
> 
> Thanks,
> 
> Mani R
> 
> --
> 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

PL1 - U4094 Reason=0000002C

[Manikandan R]

Hello,

The PL1 programs were developed in older version (with LE/370),  now I am 
trying to compile and run in the environment with PL1EN V4 version. While 
running a PL1 program I am getting abend U4094 Reason=002C (Termination 
requested during termination) in CEEROOTA however the output file is created 
(when used CATLG,CATLG Disp parameter) and it is exactly matching with older 
version output file. So it doesnt look like a application program issue. While 
googleing it says Language environment issue. Is there any suggestion on how to 
resolve this abend?

Thanks in advance for the help!

Thanks,

Mani R

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

Re: SoftAudit ?

[Lucas Rosalen]

I don't know what kind of contract you need, but I've worked for customers
that would only gather data for TADz and send to IBM, so their reports
would be produced at an IBM mainframe instead of a customer-owned one.
I was also able to use TADz Analyzer hosted on an IBM site (but fed with
customer data), which I found to be a very good tool to discover who/what
used which software/version when. Very granular data in a distance of a
mouse click.

---
*Lucas Rosalen*
Emails: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2017-05-10 16:43 GMT+02:00 Norbert Friemel :

> On Wed, 10 May 2017 09:20:35 -0500, Dyck, Lionel B. (TRA) wrote:
>
> >Whatever happened to SoftAudit from Isogon?  Did IBM pick it up and
> rename it or did it die with the IBM acquisition?
> >
> >Are there any other products that will detect the running programs and
> identify them back to a vendor and product?
> >
>
> https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/
> common/ssi/rep_sm/4/897/ENUS5698-AA4/index.html
> http://ubs-hainer.com/solutions/p-tracker
>
> Norbert Friemel
>
> --
> 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: ShopzSeries

[Carmen Vitullo]

As Lizette said, HTTPS is easier and in most cases easier to get approval from 
your network / firewall folks, we authorize via the HTTP proxy with out LAN ID 
and password, that they will allow no problem 



Carmen 
- Original Message -

From: "Lizette Koehler"  
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Wednesday, May 10, 2017 9:37:44 AM 
Subject: Re: ShopzSeries 

Yes, 

Go through the IBM Archives - it was discussed a lot and should help with 
setting it up. 

HTTPS is easier to do than the other 


Lizette 

> -Original Message- 
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Nai, Dean 
> Sent: Wednesday, May 10, 2017 7:08 AM 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: ShopzSeries 
> 
> 
> Howdy, 
> 
> I haven't used ShopZseries for a while and now I'm hearing we need to use 
> secure FTP for it. Is there any documentation on how it needs to be setup? 
> Any certificates needed? 
> 

-- 
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: SoftAudit ?

[Norbert Friemel]

On Wed, 10 May 2017 09:20:35 -0500, Dyck, Lionel B. (TRA) wrote:

>Whatever happened to SoftAudit from Isogon?  Did IBM pick it up and rename it 
>or did it die with the IBM acquisition?
>
>Are there any other products that will detect the running programs and 
>identify them back to a vendor and product?
>

https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_sm/4/897/ENUS5698-AA4/index.html
http://ubs-hainer.com/solutions/p-tracker

Norbert Friemel

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

Re: SoftAudit ?

[Stewart Gray]

Hi Lionel

IBM picked up SoftAudit and it was renamed to TLCM (Tivoli License Compliance 
Manager).

TLCM was later replaced TADz (Tivoli Asset Discovery for system z). TADz stores 
it data in a database (such as DB2) and includes a number of improvements .. 
example Version detection, and reports are generally a lot more detailed 
including FMID info etc.

TADz can be pricey though.

> On 10 May 2017, at 16.20, Dyck, Lionel B. (TRA)  wrote:
> 
> Whatever happened to SoftAudit from Isogon?  Did IBM pick it up and rename it 
> or did it die with the IBM acquisition?
> 
> Are there any other products that will detect the running programs and 
> identify them back to a vendor and product?
> 
> Thanks in advance
> 
> --
> Lionel B. Dyck
> Mainframe Systems Programmer - TRA
> Enterprise Operations (Station 200) (005OP6.3.10)
> Information and Technology, IT Operations and Services
> 
> 
> --
> 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: ShopzSeries

[Lizette Koehler]

Yes,

Go through the IBM Archives - it was discussed a lot and should help with 
setting it up.

HTTPS is easier to do than the other


Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Nai, Dean
> Sent: Wednesday, May 10, 2017 7:08 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: ShopzSeries
> 
> 
> Howdy,
> 
>I haven't used ShopZseries for a while and now I'm hearing we need to use
> secure FTP for it. Is there any documentation on how it needs to be setup?
> Any certificates needed?
> 

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

Re: ShopzSeries

[Nai, Dean]

Thanks Lucas.











On 5/10/17, 10:34 AM, "IBM Mainframe Discussion List on behalf of Lucas 
Rosalen"  wrote:

>Hello Dean,
>
>I think what you need is this doc =>
>https://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10863
>
>Thanks,
>---
>*Lucas Rosalen*
>Emails: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
>*
>LinkedIn: http://br.linkedin.com/in/lrosalen
>Phone: +48 (71) 792 809 198
>
>
>2017-05-10 16:07 GMT+02:00 Nai, Dean :
>
>>
>> Howdy,
>>
>>I haven't used ShopZseries for a while and now I'm hearing we need to
>> use secure FTP for it. Is there any documentation on how it needs to be
>> setup? Any certificates needed?
>>
>> --
>> 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

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

Re: ShopzSeries

[Lucas Rosalen]

Hello Dean,

I think what you need is this doc =>
https://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10863

Thanks,
---
*Lucas Rosalen*
Emails: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 (71) 792 809 198


2017-05-10 16:07 GMT+02:00 Nai, Dean :

>
> Howdy,
>
>I haven't used ShopZseries for a while and now I'm hearing we need to
> use secure FTP for it. Is there any documentation on how it needs to be
> setup? Any certificates needed?
>
> --
> 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: SoftAudit ?

[Mark Jacobs - Listserv]

I think it was rebranded as Tivoli Asset Manager.


Dyck, Lionel B. (TRA) 
May 10, 2017 at 10:20 AM
Whatever happened to SoftAudit from Isogon? Did IBM pick it up and 
rename it or did it die with the IBM acquisition?


Are there any other products that will detect the running programs and 
identify them back to a vendor and product?


Thanks in advance

--
Lionel B. Dyck
Mainframe Systems Programmer - TRA
Enterprise Operations (Station 200) (005OP6.3.10)
Information and Technology, IT Operations and Services


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


Please be alert for any emails that may ask you for login information 
or directs you to login via a link. If you believe this message is a 
phish or aren't sure whether this message is trustworthy, please send 
the original message as an attachment to 'phish...@timeinc.com'.




--

Mark Jacobs
Time Customer Service
Global Technology Services

The standard you walk past is the standard you accept.
Lt. Gen. David Morrison


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

SoftAudit ?

[Dyck, Lionel B. (TRA)]

Whatever happened to SoftAudit from Isogon?  Did IBM pick it up and rename it 
or did it die with the IBM acquisition?

Are there any other products that will detect the running programs and identify 
them back to a vendor and product?

Thanks in advance

--
Lionel B. Dyck
Mainframe Systems Programmer - TRA
Enterprise Operations (Station 200) (005OP6.3.10)
Information and Technology, IT Operations and Services


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

ShopzSeries

[Nai, Dean]

Howdy,

   I haven't used ShopZseries for a while and now I'm hearing we need to use 
secure FTP for it. Is there any documentation on how it needs to be setup? Any 
certificates needed?

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

Re: AW: Re: job output into dataset

[Tom Marchant]

On Tue, 9 May 2017 10:42:48 +0300, venkat kulkarni wrote:

>Yes. It's not.so I should code jesmsglg dd stmt as
>//JESMSGLG dd sysout=a,free=close,spin=unalloc

No, you should not.
Doing so would define a DD statement for your step. But the JESYSMSG 
for the job has already been allocated before your step starts.

Look up JESLOG=SPIN.

-- 
Tom Marchant

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

Re: DFDSS QUESTION :SHARE PARM WHEN DOING COPY

[retired mainframer]

You cannot code SHARE and DELETE on the same COPY command.  If the dataset is 
deleted after the copy step, then obviously DFDSS has released its enqueue and 
is no longer a factor in the situation you described.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of willie bunter
> Sent: Wednesday, May 10, 2017 5:26 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: DFDSS QUESTION :SHARE PARM WHEN DOING COPY
> 
> Thanks for raising the point that the enqueue is caused by the initiator and 
> not DFDSS,  I
> will check into this.
> To answer your question about the CICS file.  Yes, the enqueue is released.  
> The dsn is
> copied and deleted and redefined.
>

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

Re: DFDSS QUESTION :SHARE PARM WHEN DOING COPY

[willie bunter]

Thanks for raising the point that the enqueue is caused by the initiator and 
not DFDSS,  I will check into this.
To answer your question about the CICS file.  Yes, the enqueue is released.  
The dsn is copied and deleted and redefined.

Thanks again.

On Tue, 5/9/17, retired mainframer  wrote:

 Subject: Re: DFDSS QUESTION :SHARE PARM WHEN DOING COPY
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Tuesday, May 9, 2017, 1:27 PM
 
 Since the JCL has a reference to
 the DSN after the DFDSS step, the enqueue that is causing
 your conflict is held by the initiator, not by DFDSS.  The
 section I quoted has additional text that describes how
 DFDSS uses the initiator's enqueue.  You need to look
 at that to determine how it affects your job.
 
 When you close the file in
 CICS, is the enqueue released?  If so, the SHARE option is
 irrelevant since no one else is accessing the dataset. 
 Unless OAM is VSAM under the covers (like PDSE and ZFS), the
 quoted text states that is does apply.
 
 >
 -Original Message-
 > From: IBM
 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On
 > Behalf Of willie bunter
 > Sent: Tuesday, May 09, 2017 9:29 AM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: Re: DFDSS QUESTION :SHARE PARM
 WHEN DOING COPY
 > 
 >
 The job does reference the dsn after it is enabled on
 CICS.
 > 
 > Since the
 dsn is OAM the SHARE parm does appy.  Right?
 > 
 >
 
 > On Tue, 5/9/17, retired mainframer 
 wrote:
 > 
 >  Subject:
 Re: DFDSS QUESTION :SHARE PARM WHEN DOING COPY
 >  To: IBM-MAIN@LISTSERV.UA.EDU
 >  Received: Tuesday, May 9, 2017, 10:19
 AM
 > 
 >  >
 -Original
 >  Message-
 >  > From: IBM Mainframe
 >  Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 >  On
 >  > Behalf Of
 willie bunter
 >  > Sent: Tuesday, May
 09, 2017 6:01 AM
 >  > To: IBM-MAIN@LISTSERV.UA.EDU
 >  > Subject: DFDSS QUESTION :SHARE PARM
 WHEN
 >  DOING COPY
 >  >
 >  > Good
 >  Day To All,
 > 
 >
 >  > Could
 >  someone clarify the explanation and my
 understanding about
 >  the SHARE parm
 when
 >  > using COPY.
 >  Following is the explanation in the
 doc:
 >  >
 >  >
 SHARE specifies that
 >  DFSMSdss is to
 share the data sets to be copied for read
 >  > access with other programs.
 >  > SHARE and FULL are mutually
 exclusive; you
 >  cannot specify these
 keywords
 >  >
 > 
 together.
 >  > Do not specify DELETE
 if you
 >  specify SHARE. You must have
 exclusive control
 >  > over data sets
 that are to be deleted;
 >  SHARE does
 not require such exclusive
 >  >
 >  control.
 >  >
 Note: Unlike the RESTORE
 >  command, the
 COPY command honors the SHARE
 >  >
 keyword for VSAM data sets. However, the
 >  SHARE keyword is only honored for
 >  > VSAM
 >  data
 sets that were defined with share options other than
 >  (1,3) or (1,4).
 > 
 > Specifying the SHARE
 >  keyword
 does not cause DFSMSdss to honor the share
 >  > options that are defined for VSAM
 data
 >  sets. For VSAM data sets that
 are defined
 >  > with share options
 other than (1,3) or
 >  (1,4), specifying
 the SHARE keyword allows
 >  > other
 programs to obtain read access. It
 > 
 does not, however, allow write access to
 >  > the data sets while they are being
 copied.
 >  For VSAM data sets that are
 defined
 >  >
 > 
 with share options (1,3) or (1,4), neither read access
 nor
 >  write access by other
 >  > programs is
 > 
 allowed while the data set is being copied.
 >  >
 >  > If my
 understanding
 >  is correct the SHARE
 parm applis to VSAM dsns which are
 > 
 defined
 >  > with share options (2,3)
 .
 >  However the dsn in question is that
 it is an OAM file.
 >  Would the
 >  > SHARE apply to OAM dsns as
 >  well?
 > 
 >  The paragraph that
 >  talks about VSAM datasets I emphasizing
 the difference
 >  between COPY and
 RESTORE.  Since your dataset is not VSAM,
 >  the paragraph does not apply.  Note the
 following quote
 >  from the Data Set
 Serialization section of the
 > 
 manual"
 > 
 > 
 " The
 >  SHARE option has unique
 properties when applied to the
 > 
 following commands:
 >      * For the
 RESTORE
 >  command, SHARE applies to
 non-VSAM data sets only.
 >      * For
 the DUMP and COPY commands, SHARE
 > 
 applies to non-VSAM data sets and VSAM data sets that are
 >  defined with share options other than
 (1,3) and
 >  (1,4)."
 > 
 >  > Before
 >  the COPY is executed the file is closed
 on CICS.  However
 >  after the COPY
 step
 >  > has executed of the
 >  dsn (no warnings or errors received) 
 the job abends at the
 >  following
 >  > step which tries to enable
 >  the file on CICS because the dsn is not
 released from the
 >  job until
 >  > it completes.  The job has 6
 >  steps.
 >  > My
 question is
 >  shouldn''t the
 dsn be released after the COPY step
 > 
 is has completed or does
 >  > dsn
 is
 >  released at the end ot the job? 
 Could someone please clear
 >  

COBOL compiler CODEPAGE() when inter-operating with C & UNIX.

[John McKown]

Another discussion "turned me on to" the use of NATIONAL characters in
COBOL. Basically, from my reading, this is UTF-16BE with a CCSID of 1200.
That got me to looking at CCSIDs in COBOL in general. Which lead me to the
CODEPAGE() compile parameter.

Finally, to the question: If I am planning to inter-operate with C and/or
UNIX, should I use CODEPAGE(1047) instead of the default of 1140 (which is
CP-37 with Euro). I am thinking this would likely be necessary if I use
some of the C language subroutines which deal with regular expressions.
This is due to the "wrong" encoding of "[" "]" and others in CP-37.

-- 
Advertising is a valuable economic factor because it is the cheapest way of
selling goods, particularly if the goods are worthless. -- Sinclair Lewis


Maranatha! <><
John McKown

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

AUTOIPL SADUMP LOADPARM flag value

[Bruce Hewson]

hello,

Back in 2010 I had a system coded with SADUMP(,SNSYSC2) and MVS(LAST).

When a 

V, XCF,sysn,OFFLINE,SADUMP,REIPL

command was issued, the system did take a Stand Alone Dump, and did IPL.

That is my recollection.

Today I have no idea why I coded the "2" in the "SSNSYSC2"  loadparm, and was 
hoping someone could explain why it worked.

The SADUMP manual says that only "0", "4" and " " (blank) are valid values.

Hope someone can help.

Thank you
Bruce Hewson

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

Re: AW: Re: job output into dataset

[venkat kulkarni]

I think spin only works when we have dd name defined in our proc with
free=close and spin=unalloc .. else even after running spin command from
console , process wil never finish and we will not get print in output
class.

Please correct me, if I am wrong.

On 10-May-2017 11:03 AM, "Gibney, Dave"  wrote:

> Is Z a held MSGCLASS?
> I really haven't used SPIN, so I can't help much. But, I really doubt you
> can successfully define the DD you desire. I don't think JES2 allows it.
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of venkat kulkarni
> > Sent: Wednesday, May 10, 2017 12:46 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: AW: Re: job output into dataset
> >
> > Below is my stc job class output
> >
> > RESPONSE=TST4
> >
> >  $HASP837 JOBCLASS(STC)
> >
> >  $HASP837 JOBCLASS(STC)   AUTH=(ALL),BLP=YES,COMMAND=EXECUTE,
> >
> >  $HASP837 CONDPURG=YES,DSENQSHR=ALLOW,
> >
> >  $HASP837 IEFUJP=YES,IEFUSO=YES,JESLOG=(SPIN,
> >
> >  $HASP837 10K),LOG=YES,MSGLEVEL=(1,1),
> >
> >  $HASP837 MSGCLASS=Z,OUTDISP=(WRITE,WRITE),
> >
> >  $HASP837 OUTPUT=YES,PERFORM=000,PROCLIB=00,
> >
> >  $HASP837 QAFF=(ANY),REGION=0004M,SWA=BELOW,
> >
> >  $HASP837 TIME=(000120,00),TYPE26=YES,
> >
> >  $HASP837 TYPE6=YES
> >
> > I looked at every possible document and I think the issue is, when I
> issue spin
> > command , the process starts and spin records from dd but it never write
> on
> > output queue.
> >
> > So, what is stopping system to complete this spin process and should
> return
> > me $HASP138 of successful completion.
> >
> > I am still suspecting that do I need to have dd name entry in my proc
> which I
> > am using in my spin command with free=close and spin=unallocated
> >
> > Please help me to clear this doubt
> >
> > On 10-May-2017 10:26 AM, "Gibney, Dave"  wrote:
> >
> > > I don't believe attempting to override the three JES files with a
> > > explicit DD definition will work.
> > > I think, but haven't confirmed that you can define the eligibility to
> > > spin those files in the definition of the STC or JOB Class to JES2. It
> > > probably take a JES2 command or COLD start to set these attributes.
> > >
> > > Looking at the appropriate manual(s) will help you as much or more as
> > > these questions here.
> > >
> > > > -Original Message-
> > > > From: IBM Mainframe Discussion List
> > > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of venkat kulkarni
> > > > Sent: Tuesday, May 09, 2017 11:25 PM
> > > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > > Subject: Re: AW: Re: job output into dataset
> > > >
> > > >  I feel, whatever DD name I want spin, I should code in proclib for
> > > example
> > > > : If I want to always spin JESMSGLG DD from address space then I
> > > > should code below line in proclib and then
> > > >
> > > >  only my spin command will be completed.
> > > >
> > > >
> > > >
> > > > //JESMSGLG DD SYSOUT=A,FREE=CLOSE,SPIN=UNALLOC
> > > >
> > > >
> > > >
> > > > Please correct me, if I am wrong.
> > > >
> > > >
> > > >
> > > > 2) Currently, I don’t get  $HASP138 message on my console after
> > > > starting SPIN command. I just get below command
> > > >
> > > >
> > > >
> > > > $T JQ(IMS12IMS),SPIN,DDNAME=JESMSGLG
> > > >
> > > > $HASP890 JOB(IMS12IMS) 103
> > > >
> > > > $HASP890 JOB(IMS12IMS)  STATUS=(EXECUTING/TST4),CLASS=STC,
> > > >
> > > > $HASP890PRIORITY=15,SYSAFF=(TST4),HOLD=(NONE)
> > > >
> > > >
> > > >
> > > > So, I have doubt that my spin command is not getting completed or
> > > > some other reason.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > 3) After running this spin command, I don’t see any output in my
> > > > output queue. Even though i set my STC job class
> > > >
> > > >
> > > >
> > > > /$T JOBCLASS(STC),OUTDISP=(KEEP,KEEP)
> > > >
> > > >
> > > >
> > > > still, no output on output queue.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > 4) I see duplicate DD name like below after running SPIN command. Ex
> > > > JESMSGLG and JESYSMSG  are showing me 2 times in this same address
> > > > space.
> > > >
> > > >
> > > >
> > > > SDSF JOB DATA SET DISPLAY - JOB IMS12IMS (STC02551)
> > > >
> > > > COMMAND INPUT ===>
> > > >
> > > > PREFIX=IMS12IMS  DEST=(ALL)  OWNER=*  SYSNAME=
> > > >
> > > > NP   DDNAME   StepName ProcStep DSID OwnerC Dest
> > > >
> > > >  JESMSGLG JES2 2 STCCICQ  Z
> > > >
> > > >  JESJCL   JES2 3 STCCICQ  Z
> > > >
> > > >  JESYSMSG JES2 4 STCCICQ  Z
> > > >
> > > >  JESYSMSG JES2   104 STCCICQ  Z
> > > >
> > > >  JESMSGLG JES2   108 STCCICQ  Z
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Can you please help me to solve these queries.
> > > >
> > 

Re: AW: Re: job output into dataset

[Gibney, Dave]

Is Z a held MSGCLASS? 
I really haven't used SPIN, so I can't help much. But, I really doubt you can 
successfully define the DD you desire. I don't think JES2 allows it.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of venkat kulkarni
> Sent: Wednesday, May 10, 2017 12:46 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: AW: Re: job output into dataset
> 
> Below is my stc job class output
> 
> RESPONSE=TST4
> 
>  $HASP837 JOBCLASS(STC)
> 
>  $HASP837 JOBCLASS(STC)   AUTH=(ALL),BLP=YES,COMMAND=EXECUTE,
> 
>  $HASP837 CONDPURG=YES,DSENQSHR=ALLOW,
> 
>  $HASP837 IEFUJP=YES,IEFUSO=YES,JESLOG=(SPIN,
> 
>  $HASP837 10K),LOG=YES,MSGLEVEL=(1,1),
> 
>  $HASP837 MSGCLASS=Z,OUTDISP=(WRITE,WRITE),
> 
>  $HASP837 OUTPUT=YES,PERFORM=000,PROCLIB=00,
> 
>  $HASP837 QAFF=(ANY),REGION=0004M,SWA=BELOW,
> 
>  $HASP837 TIME=(000120,00),TYPE26=YES,
> 
>  $HASP837 TYPE6=YES
> 
> I looked at every possible document and I think the issue is, when I issue 
> spin
> command , the process starts and spin records from dd but it never write on
> output queue.
> 
> So, what is stopping system to complete this spin process and should return
> me $HASP138 of successful completion.
> 
> I am still suspecting that do I need to have dd name entry in my proc which I
> am using in my spin command with free=close and spin=unallocated
> 
> Please help me to clear this doubt
> 
> On 10-May-2017 10:26 AM, "Gibney, Dave"  wrote:
> 
> > I don't believe attempting to override the three JES files with a
> > explicit DD definition will work.
> > I think, but haven't confirmed that you can define the eligibility to
> > spin those files in the definition of the STC or JOB Class to JES2. It
> > probably take a JES2 command or COLD start to set these attributes.
> >
> > Looking at the appropriate manual(s) will help you as much or more as
> > these questions here.
> >
> > > -Original Message-
> > > From: IBM Mainframe Discussion List
> > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of venkat kulkarni
> > > Sent: Tuesday, May 09, 2017 11:25 PM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > Subject: Re: AW: Re: job output into dataset
> > >
> > >  I feel, whatever DD name I want spin, I should code in proclib for
> > example
> > > : If I want to always spin JESMSGLG DD from address space then I
> > > should code below line in proclib and then
> > >
> > >  only my spin command will be completed.
> > >
> > >
> > >
> > > //JESMSGLG DD SYSOUT=A,FREE=CLOSE,SPIN=UNALLOC
> > >
> > >
> > >
> > > Please correct me, if I am wrong.
> > >
> > >
> > >
> > > 2) Currently, I don’t get  $HASP138 message on my console after
> > > starting SPIN command. I just get below command
> > >
> > >
> > >
> > > $T JQ(IMS12IMS),SPIN,DDNAME=JESMSGLG
> > >
> > > $HASP890 JOB(IMS12IMS) 103
> > >
> > > $HASP890 JOB(IMS12IMS)  STATUS=(EXECUTING/TST4),CLASS=STC,
> > >
> > > $HASP890PRIORITY=15,SYSAFF=(TST4),HOLD=(NONE)
> > >
> > >
> > >
> > > So, I have doubt that my spin command is not getting completed or
> > > some other reason.
> > >
> > >
> > >
> > >
> > >
> > > 3) After running this spin command, I don’t see any output in my
> > > output queue. Even though i set my STC job class
> > >
> > >
> > >
> > > /$T JOBCLASS(STC),OUTDISP=(KEEP,KEEP)
> > >
> > >
> > >
> > > still, no output on output queue.
> > >
> > >
> > >
> > >
> > >
> > > 4) I see duplicate DD name like below after running SPIN command. Ex
> > > JESMSGLG and JESYSMSG  are showing me 2 times in this same address
> > > space.
> > >
> > >
> > >
> > > SDSF JOB DATA SET DISPLAY - JOB IMS12IMS (STC02551)
> > >
> > > COMMAND INPUT ===>
> > >
> > > PREFIX=IMS12IMS  DEST=(ALL)  OWNER=*  SYSNAME=
> > >
> > > NP   DDNAME   StepName ProcStep DSID OwnerC Dest
> > >
> > >  JESMSGLG JES2 2 STCCICQ  Z
> > >
> > >  JESJCL   JES2 3 STCCICQ  Z
> > >
> > >  JESYSMSG JES2 4 STCCICQ  Z
> > >
> > >  JESYSMSG JES2   104 STCCICQ  Z
> > >
> > >  JESMSGLG JES2   108 STCCICQ  Z
> > >
> > >
> > >
> > >
> > >
> > > Can you please help me to solve these queries.
> > >
> > >
> > >
> > > On 09-May-2017 8:16 PM, "Lizette Koehler" 
> > > wrote:
> > >
> > > > Venkat -
> > > >
> > > >
> > > > You can SPIN SYSOUT (I do not think you can SPIN INTRDR )
> > > >
> > > > Sometimes, the SYSOUT is not PURGED from the Job unless you have
> > > > SPIN=CLOSE,FREE=UNALLOC.  Otherwise the purge of the output will
> > > > occur when the task is shut down.
> > > >
> > > > JES2 keeps a counter of output written. When it gets to a certain
> > > > amount you will see S722 abends
> > > >
> > > > When you SPIN output it will go to the output class specified.
> > > 

Re: AW: Re: job output into dataset

[venkat kulkarni]

Below is my stc job class output

RESPONSE=TST4

 $HASP837 JOBCLASS(STC)

 $HASP837 JOBCLASS(STC)   AUTH=(ALL),BLP=YES,COMMAND=EXECUTE,

 $HASP837 CONDPURG=YES,DSENQSHR=ALLOW,

 $HASP837 IEFUJP=YES,IEFUSO=YES,JESLOG=(SPIN,

 $HASP837 10K),LOG=YES,MSGLEVEL=(1,1),

 $HASP837 MSGCLASS=Z,OUTDISP=(WRITE,WRITE),

 $HASP837 OUTPUT=YES,PERFORM=000,PROCLIB=00,

 $HASP837 QAFF=(ANY),REGION=0004M,SWA=BELOW,

 $HASP837 TIME=(000120,00),TYPE26=YES,

 $HASP837 TYPE6=YES

I looked at every possible document and I think the issue is, when I issue
spin command , the process starts and spin records from dd but it never
write on output queue.

So, what is stopping system to complete this spin process and should return
me $HASP138 of successful completion.

I am still suspecting that do I need to have dd name entry in my proc which
I am using in my spin command with free=close and spin=unallocated

Please help me to clear this doubt

On 10-May-2017 10:26 AM, "Gibney, Dave"  wrote:

> I don't believe attempting to override the three JES files with a
> explicit DD definition will work.
> I think, but haven't confirmed that you can define the eligibility to spin
> those files in the definition of the STC or JOB Class to JES2. It probably
> take a JES2 command or COLD start to set these attributes.
>
> Looking at the appropriate manual(s) will help you as much or more as
> these questions here.
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of venkat kulkarni
> > Sent: Tuesday, May 09, 2017 11:25 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: AW: Re: job output into dataset
> >
> >  I feel, whatever DD name I want spin, I should code in proclib for
> example
> > : If I want to always spin JESMSGLG DD from address space then I should
> > code below line in proclib and then
> >
> >  only my spin command will be completed.
> >
> >
> >
> > //JESMSGLG DD SYSOUT=A,FREE=CLOSE,SPIN=UNALLOC
> >
> >
> >
> > Please correct me, if I am wrong.
> >
> >
> >
> > 2) Currently, I don’t get  $HASP138 message on my console after starting
> > SPIN command. I just get below command
> >
> >
> >
> > $T JQ(IMS12IMS),SPIN,DDNAME=JESMSGLG
> >
> > $HASP890 JOB(IMS12IMS) 103
> >
> > $HASP890 JOB(IMS12IMS)  STATUS=(EXECUTING/TST4),CLASS=STC,
> >
> > $HASP890PRIORITY=15,SYSAFF=(TST4),HOLD=(NONE)
> >
> >
> >
> > So, I have doubt that my spin command is not getting completed or some
> > other reason.
> >
> >
> >
> >
> >
> > 3) After running this spin command, I don’t see any output in my output
> > queue. Even though i set my STC job class
> >
> >
> >
> > /$T JOBCLASS(STC),OUTDISP=(KEEP,KEEP)
> >
> >
> >
> > still, no output on output queue.
> >
> >
> >
> >
> >
> > 4) I see duplicate DD name like below after running SPIN command. Ex
> > JESMSGLG and JESYSMSG  are showing me 2 times in this same address
> > space.
> >
> >
> >
> > SDSF JOB DATA SET DISPLAY - JOB IMS12IMS (STC02551)
> >
> > COMMAND INPUT ===>
> >
> > PREFIX=IMS12IMS  DEST=(ALL)  OWNER=*  SYSNAME=
> >
> > NP   DDNAME   StepName ProcStep DSID OwnerC Dest
> >
> >  JESMSGLG JES2 2 STCCICQ  Z
> >
> >  JESJCL   JES2 3 STCCICQ  Z
> >
> >  JESYSMSG JES2 4 STCCICQ  Z
> >
> >  JESYSMSG JES2   104 STCCICQ  Z
> >
> >  JESMSGLG JES2   108 STCCICQ  Z
> >
> >
> >
> >
> >
> > Can you please help me to solve these queries.
> >
> >
> >
> > On 09-May-2017 8:16 PM, "Lizette Koehler" 
> > wrote:
> >
> > > Venkat -
> > >
> > >
> > > You can SPIN SYSOUT (I do not think you can SPIN INTRDR )
> > >
> > > Sometimes, the SYSOUT is not PURGED from the Job unless you have
> > > SPIN=CLOSE,FREE=UNALLOC.  Otherwise the purge of the output will occur
> > > when the task is shut down.
> > >
> > > JES2 keeps a counter of output written. When it gets to a certain
> > > amount you will see S722 abends
> > >
> > > When you SPIN output it will go to the output class specified.
> > >
> > > For example, SYSOUT=B -  When you spin it will go to the class B.  Now
> > > if B is setup in JES2 as a HELD class or OUTPUT class is dependent on
> > > your shop's JES2 parm
> > >
> > > You can see the output that you SPIN in the SDSF Panels.  Either the
>   O
> > >   STH   panels
> > >
> > > Once you spin the output you still need another process to write the
> > > data to a data set.
> > >
> > > Processes suggested so far
> > >  Write an SDSF ISFEXEC REXX to read the Data from JES2 to dataset
> > > _ Example is JES2DISK
> > >  Purchase a product to do this ($AVERS, VIEW DIRECT, XPTR, and so
> > > forth)
> > >  Setup and External writer to read the data from Spool and write
> > > to a dataset
> > >  

Re: AW: Re: job output into dataset

[Gibney, Dave]

I don't believe attempting to override the three JES files with a explicit 
DD definition will work. 
I think, but haven't confirmed that you can define the eligibility to spin 
those files in the definition of the STC or JOB Class to JES2. It probably take 
a JES2 command or COLD start to set these attributes.

Looking at the appropriate manual(s) will help you as much or more as these 
questions here.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of venkat kulkarni
> Sent: Tuesday, May 09, 2017 11:25 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: AW: Re: job output into dataset
> 
>  I feel, whatever DD name I want spin, I should code in proclib for example
> : If I want to always spin JESMSGLG DD from address space then I should
> code below line in proclib and then
> 
>  only my spin command will be completed.
> 
> 
> 
> //JESMSGLG DD SYSOUT=A,FREE=CLOSE,SPIN=UNALLOC
> 
> 
> 
> Please correct me, if I am wrong.
> 
> 
> 
> 2) Currently, I don’t get  $HASP138 message on my console after starting
> SPIN command. I just get below command
> 
> 
> 
> $T JQ(IMS12IMS),SPIN,DDNAME=JESMSGLG
> 
> $HASP890 JOB(IMS12IMS) 103
> 
> $HASP890 JOB(IMS12IMS)  STATUS=(EXECUTING/TST4),CLASS=STC,
> 
> $HASP890PRIORITY=15,SYSAFF=(TST4),HOLD=(NONE)
> 
> 
> 
> So, I have doubt that my spin command is not getting completed or some
> other reason.
> 
> 
> 
> 
> 
> 3) After running this spin command, I don’t see any output in my output
> queue. Even though i set my STC job class
> 
> 
> 
> /$T JOBCLASS(STC),OUTDISP=(KEEP,KEEP)
> 
> 
> 
> still, no output on output queue.
> 
> 
> 
> 
> 
> 4) I see duplicate DD name like below after running SPIN command. Ex
> JESMSGLG and JESYSMSG  are showing me 2 times in this same address
> space.
> 
> 
> 
> SDSF JOB DATA SET DISPLAY - JOB IMS12IMS (STC02551)
> 
> COMMAND INPUT ===>
> 
> PREFIX=IMS12IMS  DEST=(ALL)  OWNER=*  SYSNAME=
> 
> NP   DDNAME   StepName ProcStep DSID OwnerC Dest
> 
>  JESMSGLG JES2 2 STCCICQ  Z
> 
>  JESJCL   JES2 3 STCCICQ  Z
> 
>  JESYSMSG JES2 4 STCCICQ  Z
> 
>  JESYSMSG JES2   104 STCCICQ  Z
> 
>  JESMSGLG JES2   108 STCCICQ  Z
> 
> 
> 
> 
> 
> Can you please help me to solve these queries.
> 
> 
> 
> On 09-May-2017 8:16 PM, "Lizette Koehler" 
> wrote:
> 
> > Venkat -
> >
> >
> > You can SPIN SYSOUT (I do not think you can SPIN INTRDR )
> >
> > Sometimes, the SYSOUT is not PURGED from the Job unless you have
> > SPIN=CLOSE,FREE=UNALLOC.  Otherwise the purge of the output will occur
> > when the task is shut down.
> >
> > JES2 keeps a counter of output written. When it gets to a certain
> > amount you will see S722 abends
> >
> > When you SPIN output it will go to the output class specified.
> >
> > For example, SYSOUT=B -  When you spin it will go to the class B.  Now
> > if B is setup in JES2 as a HELD class or OUTPUT class is dependent on
> > your shop's JES2 parm
> >
> > You can see the output that you SPIN in the SDSF Panels.  Either theO
> >   STH   panels
> >
> > Once you spin the output you still need another process to write the
> > data to a data set.
> >
> > Processes suggested so far
> >  Write an SDSF ISFEXEC REXX to read the Data from JES2 to dataset
> > _ Example is JES2DISK
> >  Purchase a product to do this ($AVERS, VIEW DIRECT, XPTR, and so
> > forth)
> >  Setup and External writer to read the data from Spool and write
> > to a dataset
> >  Setup a JES2 Offloader to write the data to a dataset.
> >  Look for tools on cbttape.org
> >
> >
> >
> > Note:  There are special DD statements that are generated by JES2 you
> > cannot control with a JCL Statement to spin it.
> >
> > You could review the Manuals  JES2 INIT and TUNING GUIDE, and JES2
> > INIT and TUNING Reference.  They have good detail on how JES2 does
> > output management.
> >
> > SA32-0991-00z/OS JES2 Initialization and Tuning Guide
> > SA32-0992-00z/OS JES2 Initialization and Tuning Reference
> >
> > Next, find the REXX called JES2DISK.  I use this all the time to read
> > data from JES2 and write it to a dataset.  It works very well.
> >
> >
> > It is still not clear what problem you are trying to solve.
> >
> >
> > If you could summarize what it is you need to do, it might be helpful
> > to level set the issue at this time.  There have been a lot of
> > comments and suggestions which do not seem to meet your needs.
> >
> > For example, my task needs to collect the data from STC x which runs
> > 24x7.  I need the information written to the DD statement Y.  This
> > needs to go into a GDG or SEQ files for later review.  This output is
> > a (REPORT, JCL, LOGGING, etc)
> >
> >
> >
> > SPIN can happen at the TASK LEVEL -  S stcname,SPIN=('spin parms')
> >   Or the DD level  //DD  DD 

Re: AW: Re: job output into dataset

[venkat kulkarni]

 I feel, whatever DD name I want spin, I should code in proclib for example
: If I want to always spin JESMSGLG DD from address space then I should
code below line in proclib and then

 only my spin command will be completed.



//JESMSGLG DD SYSOUT=A,FREE=CLOSE,SPIN=UNALLOC



Please correct me, if I am wrong.



2) Currently, I don’t get  $HASP138 message on my console after starting
SPIN command. I just get below command



$T JQ(IMS12IMS),SPIN,DDNAME=JESMSGLG

$HASP890 JOB(IMS12IMS) 103

$HASP890 JOB(IMS12IMS)  STATUS=(EXECUTING/TST4),CLASS=STC,

$HASP890PRIORITY=15,SYSAFF=(TST4),HOLD=(NONE)



So, I have doubt that my spin command is not getting completed or some
other reason.





3) After running this spin command, I don’t see any output in my output
queue. Even though i set my STC job class



/$T JOBCLASS(STC),OUTDISP=(KEEP,KEEP)



still, no output on output queue.





4) I see duplicate DD name like below after running SPIN command. Ex
JESMSGLG and JESYSMSG  are showing me 2 times in this same address space.



SDSF JOB DATA SET DISPLAY - JOB IMS12IMS (STC02551)

COMMAND INPUT ===>

PREFIX=IMS12IMS  DEST=(ALL)  OWNER=*  SYSNAME=

NP   DDNAME   StepName ProcStep DSID OwnerC Dest

 JESMSGLG JES2 2 STCCICQ  Z

 JESJCL   JES2 3 STCCICQ  Z

 JESYSMSG JES2 4 STCCICQ  Z

 JESYSMSG JES2   104 STCCICQ  Z

 JESMSGLG JES2   108 STCCICQ  Z





Can you please help me to solve these queries.



On 09-May-2017 8:16 PM, "Lizette Koehler"  wrote:

> Venkat -
>
>
> You can SPIN SYSOUT (I do not think you can SPIN INTRDR )
>
> Sometimes, the SYSOUT is not PURGED from the Job unless you have
> SPIN=CLOSE,FREE=UNALLOC.  Otherwise the purge of the output will occur when
> the task is shut down.
>
> JES2 keeps a counter of output written. When it gets to a certain amount
> you will see S722 abends
>
> When you SPIN output it will go to the output class specified.
>
> For example, SYSOUT=B -  When you spin it will go to the class B.  Now if
> B is setup in JES2 as a HELD class or OUTPUT class is dependent on your
> shop's JES2 parm
>
> You can see the output that you SPIN in the SDSF Panels.  Either theO
>   STH   panels
>
> Once you spin the output you still need another process to write the data
> to a data set.
>
> Processes suggested so far
>  Write an SDSF ISFEXEC REXX to read the Data from JES2 to dataset _
> Example is JES2DISK
>  Purchase a product to do this ($AVERS, VIEW DIRECT, XPTR, and so
> forth)
>  Setup and External writer to read the data from Spool and write to a
> dataset
>  Setup a JES2 Offloader to write the data to a dataset.
>  Look for tools on cbttape.org
>
>
>
> Note:  There are special DD statements that are generated by JES2 you
> cannot control with a JCL Statement to spin it.
>
> You could review the Manuals  JES2 INIT and TUNING GUIDE, and JES2 INIT
> and TUNING Reference.  They have good detail on how JES2 does output
> management.
>
> SA32-0991-00z/OS JES2 Initialization and Tuning Guide
> SA32-0992-00z/OS JES2 Initialization and Tuning Reference
>
> Next, find the REXX called JES2DISK.  I use this all the time to read data
> from JES2 and write it to a dataset.  It works very well.
>
>
> It is still not clear what problem you are trying to solve.
>
>
> If you could summarize what it is you need to do, it might be helpful to
> level set the issue at this time.  There have been a lot of comments and
> suggestions which do not seem to meet your needs.
>
> For example, my task needs to collect the data from STC x which runs
> 24x7.  I need the information written to the DD statement Y.  This needs to
> go into a GDG or SEQ files for later review.  This output is a (REPORT,
> JCL, LOGGING, etc)
>
>
>
> SPIN can happen at the TASK LEVEL -  S stcname,SPIN=('spin parms')
>   Or the DD level  //DD  DD SYSOUT=x,SPIN=
>   OR by issuing a JES2 command  $Tzz,SPINzzz is either Task
> Number, TaskName
>
> Depending on the requirements you are provided, it will depend on which
> function you will need to use.
>
>
> The more specific the question, the better the answers.  Generic questions
> or comments can lead to confusion for everyone.
>
> This list can provide lots of suggestions and guidance.  It will be your
> job to work with the suggestions and see what works in your shop.  Each
> shop is different and what works for one does not always work for another.
>
>
>
> Lizette
>
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of venkat kulkarni
> > Sent: Tuesday, May 09, 2017 12:43 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: AW: Re: job output into dataset
> >
> > Yes. It's not.so I should code jesmsglg dd stmt as //JESMSGLG dd
> > sysout=a,free=close,spin=unalloc
> >
> >