Re: SDSF question

[Staller, Allan]

Active on a JES output writer. e.g. I have many TCP/IP attached printers
accessed through a 3rd party product.
This product uses the SAPI interface to "print" the job to the 3rd party
product (which actually drives the printers).

During the transfer from JES to the 3rd party product, the job will be
highlighted.

HTH, 


OK, so on DA that makes sense, but we have no real printers, so for
files on
the O or H queues, how can they be "active"?


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF question

[Phil Smith III]

I asked:
> When I'm looking at a queue in SDSF, what does it mean when a job
> output is highlighted? It seems almost random, but I'm sure it isn't!

Roger Bolan replied:

I see this on output queues when the job is selected for an active printer.
Is that what you mean?

And "Gibney, Dave" added:

Yep, it's active. On the DA panel, it is a running task not in a wait.

OK, so on DA that makes sense, but we have no real printers, so for files on
the O or H queues, how can they be "active"?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF question

[Gibney, Dave]

Yep, it's active. On the DA panel, it is a running task not in a wait.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> Behalf Of Roger Bolan
> Sent: Saturday, June 25, 2011 1:13 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: SDSF question
> 
> I see this on output queues when the job is selected for an active
> printer.
> Is that what you mean?
> On Jun 25, 2011 11:41 AM, "Phil Smith III"  wrote:
> > When I'm looking at a queue in SDSF, what does it mean when a job
> output
> is
> > highlighted? It seems almost random, but I'm sure it isn't!
> >
> >
> >
> >
> >
> >
> > -
> -
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN
> INFO
> > Search the archives at http://bama.ua.edu/archives/ibm-main.html
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF question

[Roger Bolan]

I see this on output queues when the job is selected for an active printer.
Is that what you mean?
On Jun 25, 2011 11:41 AM, "Phil Smith III"  wrote:
> When I'm looking at a queue in SDSF, what does it mean when a job output
is
> highlighted? It seems almost random, but I'm sure it isn't!
>
>
>
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

SDSF question

[Phil Smith III]

When I'm looking at a queue in SDSF, what does it mean when a job output is
highlighted? It seems almost random, but I'm sure it isn't!

 

 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF question

[Mark Pace]

Okay, I figured it out.  I had to RACF define and allow update access to
ISFATTR.JOB.PRTDEST


On Tue, Sep 15, 2009 at 3:23 PM, Mary Anne Matyaz wrote:

> Mark, they are fine on my 1.10 system, but I just bring over my ISFPRMxx
> member from release to release. Why don't you try starting SDSF with your
> old
> ISFPRMxx?
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>



-- 
Mark Pace
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF question

[Mary Anne Matyaz]

Mark, they are fine on my 1.10 system, but I just bring over my ISFPRMxx 
member from release to release. Why don't you try starting SDSF with your old 
ISFPRMxx? 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF question

[Mark Pace]

I'm in the same group, IFSOPER, on both systems.  There is some difference
between the groups on each system.  But I can't figure what the difference
is.  On the 1.9 system I do not run SDSF as a server, and there is not a
ISFPRMxx member.  On the 1.10 system I am running it as a server and I am
using a ISFPRMxx member.  So I don't have anything to compare the 1.10
system to the 1.9 system.

On Tue, Sep 15, 2009 at 11:47 AM, Elardus Engelbrecht <
elardus.engelbre...@sita.co.za> wrote:

> Mark Pace wrote:
>
> >On my 1.9 system in SDSF the fields SAFF & PRTDEST  are unprotected and I
> can make changes.
>
> >I just installed a 1.10 system and these fields are protected.
>
> Your ISFPRMxx could be replaced during installation...
>
> >I've been through the ISFPRMxx file and can not figure out what to change
> to make these fields unprotected.  The SAFF, I'm not really concerned
> about,
> but I need to be able to change the PRTDEST so I can route output to
> different systems.
>
> Type in SDSF the command WHO and see in what GRPNAME is your id. Check
> then your ISFPRMxx and look what group you're in.
>
> You may need some changes in RACF to put you in the correct GRPNAME.
>
> HTH
>
> Groete / Greetings
> Elardus Engelbrecht
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>



-- 
Mark Pace
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF question

[Elardus Engelbrecht]

Mark Pace wrote:

>On my 1.9 system in SDSF the fields SAFF & PRTDEST  are unprotected and I
can make changes.

>I just installed a 1.10 system and these fields are protected.  

Your ISFPRMxx could be replaced during installation...

>I've been through the ISFPRMxx file and can not figure out what to change 
to make these fields unprotected.  The SAFF, I'm not really concerned about, 
but I need to be able to change the PRTDEST so I can route output to 
different systems.

Type in SDSF the command WHO and see in what GRPNAME is your id. Check 
then your ISFPRMxx and look what group you're in.

You may need some changes in RACF to put you in the correct GRPNAME.

HTH

Groete / Greetings
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

SDSF question

[Mark Pace]

On my 1.9 system in SDSF the fields SAFF & PRTDEST  are unprotected and I
can make changes.

I just installed a 1.10 system and these fields are protected.  I've been
through the ISFPRMxx file and can not figure out what to change to make
these fields unprotected.  The SAFF, I'm not really concerned about, but I
need to be able to change the PRTDEST so I can route output to different
systems.

-- 
Mark Pace
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Howard Rifkind]

Thanks all,

I'll reorder the parms so SYSPROGX is first...


--- On Sat, 12/27/08, Ed Finnell  wrote:

> From: Ed Finnell 
> Subject: Re: SDSF Question
> To: IBM-MAIN@bama.ua.edu
> Date: Saturday, December 27, 2008, 12:39 PM
> In a message dated 12/27/2008 11:32:19 A.M. Central Standard
> Time,  
> mark.zel...@zurichna.com writes:
> 
> the other entry), and remove TSOAUTH from that group since
> you are  using IUID to classify the userids.  Then it will
> only include the  
> users in your NTBL entry.
> 
> 
> >>
> To test use WHO SDSF command to show Groupid  among other
> thingys
> 
> 
> 
> 
> **One site keeps you connected to all your
> email: AOL Mail, 
> Gmail, and Yahoo Mail. Try it now. 
> (http://www.aol.com/?optin=new-dp&icid=aolcom40vanity&ncid=emlcntaolcom0025)
> 
> --
> For IBM-MAIN subscribe / signoff / archive access
> instructions,
> send email to lists...@bama.ua.edu with the message: GET
> IBM-MAIN INFO
> Search the archives at
> http://bama.ua.edu/archives/ibm-main.html


  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Ed Finnell]

 
In a message dated 12/27/2008 11:32:19 A.M. Central Standard Time,  
mark.zel...@zurichna.com writes:

the other entry), and remove TSOAUTH from that group since
you are  using IUID to classify the userids.  Then it will only include the  
users in your NTBL entry.


>>
To test use WHO SDSF command to show Groupid  among other thingys




**One site keeps you connected to all your email: AOL Mail, 
Gmail, and Yahoo Mail. Try it now. 
(http://www.aol.com/?optin=new-dp&icid=aolcom40vanity&ncid=emlcntaolcom0025)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Mark Zelden]

On Fri, 26 Dec 2008 17:16:04 -0500, Howard Rifkind 
wrote:

>Please bare with me a moment and let me redefine what I'm after:
 
I have two groups, both of which start with:
 
GROUP NAME(ISFSPROG),  
TSOAUTH(JCL,OPER,ACCT),
and the second:
 
GROUP NAME(SYSPRGSX),  
TSOAUTH(JCL,OPER,ACCT),
I want the people who have the TSOAUTH... of the second group to have their
SDSF/LOG command start them at column #51
 
ILOGCOL(51),
 
How can I do this.  Right now  as things stand all are falling into the
first group.
 
Thanks


Howard,

Both IUID and TSOAUTH are used to assign userids to a group.  Don't use
both.  Since the matching is from the top down, everyone that has "uads" 
(RACF/TOP Secret/ACF2) attributes of JCL, OPER, and ACCT will fall into
the first group with those classifications.   

So the solution would be to put the SYSPRGSX group first (before
the other entry), and remove TSOAUTH from that group since
you are using IUID to classify the userids.  Then it will only include the 
users in your NTBL entry.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark.zel...@zurichna.com
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Imbriale, Donald]

SDSF scans ISFPARMS from the beginning and assigns users to the first
group for which they are qualified. This means that the order of the
group definitions is important: Arrange them from most selective to
least selective.

Don Imbriale

-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 5:16 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SDSF Question

Please bare with me a moment and let me redefine what I'm after:
 
I have two groups, both of which start with:
 
GROUP NAME(ISFSPROG),  
TSOAUTH(JCL,OPER,ACCT),
and the second:
 
GROUP NAME(SYSPRGSX),  
TSOAUTH(JCL,OPER,ACCT),
I want the people who have the TSOAUTH... of the second group to have
their SDSF/LOG command start them at column #51
 
ILOGCOL(51),
 
How can I do this.  Right now  as things stand all are falling into the
first group.
 

Generally, this communication is for informational purposes only
and it is not intended as an offer or solicitation for the purchase
or sale of any financial instrument or as an official confirmation
of any transaction. In the event you are receiving the offering
materials attached below related to your interest in hedge funds or
private equity, this communication may be intended as an offer or
solicitation for the purchase or sale of such fund(s).  All market
prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice.
Any comments or statements made herein do not necessarily reflect
those of JPMorgan Chase & Co., its subsidiaries and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Howard Rifkind]

Please bare with me a moment and let me redefine what I'm after:
 
I have two groups, both of which start with:
 
GROUP NAME(ISFSPROG),  
TSOAUTH(JCL,OPER,ACCT),
and the second:
 
GROUP NAME(SYSPRGSX),  
TSOAUTH(JCL,OPER,ACCT),
I want the people who have the TSOAUTH... of the second group to have their 
SDSF/LOG command start them at column #51
 
ILOGCOL(51),
 
How can I do this.  Right now  as things stand all are falling into the first 
group.
 
Thanks

>>> "Jousma, David"  12/26/2008 3:48 PM >>>
When the user logs on, have them issue "who" on the command line.  It
will give you a wealth of info, so that you know they are being
correctly selected and assigned the group you intend.

I also read this in the SDSF book about ILOGCOL:

"This parameter is ignored if the screen on which the SYSLOG or OPERLOG
is displayed can display the entire width of the SYSLOG/OPERLOG. Also,
if the value for position-number is so high that less than a full screen
of data is displayed on the SYSLOG or OPERLOG panel, SDSF adjusts the
starting position number to display a full screen of data. For example,
if the width of the screen on which the SYSLOG is displayed is 80
characters, SDSF adjusts the value of position-number to ensure that 80
characters of data are displayed"

_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com 
1830 East Paris, Grand Rapids, MI  49546 MD RSCB1G
p 616.653.8429
f 616.653.8497


-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:35 PM
To: IBM-MAIN@bama.ua.edu 
Subject: Re: SDSF Question

Thanks David,

The problem is that when user E18823 logs into SDSF with the LOG command
SDSF isn't setting the log column location to column 51.

>>> "Jousma, David"  12/26/2008 3:24 PM >>>
You don't say what the actual problem is, but remember, when using
ISFPARM's like this, the match is top down I believe.  Also, It would
probably help to add this to the paragraph:

IUID(SYSPRGSX), /* NAME TABLE USED FOR SELECTION
*/

_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com 
1830 East Paris, Grand Rapids, MI  49546 MD RSCB1G
p 616.653.8429
f 616.653.8497

-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:10 PM
To: IBM-MAIN@bama.ua.edu 
Subject: SDSF Question

Hello all,

Below is an entry I placed is the ISFPARM's file in order to create a
new group for anyone who is listed under the "NTBL NAME(SYSPRGSX).
There is only one entry in NTBLENT.  This was done in order for various
people to do the SDSF LOG command and have the log come up at column 51.

I executed the following without any errors:

F SDSF,REFRESH,M(HR)   
ISF304I Modify REFRESH command accepted.   
ISF726I SDSF parameter processing started. 
ISF739I SDSF parameters being read from member ISFPRMHR of data set
SYS2.PARMLIB.  
ISF728I SDSF parameters have been activated.   

However this isn't working.  What am I missing?  Any help would be
appreciated.  Thanks.

GROUP IUID(SYSPRGSX),   /* Group name  */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT  */
ACTION(ALL),/* All route codes displayed   */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON),   /* Include APPC sysout */
AUPDT(2),   /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions   */
 SYSID,ABEND,ACTION,INPUT,   
 FINDLIM,ST,INIT,PR,TRACE,   
 ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),   
CMDAUTH(ALL),   /* Commands allowed for all jobs   */
CMDLEV(7),  /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation  */
CURSOR(ON), /* Leave cursor on last row processed  */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB),  /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'),   /* Default datesep format  */
DFIELD2(DAFLD2),/* Sample alternate field list for DA  */
DISPLAY(OFF),   /* Do not display current values   */
DSPAUTH(ALL),   /* Browse allowed for all jobs */
GPLEN(2),   /

Re: SDSF Question

[Jousma, David]

When the user logs on, have them issue "who" on the command line.  It
will give you a wealth of info, so that you know they are being
correctly selected and assigned the group you intend.

I also read this in the SDSF book about ILOGCOL:

"This parameter is ignored if the screen on which the SYSLOG or OPERLOG
is displayed can display the entire width of the SYSLOG/OPERLOG. Also,
if the value for position-number is so high that less than a full screen
of data is displayed on the SYSLOG or OPERLOG panel, SDSF adjusts the
starting position number to display a full screen of data. For example,
if the width of the screen on which the SYSLOG is displayed is 80
characters, SDSF adjusts the value of position-number to ensure that 80
characters of data are displayed"

_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB1G
p 616.653.8429
f 616.653.8497


-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:35 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SDSF Question

Thanks David,
 
The problem is that when user E18823 logs into SDSF with the LOG command
SDSF isn't setting the log column location to column 51.

>>> "Jousma, David"  12/26/2008 3:24 PM >>>
You don't say what the actual problem is, but remember, when using
ISFPARM's like this, the match is top down I believe.  Also, It would
probably help to add this to the paragraph:

IUID(SYSPRGSX), /* NAME TABLE USED FOR SELECTION
*/

_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com 
1830 East Paris, Grand Rapids, MI  49546 MD RSCB1G
p 616.653.8429
f 616.653.8497

-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:10 PM
To: IBM-MAIN@bama.ua.edu 
Subject: SDSF Question

Hello all,

Below is an entry I placed is the ISFPARM's file in order to create a
new group for anyone who is listed under the "NTBL NAME(SYSPRGSX).
There is only one entry in NTBLENT.  This was done in order for various
people to do the SDSF LOG command and have the log come up at column 51.

I executed the following without any errors:

F SDSF,REFRESH,M(HR)   
ISF304I Modify REFRESH command accepted.   
ISF726I SDSF parameter processing started. 
ISF739I SDSF parameters being read from member ISFPRMHR of data set
SYS2.PARMLIB.  
ISF728I SDSF parameters have been activated.   

However this isn't working.  What am I missing?  Any help would be
appreciated.  Thanks.

GROUP IUID(SYSPRGSX),   /* Group name  */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT  */
ACTION(ALL),/* All route codes displayed   */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON),   /* Include APPC sysout */
AUPDT(2),   /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions   */
 SYSID,ABEND,ACTION,INPUT,   
 FINDLIM,ST,INIT,PR,TRACE,   
 ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),   
CMDAUTH(ALL),   /* Commands allowed for all jobs   */
CMDLEV(7),  /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation  */
CURSOR(ON), /* Leave cursor on last row processed  */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB),  /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'),   /* Default datesep format  */
DFIELD2(DAFLD2),/* Sample alternate field list for DA  */
DISPLAY(OFF),   /* Do not display current values   */
DSPAUTH(ALL),   /* Browse allowed for all jobs */
GPLEN(2),   /* Group prefix length */
ILOGCOL(51),/* Initial display column in log   */
ISYS(LOCAL),/* Initial system default for DA   */
LANG(ENGLISH),  /* Default language*/
LOGOPT(OPERACT),/* Default log option  */
OWNER(NONE),/* Default owner   */
UPCTAB(TRTAB2), /* Upper case translate table name */
VALTAB(TRTAB),  /* Valid charac

Re: SDSF Question

[Howard Rifkind]

Thanks David,
 
The problem is that when user E18823 logs into SDSF with the LOG command SDSF 
isn't setting the log column location to column 51.

>>> "Jousma, David"  12/26/2008 3:24 PM >>>
You don't say what the actual problem is, but remember, when using
ISFPARM's like this, the match is top down I believe.  Also, It would
probably help to add this to the paragraph:

IUID(SYSPRGSX), /* NAME TABLE USED FOR SELECTION
*/

_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com 
1830 East Paris, Grand Rapids, MI  49546 MD RSCB1G
p 616.653.8429
f 616.653.8497

-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:10 PM
To: IBM-MAIN@bama.ua.edu 
Subject: SDSF Question

Hello all,

Below is an entry I placed is the ISFPARM's file in order to create a
new group for anyone who is listed under the "NTBL NAME(SYSPRGSX).
There is only one entry in NTBLENT.  This was done in order for various
people to do the SDSF LOG command and have the log come up at column 51.

I executed the following without any errors:

F SDSF,REFRESH,M(HR)   
ISF304I Modify REFRESH command accepted.   
ISF726I SDSF parameter processing started. 
ISF739I SDSF parameters being read from member ISFPRMHR of data set
SYS2.PARMLIB.  
ISF728I SDSF parameters have been activated.   

However this isn't working.  What am I missing?  Any help would be
appreciated.  Thanks.

GROUP IUID(SYSPRGSX),   /* Group name  */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT  */
ACTION(ALL),/* All route codes displayed   */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON),   /* Include APPC sysout */
AUPDT(2),   /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions   */
 SYSID,ABEND,ACTION,INPUT,   
 FINDLIM,ST,INIT,PR,TRACE,   
 ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),   
CMDAUTH(ALL),   /* Commands allowed for all jobs   */
CMDLEV(7),  /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation  */
CURSOR(ON), /* Leave cursor on last row processed  */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB),  /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'),   /* Default datesep format  */
DFIELD2(DAFLD2),/* Sample alternate field list for DA  */
DISPLAY(OFF),   /* Do not display current values   */
DSPAUTH(ALL),   /* Browse allowed for all jobs */
GPLEN(2),   /* Group prefix length */
ILOGCOL(51),/* Initial display column in log   */
ISYS(LOCAL),/* Initial system default for DA   */
LANG(ENGLISH),  /* Default language*/
LOGOPT(OPERACT),/* Default log option  */
OWNER(NONE),/* Default owner   */
UPCTAB(TRTAB2), /* Upper case translate table name */
VALTAB(TRTAB),  /* Valid character translate table */
VIO(SYSALLDA)   /* Unit name for page mode output  */
 
 // 
 /* Sample NTBL list */ 
 // 
  NTBL NAME(SLIST)  
NTBLENT STRING($S),OFFSET(1)
NTBLENT STRING(P),OFFSET(7) 
NTBLENT STRING(PAY),OFFSET(3)   

  NTBL NAME(SYSPRGSX)   
NTBLENT STRING(E18823),OFFSET(1)

_
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only.
Access to this E-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the
contents of this E-mail or any action taken (or not taken) in
reliance on it is unauthorized and may be unlawful. If you are not an
addressee, please inform the sender immediately, then delete this
message and empty from your trash.


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

Re: SDSF Question

[Jousma, David]

Just reread your post, you do have the IUID parm(didn't see it).  I
don't see a name however NAME(SYSPRGSX).  Not sure if that is a problem
or not.  My guess is your new GROUP is AFTER the the one you already
had, and the selection on that one is a first match.

_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB1G
p 616.653.8429
f 616.653.8497


-Original Message-
From: Jousma, David 
Sent: Friday, December 26, 2008 3:25 PM
To: 'IBM Mainframe Discussion List'
Subject: RE: SDSF Question

You don't say what the actual problem is, but remember, when using
ISFPARM's like this, the match is top down I believe.  Also, It would
probably help to add this to the paragraph:

IUID(SYSPRGSX), /* NAME TABLE USED FOR SELECTION
*/

_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB1G
p 616.653.8429
f 616.653.8497

-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:10 PM
To: IBM-MAIN@bama.ua.edu
Subject: SDSF Question

Hello all,
 
Below is an entry I placed is the ISFPARM's file in order to create a
new group for anyone who is listed under the "NTBL NAME(SYSPRGSX).
There is only one entry in NTBLENT.  This was done in order for various
people to do the SDSF LOG command and have the log come up at column 51.
 
I executed the following without any errors:
 
 F SDSF,REFRESH,M(HR)   
 ISF304I Modify REFRESH command accepted.   
 ISF726I SDSF parameter processing started. 
 ISF739I SDSF parameters being read from member ISFPRMHR of data set
 SYS2.PARMLIB.  
 ISF728I SDSF parameters have been activated.   
 
However this isn't working.  What am I missing?  Any help would be
appreciated.  Thanks.
 
GROUP IUID(SYSPRGSX),   /* Group name  */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT  */
ACTION(ALL),/* All route codes displayed   */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON),   /* Include APPC sysout */
AUPDT(2),   /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions   */
 SYSID,ABEND,ACTION,INPUT,   
 FINDLIM,ST,INIT,PR,TRACE,   
 ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),   
CMDAUTH(ALL),   /* Commands allowed for all jobs   */
CMDLEV(7),  /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation  */
CURSOR(ON), /* Leave cursor on last row processed  */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB),  /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'),   /* Default datesep format  */
DFIELD2(DAFLD2),/* Sample alternate field list for DA  */
DISPLAY(OFF),   /* Do not display current values   */
DSPAUTH(ALL),   /* Browse allowed for all jobs */
GPLEN(2),   /* Group prefix length */
ILOGCOL(51),/* Initial display column in log   */
ISYS(LOCAL),/* Initial system default for DA   */
LANG(ENGLISH),  /* Default language*/
LOGOPT(OPERACT),/* Default log option  */
OWNER(NONE),/* Default owner   */
UPCTAB(TRTAB2), /* Upper case translate table name */
VALTAB(TRTAB),  /* Valid character translate table */
VIO(SYSALLDA)   /* Unit name for page mode output  */
 
 // 
 /* Sample NTBL list */ 
 // 
  NTBL NAME(SLIST)  
NTBLENT STRING($S),OFFSET(1)
NTBLENT STRING(P),OFFSET(7) 
NTBLENT STRING(PAY),OFFSET(3)   

  NTBL NAME(SYSPRGSX)   
NTBLENT STRING(E18823),OFFSET(1)

_

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner

Re: SDSF Question

[Jousma, David]

You don't say what the actual problem is, but remember, when using
ISFPARM's like this, the match is top down I believe.  Also, It would
probably help to add this to the paragraph:

IUID(SYSPRGSX), /* NAME TABLE USED FOR SELECTION
*/

_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB1G
p 616.653.8429
f 616.653.8497

-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:10 PM
To: IBM-MAIN@bama.ua.edu
Subject: SDSF Question

Hello all,
 
Below is an entry I placed is the ISFPARM's file in order to create a
new group for anyone who is listed under the "NTBL NAME(SYSPRGSX).
There is only one entry in NTBLENT.  This was done in order for various
people to do the SDSF LOG command and have the log come up at column 51.
 
I executed the following without any errors:
 
 F SDSF,REFRESH,M(HR)   
 ISF304I Modify REFRESH command accepted.   
 ISF726I SDSF parameter processing started. 
 ISF739I SDSF parameters being read from member ISFPRMHR of data set
 SYS2.PARMLIB.  
 ISF728I SDSF parameters have been activated.   
 
However this isn't working.  What am I missing?  Any help would be
appreciated.  Thanks.
 
GROUP IUID(SYSPRGSX),   /* Group name  */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT  */
ACTION(ALL),/* All route codes displayed   */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON),   /* Include APPC sysout */
AUPDT(2),   /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions   */
 SYSID,ABEND,ACTION,INPUT,   
 FINDLIM,ST,INIT,PR,TRACE,   
 ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),   
CMDAUTH(ALL),   /* Commands allowed for all jobs   */
CMDLEV(7),  /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation  */
CURSOR(ON), /* Leave cursor on last row processed  */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB),  /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'),   /* Default datesep format  */
DFIELD2(DAFLD2),/* Sample alternate field list for DA  */
DISPLAY(OFF),   /* Do not display current values   */
DSPAUTH(ALL),   /* Browse allowed for all jobs */
GPLEN(2),   /* Group prefix length */
ILOGCOL(51),/* Initial display column in log   */
ISYS(LOCAL),/* Initial system default for DA   */
LANG(ENGLISH),  /* Default language*/
LOGOPT(OPERACT),/* Default log option  */
OWNER(NONE),/* Default owner   */
UPCTAB(TRTAB2), /* Upper case translate table name */
VALTAB(TRTAB),  /* Valid character translate table */
VIO(SYSALLDA)   /* Unit name for page mode output  */
 
 // 
 /* Sample NTBL list */ 
 // 
  NTBL NAME(SLIST)  
NTBLENT STRING($S),OFFSET(1)
NTBLENT STRING(P),OFFSET(7) 
NTBLENT STRING(PAY),OFFSET(3)   

  NTBL NAME(SYSPRGSX)   
NTBLENT STRING(E18823),OFFSET(1)

_
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only.
Access to this E-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the
contents of this E-mail or any action taken (or not taken) in
reliance on it is unauthorized and may be unlawful. If you are not an
addressee, please inform the sender immediately, then delete this
message and empty from your trash.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named

SDSF Question

[Howard Rifkind]

Hello all,
 
Below is an entry I placed is the ISFPARM's file in order to create a new group 
for anyone who is listed under the "NTBL NAME(SYSPRGSX).  There is only one 
entry in NTBLENT.  This was done in order for various people to do the SDSF LOG 
command and have the log come up at column 51.
 
I executed the following without any errors:
 
 F SDSF,REFRESH,M(HR)   
 ISF304I Modify REFRESH command accepted.   
 ISF726I SDSF parameter processing started. 
 ISF739I SDSF parameters being read from member ISFPRMHR of data set
 SYS2.PARMLIB.  
 ISF728I SDSF parameters have been activated.   
 
However this isn't working.  What am I missing?  Any help would be appreciated. 
 Thanks.
 
GROUP IUID(SYSPRGSX),   /* Group name  */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT  */
ACTION(ALL),/* All route codes displayed   */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON),   /* Include APPC sysout */
AUPDT(2),   /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions   */
 SYSID,ABEND,ACTION,INPUT,   
 FINDLIM,ST,INIT,PR,TRACE,   
 ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),   
CMDAUTH(ALL),   /* Commands allowed for all jobs   */
CMDLEV(7),  /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation  */
CURSOR(ON), /* Leave cursor on last row processed  */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB),  /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'),   /* Default datesep format  */
DFIELD2(DAFLD2),/* Sample alternate field list for DA  */
DISPLAY(OFF),   /* Do not display current values   */
DSPAUTH(ALL),   /* Browse allowed for all jobs */
GPLEN(2),   /* Group prefix length */
ILOGCOL(51),/* Initial display column in log   */
ISYS(LOCAL),/* Initial system default for DA   */
LANG(ENGLISH),  /* Default language*/
LOGOPT(OPERACT),/* Default log option  */
OWNER(NONE),/* Default owner   */
UPCTAB(TRTAB2), /* Upper case translate table name */
VALTAB(TRTAB),  /* Valid character translate table */
VIO(SYSALLDA)   /* Unit name for page mode output  */
 
 // 
 /* Sample NTBL list */ 
 // 
  NTBL NAME(SLIST)  
NTBLENT STRING($S),OFFSET(1)
NTBLENT STRING(P),OFFSET(7) 
NTBLENT STRING(PAY),OFFSET(3)   

  NTBL NAME(SYSPRGSX)   
NTBLENT STRING(E18823),OFFSET(1)

_
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only.
Access to this E-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the
contents of this E-mail or any action taken (or not taken) in
reliance on it is unauthorized and may be unlawful. If you are not an
addressee, please inform the sender immediately, then delete this
message and empty from your trash.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are looking at?

[Mark Zelden]

On Fri, 22 Feb 2008 17:16:10 -0500, Dave Barry <[EMAIL PROTECTED]> wrote:

>I believe shared ISPF profile is the case.  This behavior started in
>z/OS 1.8 with the advent of the SDSF address space.
>
>Thanks for the tip about using SYSID with no operands.
>

The SDSF server address space has been around *a long* time.  I think it 
was SDSF 1.6 which IIRC was the version that supported OS/390 R1 or
at least OS/390 R2.   It is just a way to manage the configuration of SDSF 
from a STC instead of assembling and linking them into the SDSF loadlib 
and makes it easy to change the configuration dynamically.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are looking at?

[Dave Barry]

I should have said, "when we upgraded to z/OS 1.8."  That must have been
when we started using the SDSF server.

Thanks again,
db 

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Schwarz, Barry A
Sent: Friday, February 22, 2008 5:19 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SDSF Question - How do you change the system log you are
looking at?

The SDSF Server, which is what runs in the SDSF address space, has been
around since at least OS/390 2.10.

-Original Message-
From: Dave Barry [mailto:[EMAIL PROTECTED]
Sent: Friday, February 22, 2008 2:16 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SDSF Question - How do you change the system log you are
looking at?

I believe shared ISPF profile is the case.  This behavior started in
z/OS 1.8 with the advent of the SDSF address space.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are looking at?

[Schwarz, Barry A]

The SDSF Server, which is what runs in the SDSF address space, has been
around since at least OS/390 2.10.

-Original Message-
From: Dave Barry [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 22, 2008 2:16 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SDSF Question - How do you change the system log you are
looking at?

I believe shared ISPF profile is the case.  This behavior started in
z/OS 1.8 with the advent of the SDSF address space.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are looking at?

[Dave Barry]

I believe shared ISPF profile is the case.  This behavior started in
z/OS 1.8 with the advent of the SDSF address space.

Thanks for the tip about using SYSID with no operands.

db 

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Mark Zelden
Sent: Friday, February 22, 2008 8:52 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SDSF Question - How do you change the system log you are
looking at?

On Thu, 21 Feb 2008 18:58:10 -0500, Dave Barry <[EMAIL PROTECTED]> wrote:

> In the latest SDSF, SYSID value is carried across LPARs in the plex 
>regardless of whether they are in a MAS.  Not sure about the 
>installation and customization, but I now have to use SYSID on every 
>system, even though none share a SPOOL.
>

Are you using a shared ISPF profile data set?   If you use SYSID without
any operands, it defaults to the current sysid.  Even if you share your
ISPF profile this will allow you to view the syslog of the system you
are logged onto without having to issue the SYSID command ever.  That is
the way it's always worked... unless something changed in 1.9 that
I am not aware of.   What has changed is the SYSID ? display in recent
releases.  It used to just show the value of the setting.  Now it will
display all the systems defined in the MASDEF (whether they exist or
not) with the system you are logged onto being enclosed in parenthesis.
In order to tell the current setting, you have to look at the title
line:

SDSF SYSLOG   397.101   IPO1 IPO2  11/15/2000  4W  
  |   | |   |  |   
Job   | |   |Outstandin
number| |   |WTORs 
  | |Date of   
   Data set |SYSLOG
   number   |data set  
|  
 JES2 system ID of the 
 log currently shown (IPO1), and   
 JES2 system ID of the system  
 the user is logged on to (IPO2)   

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead Zurich North America
/ Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at
http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

--
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are looking at?

[Shmuel Metz (Seymour J.)]

In <[EMAIL PROTECTED]>, on
02/21/2008
   at 06:58 PM, Dave Barry <[EMAIL PROTECTED]> said:

> In the latest SDSF, SYSID value is carried across LPARs in the plex
>regardless of whether they are in a MAS.

Doesn't that require MQ Series?
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are looking at?

[Mark Zelden]

On Thu, 21 Feb 2008 18:58:10 -0500, Dave Barry <[EMAIL PROTECTED]> wrote:

> In the latest SDSF, SYSID value is carried across LPARs in the plex
>regardless of whether they are in a MAS.  Not sure about the
>installation and customization, but I now have to use SYSID on every
>system, even though none share a SPOOL.
>

Are you using a shared ISPF profile data set?   If you use SYSID without
any operands, it defaults to the current sysid.  Even if you share your
ISPF profile this will allow you to view the syslog of the system you are 
logged onto without having to issue the SYSID command ever.  That
is the way it's always worked... unless something changed in 1.9 that
I am not aware of.   What has changed is the SYSID ? display in recent
releases.  It used to just show the value of the setting.  Now it will display
all the systems defined in the MASDEF (whether they exist or not) with the
system you are logged onto being enclosed in parenthesis.  In order to tell
the current setting, you have to look at the title line:

SDSF SYSLOG   397.101   IPO1 IPO2  11/15/2000  4W  
  |   | |   |  |   
Job   | |   |Outstandin
number| |   |WTORs 
  | |Date of   
   Data set |SYSLOG
   number   |data set  
|  
 JES2 system ID of the 
 log currently shown (IPO1), and   
 JES2 system ID of the system  
 the user is logged on to (IPO2)   

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are looking at?

[Dave Barry]

 In the latest SDSF, SYSID value is carried across LPARs in the plex
regardless of whether they are in a MAS.  Not sure about the
installation and customization, but I now have to use SYSID on every
system, even though none share a SPOOL.

db

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Mark Zelden

To clarify:  The "other system" can only be one in the same MAS.  If
your JES is not shared, it doesn't matter if the other system is in the
same
sysplex.   However, if OPERLOG is configured in the sysplex and the
other
system
participates, you can view the operlog and filter it to show only that
system.

Mark
--

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are look ing at?

[Stocker, Herman]

Thank to all who answered.  SYSID was the command I was looking for.

Regards, 
Herman Stocker


The sender believes that this E-mail and any attachments were free of any
virus, worm, Trojan horse, and/or malicious code when sent. This message and
its attachments could have been infected during transmission. By reading the
message and opening any attachments, the recipient accepts full
responsibility for taking protective and remedial action about viruses and
other defects. The sender's employer is not liable for any loss or damage
arising in any way from this message or its attachments.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are looking at?

[Mark Zelden]

On Wed, 20 Feb 2008 14:57:28 -0600, Paul Dineen <[EMAIL PROTECTED]> wrote:

>Herman,
>
>Is it the SDSF 'SYSID' command you're looking for?   "SYSID " where ""
>is the other system in your plex.
>

To clarify:  The "other system" can only be one in the same MAS.  If your
JES is not shared, it doesn't matter if the other system is in the same
sysplex.   However, if OPERLOG is configured in the sysplex and the other
system 
participates, you can view the operlog and filter it to show only that system.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are looking at?

[Ted MacNEIL]

>I'm on a 1.4 JES2 system (PLEX) with SDSF what I would like to do is to look 
>at a different system's log file from the one I'm on.  

>I know I did this before but can not find out how I did it again.

Primary command:
==> SYSID 

Where  is the JES-id for the target system.
Has been available for aeons.


-
Too busy driving to stop for gas!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are looking at?

[Paul Dineen]

Herman,

Is it the SDSF 'SYSID' command you're looking for?   "SYSID " where "" 
is the other system in your plex.

HTH,
Paul


On Wed, 20 Feb 2008 14:52:55 -0500, Stocker, Herman 
<[EMAIL PROTECTED]> wrote:

>G'day,
>I'm on a 1.4 JES2 system (PLEX) with SDSF what I would like to do is to look
>at a different system's log file from the one I'm on.  I know I did this
>before but can not find out how I did it again.
>
>Thank you.
>
>Regards,
>Herman Stocker
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question - How do you change the system log you are looking at?

[Ceruti, Gerard G]

Herman

Do you have OPERLOG enabled (syslog into a CF structure) if so, from
within SDSF, enter "set log ?" and select operlog, then "filter sysname
"  is the system's log you want to see.

Regards
Gerard Ceruti 
may the 'z' be with you


-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Stocker, Herman
Sent: 20 February 2008 09:53 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF Question - How do you change the system log you are
looking at?

G'day,
I'm on a 1.4 JES2 system (PLEX) with SDSF what I would like to do is to
look
at a different system's log file from the one I'm on.  I know I did this
before but can not find out how I did it again.

Thank you.

Regards, 
Herman Stocker


The sender believes that this E-mail and any attachments were free of
any
virus, worm, Trojan horse, and/or malicious code when sent. This message
and
its attachments could have been infected during transmission. By reading
the
message and opening any attachments, the recipient accepts full
responsibility for taking protective and remedial action about viruses
and
other defects. The sender's employer is not liable for any loss or
damage
arising in any way from this message or its attachments.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
__

Standard Bank Disclaimer and Confidentiality Note

This e-mail, its attachments and any rights attaching hereto are, unless the 
context clearly indicates otherwise, the property of Standard Bank Group Limited
and/or its subsidiaries ("the Group"). It is confidential, private and intended 
for the addressee only. Should you not be the addressee and receive this e-mail 
by
mistake, kindly notify the sender, and delete this e-mail, immediately and do 
not disclose or use same in any manner whatsoever. Views and opinions
expressed in this e-mail are those of the sender unless clearly stated as those 
of the Group. The Group accepts no liability whatsoever for any loss or
damages whatsoever and howsoever incurred, or suffered, resulting, or arising, 
from the use of this email or its attachments. The Group does not warrant the 
integrity
of this e-mail nor that it is free of errors, viruses, interception or 
interference. Licensed divisions of the Standard Bank Group are authorised 
financial services providers
in terms of the Financial Advisory and Intermediary Services Act, No 37 of 2002 
(FAIS).
For information about the Standard Bank Group Limited visit our website 
http://www.standardbank.co.za
___

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

SDSF Question - How do you change the system log you are looking at?

[Stocker, Herman]

G'day,
I'm on a 1.4 JES2 system (PLEX) with SDSF what I would like to do is to look
at a different system's log file from the one I'm on.  I know I did this
before but can not find out how I did it again.

Thank you.

Regards, 
Herman Stocker


The sender believes that this E-mail and any attachments were free of any
virus, worm, Trojan horse, and/or malicious code when sent. This message and
its attachments could have been infected during transmission. By reading the
message and opening any attachments, the recipient accepts full
responsibility for taking protective and remedial action about viruses and
other defects. The sender's employer is not liable for any loss or damage
arising in any way from this message or its attachments.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Ed Gould]

On Nov 6, 2007, at 4:13 AM, Shmuel Metz (Seymour J.) wrote:


In <[EMAIL PROTECTED]>, on 10/17/2007
   at 04:17 PM, Ed Gould <[EMAIL PROTECTED]> said:

That is interesting as we were early ship for PSF and we had our
hands

full with PSF PTF's but, I don't recall of a single JES2 issue


There was no PSF for the original 3800. It came later, with AFP.



I know that Shmuel. We were in the early ship program for PSF and all  
we had were 3800-3's and two 3820's. We did NOT have any 3800's  
before that. In fact we had XEROX printers. The majority of the bugs  
we found in PSF were in error recovery. there might have been some  
issue with JES2 in draining printers (not being able to) but  
canceling PSF  seemed to work. The (Xerox) units stood over in the  
corner and were standalone as I recall. The system created tapes and  
the operator manually had to take them over and mount them on the  
xerox unit and type some commands on the console (if thats the right  
term). It was somewhat error prone in that operators could forget to  
print tapes. I had the idea that these were expensive and that is why  
they pushed to get rid of them. Although, IIRC (memory is iffy here)  
IBM approached our management and had to do a sell on cost. We were  
lucky in that there was not a lot of custom programming that had been  
done for the xerox printers, so the conversion was relatively  
painless. IIRC (and it's been 15+ years) we had to create some  
IEBGENER jobs to chop off the data from 134-144 and some Fileaid   
jobs to insert 5A records. I was able to do this in an afternoon or  
less. Like I said we were lucky in that almost no custom programming  
had been done. We were really lucky that we did not have to touch any  
COBOL programs to accomplish this or the conversion would have  
probably would have taken months.


Ed

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Shmuel Metz (Seymour J.)]

In <[EMAIL PROTECTED]>, on 10/17/2007
   at 04:17 PM, Ed Gould <[EMAIL PROTECTED]> said:

>That is interesting as we were early ship for PSF and we had our   hands
>full with PSF PTF's but, I don't recall of a single JES2 issue

There was no PSF for the original 3800. It came later, with AFP.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Ed Gould]

On Oct 17, 2007, at 4:59 PM, Skip Robinson wrote:


This was definitely about 3800 device support. Historically JES2 had
controlled a slew of peripheral devices: printers, punches, TP,  
RJE, NJE.
The code to handle I/O to these devices was included in JES2  
modules. The
3800 was a logical candidate but a most unfortunate one. The 3800  
was far
more complex than any devices previously managed. As a brand new  
device, it
was also undergoing development and refinement. Every quirk and  
tweak had

to be handled by JES2 code. It was a quagmire.

As a consequence of that experience, FSS was born. From that point  
forward,
device support was externalized via a standard interface so that  
JES2 code
would never again have to confront the innards and foibles of new  
hardware.
In the interim, customers who suffered unstable JES2 would run a  
secondary

JES2 to take the hit for 3800 hiccups.

.



Skip,

Thanks for taking the brunt of the pain of the 3800.

Ed

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Skip Robinson]

This was definitely about 3800 device support. Historically JES2 had
controlled a slew of peripheral devices: printers, punches, TP, RJE, NJE.
The code to handle I/O to these devices was included in JES2 modules. The
3800 was a logical candidate but a most unfortunate one. The 3800 was far
more complex than any devices previously managed. As a brand new device, it
was also undergoing development and refinement. Every quirk and tweak had
to be handled by JES2 code. It was a quagmire.

As a consequence of that experience, FSS was born. From that point forward,
device support was externalized via a standard interface so that JES2 code
would never again have to confront the innards and foibles of new hardware.
In the interim, customers who suffered unstable JES2 would run a secondary
JES2 to take the hit for 3800 hiccups.

.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[EMAIL PROTECTED]


   
 Ed Gould  
 <[EMAIL PROTECTED] 
 AST.NET>   To 
 Sent by: IBM  IBM-MAIN@BAMA.UA.EDU
 Mainframe  cc 
 Discussion List   
 <[EMAIL PROTECTED] Subject 
 .EDU> Re: embarressing SDSF question. 
   
   
 10/17/2007 02:17  
 PM
   
   
 Please respond to 
   IBM Mainframe   
  Discussion List  
 <[EMAIL PROTECTED] 
   .EDU>   
   
   




On Oct 17, 2007, at 1:22 PM, Skip Robinson wrote:

> Running a secondary JES2 to support printing is a venerable
> tradition. Back
> in the day when 3800 printers first came out, the device support
> embedded
> in JES code was flaky. Keeping the subsystem running was a nightmare.
> Hardware problems--or software problems that failed to handle the
> hardware
> properly--caused frequent JES2 abends. In my shop we ran a
> secondary JES2
> solely for the purpose of managing the 3800s. When that JES2 went
> down, the
> rest of the world was sheltered from the disruption. It was years
> before we
> felt confident to revert to a single JES2.
>


Skip,

That is interesting as we were early ship for PSF and we had our
hands full with PSF PTF's but, I don't recall of a single JES2 issue
(my memory is fair in this area) I was on the phone daily with the
PSF level 2 people and we got to know each other pretty well. So I
think I would have remembered any JES2 issues or are you talking pre
PSF?

Ed

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Ed Gould]

On Oct 17, 2007, at 1:22 PM, Skip Robinson wrote:

Running a secondary JES2 to support printing is a venerable  
tradition. Back
in the day when 3800 printers first came out, the device support  
embedded

in JES code was flaky. Keeping the subsystem running was a nightmare.
Hardware problems--or software problems that failed to handle the  
hardware
properly--caused frequent JES2 abends. In my shop we ran a  
secondary JES2
solely for the purpose of managing the 3800s. When that JES2 went  
down, the
rest of the world was sheltered from the disruption. It was years  
before we

felt confident to revert to a single JES2.

The wrinkle of SDSF level was not an issue then. Setting up a  
'secondary
SDSF' is not a big deal as others have described. I've never had to  
use

STEPLIB for down-level compatibility, but I like the idea of limiting
secondary access to as few people as possible if only to avoid  
confusion.
Updating the old software would be nice, but I think you can run  
the shop

with what you have.

.


Skip,

That is interesting as we were early ship for PSF and we had our  
hands full with PSF PTF's but, I don't recall of a single JES2 issue  
(my memory is fair in this area) I was on the phone daily with the  
PSF level 2 people and we got to know each other pretty well. So I  
think I would have remembered any JES2 issues or are you talking pre  
PSF?


Ed

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Ed Gould]

On Oct 17, 2007, at 1:20 PM, Staller, Allan wrote:


Time for a new vendor! Their price may comde down rather quickly after
that!


Nope. The vendor has specifically stated that the release that we have
only supports the R4 format of the checkpoint.
And I've validated that by looking at their "interface" and  
changing it

to use the z2 format variables. It just doesn't work. They do have a
newer version, for more money.





I would have to agree with you on that. BUT anybody who would buy a  
product that is release dependent should have made sure that any  
upgrade is either reasonably priced (you pick your number) or free.  
When I was evaluating products a while back I always put a "NO" stamp  
on any release dependent product. I never had one get by me as I made  
sure management was aware of this and the auditors as well.


While 20/20 hindsight is good it (to me) just makes plain sense never  
agree to buy any product like this. At one place I worked one of the  
vendors did not charge for such upgrade BUT they used every advanced  
facility that was available to JES. Subsequently we had to keep JES2  
at an extremely current maintenance level. Frankly it was too  
bleeding edge for me. I spent more time keep JES current than I  
should have. While I semi liked the vendor it was a lot of extra work  
on my behalf. I was not lazy just trying to keep up with JES2  
maintenance is almost a fulltime job.


Ed

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[McKown, John]

> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Staller, Allan
> Sent: Wednesday, October 17, 2007 1:21 PM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: embarressing SDSF question.
> 
> 
> Time for a new vendor! Their price may comde down rather quickly after
> that!
> 

Well, they really have been pretty nice. This product used to be
"supported" by our "printer specialist", not Tech Services. He decided
to not even pay maintenance for that last 2 or 3 years, to save budget
money.

Also, it turns out that the "server" is running customized code from yet
another vendor. Most of us in Tech Services think it is time to rethink
all this custom code for printing. The problem is that the output from
the mainframe uses some very old coding from Xerox called MetaCode (akin
to PCL on a laserjet, but different). When we retired the Xerox Metacode
printers, it was decided to "emulate" them on the "server" to avoid
needing to change anything on the mainframe which is "going away".

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

The information contained in this e-mail message may be privileged
and/or confidential.  It is for intended addressee(s) only.  If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense.  If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Skip Robinson]

Running a secondary JES2 to support printing is a venerable tradition. Back
in the day when 3800 printers first came out, the device support embedded
in JES code was flaky. Keeping the subsystem running was a nightmare.
Hardware problems--or software problems that failed to handle the hardware
properly--caused frequent JES2 abends. In my shop we ran a secondary JES2
solely for the purpose of managing the 3800s. When that JES2 went down, the
rest of the world was sheltered from the disruption. It was years before we
felt confident to revert to a single JES2.

The wrinkle of SDSF level was not an issue then. Setting up a 'secondary
SDSF' is not a big deal as others have described. I've never had to use
STEPLIB for down-level compatibility, but I like the idea of limiting
secondary access to as few people as possible if only to avoid confusion.
Updating the old software would be nice, but I think you can run the shop
with what you have.

.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[EMAIL PROTECTED]


   
 "McKown, John"
 <[EMAIL PROTECTED] 
 THMARKETS.COM> To 
 Sent by: IBM  IBM-MAIN@BAMA.UA.EDU
 Mainframe  cc 
 Discussion List   
 <[EMAIL PROTECTED] Subject 
 .EDU>     Re: embarressing SDSF question. 
   
   
 10/17/2007 10:20  
 AM
   
   
 Please respond to 
   IBM Mainframe   
  Discussion List  
 <[EMAIL PROTECTED] 
   .EDU>   
   
   




> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Jousma, David
> Sent: Wednesday, October 17, 2007 12:13 PM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: embarressing SDSF question.
>
>
> Rather than rolling out 2 different versions of sdsf to the world, why
> not have the output from the secondary(backleveled JES) all routed via
> NJE to the primary jes?  Then you would only need to logon via special
> proc to debug problems(hopefully not too often).
> 
> Dave Jousma

Actually, nothing runs on the secondary JES2. We have some very old
software which takes SPOOL output from JES2 and sends it to a
specialized server. This software cannot tolerate the z2 level of the
JES2 checkpoint, only the R4 format. So I need to run the z/OS 1.6 JES2
with a different set of SPOOL and checkpoint datasets so that I can have
the R4 format checkpoint. The jobs are run under the primary (1.8) JES2
and NJE'ed to the secondary JES2 so that the software can pick them up
and send the reports to that specialized server.

We're trying to justify the cost for the newer software.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Staller, Allan]

Time for a new vendor! Their price may comde down rather quickly after
that!


Nope. The vendor has specifically stated that the release that we have
only supports the R4 format of the checkpoint. 
And I've validated that by looking at their "interface" and changing it
to use the z2 format variables. It just doesn't work. They do have a
newer version, for more money.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[McKown, John]

> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Elardus Engelbrecht
> Sent: Wednesday, October 17, 2007 1:10 PM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: embarressing SDSF question.
> 



> AFAIK, third party software which are reading JES2 SPOOL are 
> usually supplied 
> with assembler steps to pickup the JES2 spool macro layout 
> from whatever 
> MODGEN or MACLIB you choose to use.
> 



> 
> Do your software has something similiar?
> 
> If not, you can ask support from the vendor in this case. You 
> may/can/should 
> use my argument as a subtle weapon to lower pricing for a new 
> release... ;-D
> 
> HTH!
> 
> Groete / Greetings
> Elardus Engelbrecht

Nope. The vendor has specifically stated that the release that we have
only supports the R4 format of the checkpoint. 
And I've validated that by looking at their "interface" and changing it
to use the z2 format variables. It just doesn't work. They do have a
newer version, for more money.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

The information contained in this e-mail message may be privileged
and/or confidential.  It is for intended addressee(s) only.  If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense.  If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Elardus Engelbrecht]

McKown, John wrote:

>We have some very old software which takes SPOOL output from JES2 and 
sends it to a specialized server. This software cannot tolerate the z2 level of 
the JES2 checkpoint, only the R4 format.

AFAIK, third party software which are reading JES2 SPOOL are usually supplied 
with assembler steps to pickup the JES2 spool macro layout from whatever 
MODGEN or MACLIB you choose to use.

For example with EPS, VPS, TSPRINT and JES328X (Basically SPOOL readers) 
we have to reassemble the modules which are reading the JES2 SPOOL during 
each JES2 upgrade. 

The same goes for third party TP software which are also reading SPOOL data.

Do your software has something similiar?

If not, you can ask support from the vendor in this case. You may/can/should 
use my argument as a subtle weapon to lower pricing for a new release... ;-D

HTH!

Groete / Greetings
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Jousma, David]

Gotcha, mis-understood the situation. 



Dave Jousma
Mainframe Services
[EMAIL PROTECTED]
616.653.8429



This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[McKown, John]

> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Jousma, David
> Sent: Wednesday, October 17, 2007 12:13 PM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: embarressing SDSF question.
> 
> 
> Rather than rolling out 2 different versions of sdsf to the world, why
> not have the output from the secondary(backleveled JES) all routed via
> NJE to the primary jes?  Then you would only need to logon via special
> proc to debug problems(hopefully not too often). 
> 
> Dave Jousma

Actually, nothing runs on the secondary JES2. We have some very old
software which takes SPOOL output from JES2 and sends it to a
specialized server. This software cannot tolerate the z2 level of the
JES2 checkpoint, only the R4 format. So I need to run the z/OS 1.6 JES2
with a different set of SPOOL and checkpoint datasets so that I can have
the R4 format checkpoint. The jobs are run under the primary (1.8) JES2
and NJE'ed to the secondary JES2 so that the software can pick them up
and send the reports to that specialized server.

We're trying to justify the cost for the newer software.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

The information contained in this e-mail message may be privileged
and/or confidential.  It is for intended addressee(s) only.  If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense.  If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Jousma, David]

Rather than rolling out 2 different versions of sdsf to the world, why
not have the output from the secondary(backleveled JES) all routed via
NJE to the primary jes?  Then you would only need to logon via special
proc to debug problems(hopefully not too often). 



Dave Jousma
Mainframe Services
[EMAIL PROTECTED]
616.653.8429


-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Elardus Engelbrecht
Sent: Wednesday, October 17, 2007 12:10 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: embarressing SDSF question.

McKown, John  wrote:
>The question I have is how to get SDSF to access the JESA system. I 
>think
that I'll need to use the 1.6 version of SDSF due to the JES2
dependancies in the SDSF code. True? I am just not figuring out how to
do this. The closest that I've come up with is a second TSO proc which
is STEPLIB'ed to the old SDSF code.


Create a second SDSF server and have your users with correct STEPLIB
connect to the correct SDSF server which will use/point to the correct
JES2.

Look in SDSF book for the word SERVERGROUP where you can use the correct
name of the SDSF server against whatever JES2 and whatever JES2 HASP
member.

Start a new server with something like S SDSF.SDSFT

Use TSO command to access correct SDSF server: SDSF SERVER(SDSFT).

PS: I never tried that, but once done this something like this for JESA
and JES328X when on OS/390.

HTH!


This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Elardus Engelbrecht]

McKown, John  wrote:
>The question I have is how to get SDSF to access the JESA system. I think 
that I'll need to use the 1.6 version of SDSF due to the JES2 dependancies in 
the SDSF code. True? I am just not figuring out how to do this. The closest 
that I've come up with is a second TSO proc which is STEPLIB'ed to the old 
SDSF code.


Create a second SDSF server and have your users with correct STEPLIB 
connect to the correct SDSF server which will use/point to the correct JES2.

Look in SDSF book for the word SERVERGROUP where you can use the correct 
name of the SDSF server against whatever JES2 and whatever JES2 HASP 
member.

Start a new server with something like S SDSF.SDSFT

Use TSO command to access correct SDSF server: SDSF SERVER(SDSFT).

PS: I never tried that, but once done this something like this for JESA and 
JES328X when on OS/390.

HTH!

Groete / Greetings 
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Rick Fochtman]

--


We upgraded from z/OS 1.6 to 1.8 over the weekend. We have run into one
really bad problem. The z/OS 1.6 JES2 was running in R4 mode. We have a
product which sends output to a specialized printer. This product does
not support the "z" level of the checkpoint. We are adverse to upgrading
the product to the newest release due to the cost. What I am thinking
might work would be to run a secondary JES on z/OS 1.8. This JES2 would
be the 1.6 release with its own SPOOL, in R4 format. We would connect
the 1.8 JES2 to the 1.6 via NJE. We would then point the product to the
alternate, 1.6, JES (JESA) SPOOL and start it SUB=JESA. I think this
would work. The print operator would then change the DEST of the print
from LOCAL to the JESA node to transmit the SPOOL to JESA. Hopefully
this will work.

The question I have is how to get SDSF to access the JESA system. I
think that I'll need to use the 1.6 version of SDSF due to the JES2
dependancies in the SDSF code. True? I am just not figuring out how to
do this. The closest that I've come up with is a second TSO proc which
is STEPLIB'ed to the old SDSF code.
 


---
John, what you propose might be a usable solution; we tried something 
similar years ago at Clearing. Probably the biggest problems you'll 
encounter will be human error on the part of the print operator who's 
shuffling things back and forth between spools. IMHO, you'll be better 
off in the long run to bite the bullet and upgrade your specialized 
print processor. If you threaten the vendor with discontinuation of the 
product, maybe they'll be a little more friendly with their upgrade pricing.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: embarressing SDSF question.

[Big Iron]

I believe that it is documented in the z/OS 1.8 migration guide that you
need to be in z2 mode to use the 1.8 version of SDSF. See APAR PK27162
for HQX7720.

Bill

On Tue, 16 Oct 2007 07:51:48 -0500, McKown, John
<[EMAIL PROTECTED]> wrote:

>We upgraded from z/OS 1.6 to 1.8 over the weekend. We have run into one
>really bad problem. The z/OS 1.6 JES2 was running in R4 mode. We have a
>product which sends output to a specialized printer. This product does
>not support the "z" level of the checkpoint. We are adverse to upgrading
>the product to the newest release due to the cost. What I am thinking
>might work would be to run a secondary JES on z/OS 1.8. This JES2 would
>be the 1.6 release with its own SPOOL, in R4 format. We would connect
>the 1.8 JES2 to the 1.6 via NJE. We would then point the product to the
>alternate, 1.6, JES (JESA) SPOOL and start it SUB=JESA. I think this
>would work. The print operator would then change the DEST of the print
>from LOCAL to the JESA node to transmit the SPOOL to JESA. Hopefully
>this will work.
>
>The question I have is how to get SDSF to access the JESA system. I
>think that I'll need to use the 1.6 version of SDSF due to the JES2
>dependancies in the SDSF code. True? I am just not figuring out how to
>do this. The closest that I've come up with is a second TSO proc which
>is STEPLIB'ed to the old SDSF code.
>
>--
>John McKown
>Senior Systems Programmer
>HealthMarkets
>Keeping the Promise of Affordable Coverage
>Administrative Services Group
>Information Technology

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

embarressing SDSF question.

[McKown, John]

We upgraded from z/OS 1.6 to 1.8 over the weekend. We have run into one
really bad problem. The z/OS 1.6 JES2 was running in R4 mode. We have a
product which sends output to a specialized printer. This product does
not support the "z" level of the checkpoint. We are adverse to upgrading
the product to the newest release due to the cost. What I am thinking
might work would be to run a secondary JES on z/OS 1.8. This JES2 would
be the 1.6 release with its own SPOOL, in R4 format. We would connect
the 1.8 JES2 to the 1.6 via NJE. We would then point the product to the
alternate, 1.6, JES (JESA) SPOOL and start it SUB=JESA. I think this
would work. The print operator would then change the DEST of the print
from LOCAL to the JESA node to transmit the SPOOL to JESA. Hopefully
this will work.

The question I have is how to get SDSF to access the JESA system. I
think that I'll need to use the 1.6 version of SDSF due to the JES2
dependancies in the SDSF code. True? I am just not figuring out how to
do this. The closest that I've come up with is a second TSO proc which
is STEPLIB'ed to the old SDSF code.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

The information contained in this e-mail message may be privileged
and/or confidential.  It is for intended addressee(s) only.  If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense.  If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Batch SDSF Question regarding ISFAFD

[JONES, CHARLIE]

I have used batch SDSF for years but now I need to notch it up a level.
I would
need to update some of the fields where overtyping is allowed.  I don't
believe batch
SDSF will allow this but I have found hints that ISFAFD will.  Anyone
out there have
a sample piece of JCL that shows how to tab over and change field values
in batch
ISFAFD?

Charlie Jones

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Eric Bielefeld]

Shane,

I finally got around to looking at the archives.  Yes, there are several 
good discussions about ECPU vs CPU time & percent.  There is a good 
discussion from January 2004.  I think I understand the difference now.

Eric Bielefeld
Sr. Systems Programmer
Lands' End
608-935-4680


On Mon, 11 Dec 2006 10:16:18 +1000, Shane Ginnane <[EMAIL PROTECTED]> 
wrote:

>> What is the difference between CPU% and ECPU%.
>
>Search the archives Eric - has ben debated (at depth) here in the last
>couple of years.
>
>> Also, what is the SCPU%?
>
>System CPU - from ERBSMFI no doubt. Same number used everywhere.
>
>Shane ...

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Shmuel Metz (Seymour J.)]

In
<[EMAIL PROTECTED]>,
on 09/25/2006
   at 06:45 PM, Kirk Talman <[EMAIL PROTECTED]> said:

>It's been +10 yrs since I worked on TPX as a developer, but the
>behavior  you describe is the difference between SNA and non-SNA
>protocol.  Under  SNA protocol ATTN replaces PA1, because RESET will
>not unlock the keyboard  and give you direction if the application
>has not already given it to you,  or ended the bracket so that you
>can use implied BID to get direction.

Even on local non-SNA there are situations where ATTN will work but
PA1 will not.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Shmuel Metz (Seymour J.)]

In <[EMAIL PROTECTED]>, on 09/26/2006
   at 01:51 AM, Binyamin Dissen <[EMAIL PROTECTED]> said:

>When I did VTAM programming, to communicate SNA out-of-line (when you
>did not own the direction) required sending a request to the PLU
>(ATTN) or SLU to give you control and then you could do your data
>transfer.

More precisely, certain type of Request Units are synchronous and
certain are asynchronous. You can send any asynchronous RU at any
time, including SIGNAL, regardless of the bracket state.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Chris Mason]

Kirk

Thanks for confirming that my guess that "Attn" would work for Ed is
correct.

I'll confess that I missed out the BID angle since my post was quite long
enough already. In my description of the way the "change direction" (CD)
indicator works, I had assumed that the LU type 2 session was already "in
brackets" and hence was observing the strict half-duplex protocol.

I've not come across the expression "get direction" before. For those who
have to work harder to follow our jargon, this appears to mean "be granted
the permission to send a message".

Having mentioned the bracket protocol, perhaps one can say that, although
"between brackets" is no longer the strict half-duplex environment created
when "in brackets" is in effect, there is still a sort of half-duplex
situation applying. "Between brackets", the secondary LU (3270 display) has
permission to send, has "got direction", up to the time that the primary LU
(application) may send the approximate equivalent of the SIGNAL request, the
BID request, and the secondary LU has responded positively. Necessarily, the
first message sent when in the "between brackets" state must initiate a
bracket by sending the "begin bracket" indicator in the header. You also
reminded me that it's only the primary LU which can decide to terminate the
"in brackets" state, reverting to the "between brackets" state, by sending
the "end bracket" indicator in the header.

Chris Mason

- Original Message - 
From: "Kirk Talman" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: 
Sent: Tuesday, 26 September, 2006 12:45 AM
Subject: Re: SDSF Question


> It's been +10 yrs since I worked on TPX as a developer, but the behavior
> you describe is the difference between SNA and non-SNA protocol.  Under
> SNA protocol ATTN replaces PA1, because RESET will not unlock the keyboard
> and give you direction if the application has not already given it to you,
> or ended the bracket so that you can use implied BID to get direction.
>
> Today I use Extra and (ughh0 Switch, and they use the SNA protocol,
> probably under DFT protocol.  I use ATTN to get direction when I don't
> have it.
>
> IBM Mainframe Discussion List  wrote on 9/22/2006
> 11:39:24 PM:
>
> > 10+ years ago we had a vtam appl switcher (sorry forgot the name but
> > it could have been TPX).
>
> > It worked great on real 3270's but they made us switch over pc's. The
> > 3270 emulator would not let us hit reset and pa1 . It essentially
> > made the vtam appl switcher unusable. grumble grumble I complained
> > but no one would listen. I suggested dropping the product as it was
> > useless now. The VP of the PC department got  p-oed. We had a meeting
> > and when I showed up with VTAM traces to prove his emulator wasn't
> > working correctly he got even madder.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Binyamin Dissen]

On Mon, 25 Sep 2006 18:45:08 -0400 Kirk Talman <[EMAIL PROTECTED]> wrote:

:>It's been +10 yrs since I worked on TPX as a developer, but the behavior 
:>you describe is the difference between SNA and non-SNA protocol.  Under 
:>SNA protocol ATTN replaces PA1, because RESET will not unlock the keyboard 
:>and give you direction if the application has not already given it to you, 
:>or ended the bracket so that you can use implied BID to get direction.

When I did VTAM programming, to communicate SNA out-of-line (when you did not
own the direction) required sending a request to the PLU (ATTN) or SLU to give
you control and then you could do your data transfer.

Non-SNA is a free for all - each side can send data at any time.

--
Binyamin Dissen <[EMAIL PROTECTED]>
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Kirk Talman]

It's been +10 yrs since I worked on TPX as a developer, but the behavior 
you describe is the difference between SNA and non-SNA protocol.  Under 
SNA protocol ATTN replaces PA1, because RESET will not unlock the keyboard 
and give you direction if the application has not already given it to you, 
or ended the bracket so that you can use implied BID to get direction.

Today I use Extra and (ughh0 Switch, and they use the SNA protocol, 
probably under DFT protocol.  I use ATTN to get direction when I don't 
have it.

IBM Mainframe Discussion List  wrote on 9/22/2006 
11:39:24 PM:

> 10+ years ago we had a vtam appl switcher (sorry forgot the name but 
> it could have been TPX).

> It worked great on real 3270's but they made us switch over pc's. The 
> 3270 emulator would not let us hit reset and pa1 . It essentially 
> made the vtam appl switcher unusable. grumble grumble I complained 
> but no one would listen. I suggested dropping the product as it was 
> useless now. The VP of the PC department got  p-oed. We had a meeting 
> and when I showed up with VTAM traces to prove his emulator wasn't 
> working correctly he got even madder.



-
The information contained in this communication (including any
attachments hereto) is confidential and is intended solely for the
personal and confidential use of the individual or entity to whom
it is addressed.  The information may also constitute a legally
privileged confidential communication.  If the reader of this
message is not the intended recipient or an agent responsible for
delivering it to the intended recipient, you are hereby notified
that you have received this communication in error and that any
review, dissemination, copying, or unauthorized use of this
information, or the taking of any action in reliance on the
contents of this information is strictly prohibited.  If you have
received this communication in error, please notify us immediately
by e-mail, and delete the original message.  Thank you

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Chris Mason]

not
locked.

Warning: I've composed this largely from memory but I'm sure I'll be
corrected where I have strayed too far from full accuracy.

Chris Mason

- Original Message - 
From: "Ed Gould" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: 
Sent: Saturday, 23 September, 2006 5:39 AM
Subject: Re: SDSF Question


> 10+ years ago we had a vtam appl switcher (sorry forgot the name but
> it could have been TPX).
>
> It worked great on real 3270's but they made us switch over pc's. The
> 3270 emulator would not let us hit reset and pa1 . It essentially
> made the vtam appl switcher unusable. grumble grumble I complained
> but no one would listen. I suggested dropping the product as it was
> useless now. The VP of the PC department got  p-oed. We had a meeting
> and when I showed up with VTAM traces to prove his emulator wasn't
> working correctly he got even madder.
>
> Ed
>
> On Sep 22, 2006, at 10:18 AM, Greg Shirey wrote:
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
> > On Behalf
> > Of Shmuel Metz (Seymour J.)
> > Sent: Friday, September 22, 2006 7:31 AM
> >
> >> In <[EMAIL PROTECTED]>, on 09/21/2006
> >at 04:25 PM, Greg Shirey <[EMAIL PROTECTED]> said:
> >
> >>> PA1.
> >
> >> That won't work if the keyboard is locked. Attention should always
> >> work.
> >
> > Shmuel,
> >
> > Thanks for that helpful information.  I never knew that.
> > And it works with MacKinney's VTAM/Switch (which uses the PA1 key
> > to switch
> > between sessions) - that is, pressing Attention returns control to
> > Switch
> > where you can type "SIM PA1" (simulate pressing PA1) to end the SDSF
> > auto-update.
> >
> > Greg Shirey
> > Ben E. Keith Company

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Ed Gould]

10+ years ago we had a vtam appl switcher (sorry forgot the name but  
it could have been TPX).


It worked great on real 3270's but they made us switch over pc's. The  
3270 emulator would not let us hit reset and pa1 . It essentially  
made the vtam appl switcher unusable. grumble grumble I complained  
but no one would listen. I suggested dropping the product as it was  
useless now. The VP of the PC department got  p-oed. We had a meeting  
and when I showed up with VTAM traces to prove his emulator wasn't  
working correctly he got even madder.


Ed

On Sep 22, 2006, at 10:18 AM, Greg Shirey wrote:


-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]  
On Behalf

Of Shmuel Metz (Seymour J.)
Sent: Friday, September 22, 2006 7:31 AM


In <[EMAIL PROTECTED]>, on 09/21/2006

   at 04:25 PM, Greg Shirey <[EMAIL PROTECTED]> said:


PA1.


That won't work if the keyboard is locked. Attention should always  
work.


Shmuel,

Thanks for that helpful information.  I never knew that.
And it works with MacKinney's VTAM/Switch (which uses the PA1 key  
to switch
between sessions) - that is, pressing Attention returns control to  
Switch

where you can type "SIM PA1" (simulate pressing PA1) to end the SDSF
auto-update.

Greg Shirey
Ben E. Keith Company

## 
##
As of January 1, 2007, Ben E. Keith Company will no longer accept  
emails
addressed to our "bekco.com" address. Please change your  
information for

all Ben E. Keith contacts to our new email address, "benekeith.com".
Thank you.
## 
##


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Greg Shirey]

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Shmuel Metz (Seymour J.)
Sent: Friday, September 22, 2006 7:31 AM

>In <[EMAIL PROTECTED]>, on 09/21/2006
   at 04:25 PM, Greg Shirey <[EMAIL PROTECTED]> said:

>>PA1.

>That won't work if the keyboard is locked. Attention should always work.
 
Shmuel,

Thanks for that helpful information.  I never knew that.  
And it works with MacKinney's VTAM/Switch (which uses the PA1 key to switch
between sessions) - that is, pressing Attention returns control to Switch
where you can type "SIM PA1" (simulate pressing PA1) to end the SDSF
auto-update.

Greg Shirey
Ben E. Keith Company 


As of January 1, 2007, Ben E. Keith Company will no longer accept emails
addressed to our "bekco.com" address. Please change your information for
all Ben E. Keith contacts to our new email address, "benekeith.com". 
Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Tim Henness]

We have it disabled for most users at our shop because it also has the side-
effect of bypassing the TSO inactivity timeout, enforced by the SMFPRMxx JWT
(nnn) option.

Tim

On Thu, 21 Sep 2006 16:30:46 -0500, Mark Zelden <[EMAIL PROTECTED]> 
wrote:

>
>Speaking of SDSF auto update...
>
>I've been at a lot of shops that disabled it (it least from all but
>a few select groups / users) because it skews TSO response time numbers.
>Others at least make the minimum update interval no less than some
>number like 10 to 15 seconds.  I of course let myself do it with a
>an update interval of 2 seconds.  :-)  Actually... I can't remember
>the last time I used it.  I prefer to hit enter as fast as I can in
>the DA screen to chew up as many CPU cycles as possible.
>
>Mark

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Chase, John]

> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of McKnight, Lee
> 
> That's really cool; but how do you stop it?  The auto update 
> has my screen locked!

PA1 key.

-jc-

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Shmuel Metz (Seymour J.)]

In <[EMAIL PROTECTED]>, on 09/21/2006
   at 04:25 PM, Greg Shirey <[EMAIL PROTECTED]> said:

>PA1.

That won't work if the keyboard is locked. Attention should always
work.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Shmuel Metz (Seymour J.)]

In
<[EMAIL PROTECTED]>,
on 09/21/2006
   at 04:13 PM, "McKnight, Lee" <[EMAIL PROTECTED]> said:

>That's really cool; but how do you stop it? 

With Attention[1]. Check your keyboard map.

[1] Not the same as PA1.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Shmuel Metz (Seymour J.)]

In <[EMAIL PROTECTED]>, on
09/20/2006
   at 08:57 PM, Dean Montevago <[EMAIL PROTECTED]> said:

>What is this ?

Check the key mapping on your 3270 simulator. I believe that you'll
find that PF1-12 map to PFK 1-12 and that Shift-PF1-12 map to PFK
13-24. So what you're actually seeing is PFK 19.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Alan Schwartz]

We had a case a number of years ago where this caused a problem.  We used 
a VTAM session manager and a programmer turned the Autoupdate display and 
then left his desk.  The session manager went to a password required 
screen after some period of inactivity and the SDSF screen images kept 
accumulating.  Soon enough it terminated with an 878 abend. 

Bye-bye Autoupdate.

Alan Schwartz
Assurant Shared Business Services
Lead Systems Programmer
Phone:  651-361-4758
Fax:   651-361-5625



Robert Bardos <[EMAIL PROTECTED]> 
Sent by: IBM Mainframe Discussion List 
09/22/2006 03:24 AM
Please respond to
IBM-Main List 


To
IBM-MAIN@BAMA.UA.EDU
cc

Subject
Re: SDSF Question






With regards to SDSF Auto-Update:

a) it works as well when SDSF is started under ISPF (unless it has
been deactivated)

b) stopping it when TSO/ISPF has been started under control of a
session manager can be achieved (at least at the sites that I
know) by pressing ATTN twice (quickly). ATTN (function [sys attn]
in PCOMM) often being mapped to the ESC key. Pressing it only once
usually brings you back to the application menu screen.

Robert

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


**
This e-mail message and all attachments transmitted with it may contain legally 
privileged and/or confidential information intended solely for the use of the 
addressee(s). If the reader of this message is not the intended recipient, you 
are hereby notified that any reading, dissemination, distribution, copying, 
forwarding or other use of this message or its attachments is strictly 
prohibited. If you have received this message in error, please notify the 
sender immediately and delete this message and all copies and backups thereof.

Thank you.
**

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Daniel A. McLaughlin]

Isn't it like that other operating system that runs the computers that 
people can pick up? Wouldn't you have to do a power on/reset to stop it?

Back to Friday...




Daniel McLaughlin
ZOS Systems Programmer
Crawford & Company
PH: 770 621 3256
[EMAIL PROTECTED]









--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Robert Bardos]

With regards to SDSF Auto-Update:

a) it works as well when SDSF is started under ISPF (unless it has
been deactivated)

b) stopping it when TSO/ISPF has been started under control of a
session manager can be achieved (at least at the sites that I
know) by pressing ATTN twice (quickly). ATTN (function [sys attn]
in PCOMM) often being mapped to the ESC key. Pressing it only once
usually brings you back to the application menu screen.

Robert

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Ed Gould]

Ron,

Agreed, I had it disabled since I first was responsible for the  
product (IIRC it was an FDP). I agree that it skewed TSO response  
time numbers. I let sysprogs have it but they used it sparingly and  
responsibly. I also set it up so the users could only view *THIER*  
jobs. Operators were allowed to see everything.


Usually when a new person showed up and asked for the ability to view  
everything. I always said NO and if they wanted to push it take it to  
their supervisor. The request never made it past them.


Ed

On Sep 21, 2006, at 7:09 PM, Ron Hawkins wrote:


Mark,

Don't bite that tongue in your cheek...

At a site I was in 15 years ago (you know who you are) the head of
Development had the SDSF "DA" screen disabled for all programmers and
analysts. Result was a 5% drop in daily CPUTM for TSO.

This was accompanied by drop in phone calls asking "why is my job  
swapped
out" "please speed up my job" "why are there so many CICS regions"  
blah blah

blah. What a productivity boost - for me anyway :)

Ron


an update interval of 2 seconds.  :-)  Actually... I can't remember
the last time I used it.  I prefer to hit enter as fast as I can in
the DA screen to chew up as many CPU cycles as possible.

Mark


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Ron Hawkins]

Mark,

Don't bite that tongue in your cheek... 

At a site I was in 15 years ago (you know who you are) the head of
Development had the SDSF "DA" screen disabled for all programmers and
analysts. Result was a 5% drop in daily CPUTM for TSO.

This was accompanied by drop in phone calls asking "why is my job swapped
out" "please speed up my job" "why are there so many CICS regions" blah blah
blah. What a productivity boost - for me anyway :)

Ron

> an update interval of 2 seconds.  :-)  Actually... I can't remember
> the last time I used it.  I prefer to hit enter as fast as I can in
> the DA screen to chew up as many CPU cycles as possible.
> 
> Mark

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Thompson, Steve (SCI TW)]

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Mark Zelden
Sent: Thursday, September 21, 2006 4:31 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SDSF Question

I prefer to hit enter as fast as I can in
the DA screen to chew up as many CPU cycles as possible. 


I presume that she who must be obeyed when you were little did not teach
you about interrupting being bad manners?

;-)

Later,
Steve Thompson

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Mark Zelden]

On Thu, 21 Sep 2006 16:13:13 -0500, McKnight, Lee <[EMAIL PROTECTED]> wrote:

>That's really cool; but how do you stop it?  The auto update has my
>screen locked!
>

With an operator command: C U=tso_userid:-) 

Use the attention key (SNA) or PA1 (non-sna).

Speaking of SDSF auto update...

I've been at a lot of shops that disabled it (it least from all but
a few select groups / users) because it skews TSO response time numbers. 
Others at least make the minimum update interval no less than some
number like 10 to 15 seconds.  I of course let myself do it with a
an update interval of 2 seconds.  :-)  Actually... I can't remember
the last time I used it.  I prefer to hit enter as fast as I can in
the DA screen to chew up as many CPU cycles as possible. 

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group
mailto: [EMAIL PROTECTED]
z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Greg Shirey]

PA1.  (You have to know where your terminal emulator maps that key...) 

Greg Shirey
Ben E. Keith Company

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of McKnight, Lee
Sent: Thursday, September 21, 2006 4:13 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SDSF Question


That's really cool; but how do you stop it?  The auto update has my
screen locked!

Thanks, Mac.
Lee McKnight CDP, BIG
Mainframe Engineer
TRC, Inc.
z/OS Systems/Linux
563.262.5334
[EMAIL PROTECTED]
[EMAIL PROTECTED]
www.trctac.com
 

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Dean Montevago
Sent: Wednesday, September 20, 2006 7:58 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF Question

Hi,

I'm at a DR test right now and one of the operators showed me this
command in SDSF. You hit SHIFT and PF7 and an ampersand appears on the
command you type in a time interval (in seconds) and a message appears
on the command:  AUTO UPDATE (with the time interval you selected)
. This allows you to see a job transition through it's steps without
having to hit enter. The operator told me he's used this in other shops.
What is this ? Where is this ? 

TIA
Dean 

Dean Montevago
Sr. Systems Specialist
Visiting Nurse Service of New York
(212) 609 - 5596
[EMAIL PROTECTED]

--
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


As of January 1, 2007, Ben E. Keith Company will no longer accept emails
addressed to our "bekco.com" address. Please change your information for
all Ben E. Keith contacts to our new email address, "benekeith.com". 
Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[McKnight, Lee]

That's really cool; but how do you stop it?  The auto update has my
screen locked!

Thanks, Mac.
Lee McKnight CDP, BIG
Mainframe Engineer
TRC, Inc.
z/OS Systems/Linux
563.262.5334
[EMAIL PROTECTED]
[EMAIL PROTECTED]
www.trctac.com
 

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Dean Montevago
Sent: Wednesday, September 20, 2006 7:58 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF Question

Hi,

I'm at a DR test right now and one of the operators showed me this
command in SDSF. You hit SHIFT and PF7 and an ampersand appears on the
command you type in a time interval (in seconds) and a message appears
on the command:  AUTO UPDATE (with the time interval you selected)
. This allows you to see a job transition through it's steps without
having to hit enter. The operator told me he's used this in other shops.
What is this ? Where is this ? 

TIA
Dean 

Dean Montevago
Sr. Systems Specialist
Visiting Nurse Service of New York
(212) 609 - 5596
[EMAIL PROTECTED]

--
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Ted MacNEIL]

>This is the autoupdate feature.

IIRC, this only works with the TSO version (from READY), and not the ISPF 
version.

When in doubt.
PANIC!!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Robert Bardos]

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
On
Behalf Of Dean Montevago
Sent: Thursday, 21 September 2006 10:28 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF Question

Hi,

I'm at a DR test right now and one of the operators showed me this
command in SDSF. You hit SHIFT and PF7 and an ampersand appears on
the
command you type in a time interval (in seconds) and a message
appears
on the command:  AUTO UPDATE (with the time interval you
selected)
. This allows you to see a job transition through it's steps
without
having to hit enter. The operator told me he's used this in other
shops.
What is this ? Where is this ?

TIA
Dean

  - - - - - - - - -


This is the autoupdate feature.

Do sometimes use it myself in the form of "bottom&15" when having
an eye on the output of long-running jobs as it grows. (Or when
watching the syslog deep in the night. But this was a long time
ago when message rates were much, much lower than nowadays)

Robert

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Ed Finnell]

 
In a message dated 9/20/2006 8:04:36 P.M. Central Standard Time,  
[EMAIL PROTECTED] writes:

That is  standard SDSF. The actual command is &x, where x is the  refresh
interval. I suspect shift F7 simply maps to PF19, and if you look  at the
definition for that key you will probably see an &x  command.  



>>
FYI:Can set a minimum value in ISFPARMS like 5  maybe

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Dean Montevago]

cool !! thanks.

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of Buckley, Michael J
Sent: Wednesday, September 20, 2006 9:04 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SDSF Question


That is standard SDSF. The actual command is &x, where x is the refresh
interval. I suspect shift F7 simply maps to PF19, and if you look at the
definition for that key you will probably see an &x command.  

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Dean Montevago
Sent: Thursday, 21 September 2006 10:28 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF Question

Hi,

I'm at a DR test right now and one of the operators showed me this
command in SDSF. You hit SHIFT and PF7 and an ampersand appears on the
command you type in a time interval (in seconds) and a message appears
on the command:  AUTO UPDATE (with the time interval you selected)
. This allows you to see a job transition through it's steps without
having to hit enter. The operator told me he's used this in other shops.
What is this ? Where is this ? 

TIA
Dean 

Dean Montevago
Sr. Systems Specialist
Visiting Nurse Service of New York
(212) 609 - 5596
[EMAIL PROTECTED]

--
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Buckley, Michael J]

That is standard SDSF. The actual command is &x, where x is the refresh
interval. I suspect shift F7 simply maps to PF19, and if you look at the
definition for that key you will probably see an &x command.  

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Dean Montevago
Sent: Thursday, 21 September 2006 10:28 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF Question

Hi,

I'm at a DR test right now and one of the operators showed me this
command in SDSF. You hit SHIFT and PF7 and an ampersand appears on the
command you type in a time interval (in seconds) and a message appears
on the command:  AUTO UPDATE (with the time interval you selected)
. This allows you to see a job transition through it's steps without
having to hit enter. The operator told me he's used this in other shops.
What is this ? Where is this ? 

TIA
Dean 

Dean Montevago
Sr. Systems Specialist
Visiting Nurse Service of New York
(212) 609 - 5596
[EMAIL PROTECTED]

--
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

SDSF Question

[Dean Montevago]

Hi,

I'm at a DR test right now and one of the operators showed me this command in 
SDSF. You hit SHIFT and PF7 and an ampersand appears on the command you type in 
a time interval (in seconds) and a message appears on the command:  AUTO 
UPDATE (with the time interval you selected) . This allows you to see a job 
transition through it's steps without having to hit enter. The operator told me 
he's used this in other shops. What is this ? Where is this ? 

TIA
Dean 

Dean Montevago
Sr. Systems Specialist
Visiting Nurse Service of New York
(212) 609 - 5596
[EMAIL PROTECTED]

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[willie bunter]

Thanks to all for replying.  You all have been extremely helpful.



-
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great rates 
starting at 1¢/min.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[willie bunter]

Thanks Kirk, it works.  I just couldn't remember the XC portion.  It's the age 
!!!

Kirk Talman <[EMAIL PROTECTED]> wrote:  This is one of the very clever SDSF 
line commands. It allows you to 
combine multiple line items in one stream. XD (for file output) or XS 
(for spool output) on the first line, XC on the last line, and just X on 
middles lines, if any. The PF1 HELP indicates there is new option XF to 
specify a DDNAME instead of a DSNAME.

The only limitation is that the output file has the A RECFM attribute even 
if the spool entry was made with the M RECFM attribute. Conversion from 
one to another is an interesting programming exercise.

IBM Mainframe Discussion List wrote on 04/27/2006 
11:03:50 AM:

> Try "XDC" instead of "XD" - XDC closes the dataset after it prints to 
it.

> -Original Message-
> willie bunter
> April 27, 2006 11:03 AM

> Good Day,

> I remember that I was able to perform the XD command which would 
> store the listing in a dataset. It creates the dataset however, 
> when I try the command again I get the message "print already open".
> To get around it I get out of SDSF and get back in and try the 
> command which works. Is there a way to bypass this problem instead of 
getting in and out of SDSF?



-
The information contained in this communication (including any
attachments hereto) is confidential and is intended solely for the
personal and confidential use of the individual or entity to whom
it is addressed. The information may also constitute a legally
privileged confidential communication. If the reader of this
message is not the intended recipient or an agent responsible for
delivering it to the intended recipient, you are hereby notified
that you have received this communication in error and that any
review, dissemination, copying, or unauthorized use of this
information, or the taking of any action in reliance on the
contents of this information is strictly prohibited. If you have
received this communication in error, please notify us immediately
by e-mail, and delete the original message. Thank you

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html



-
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great rates 
starting at 1¢/min.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Kirk Talman]

This is one of the very clever SDSF line commands.  It allows you to 
combine multiple line items in one stream.  XD (for file output) or XS 
(for spool output) on the first line, XC on the last line, and just X on 
middles lines, if any.  The PF1 HELP indicates there is new option XF to 
specify a DDNAME instead of a DSNAME.

The only limitation is that the output file has the A RECFM attribute even 
if the spool entry was made with the M RECFM attribute.  Conversion from 
one to another is an interesting programming exercise.

IBM Mainframe Discussion List  wrote on 04/27/2006 
11:03:50 AM:

> Try "XDC" instead of "XD" - XDC closes the dataset after it prints to 
it.

> -Original Message-
> willie bunter
> April 27, 2006 11:03 AM

> Good Day,

> I remember that I was able to perform the XD command which would 
> store the listing in a dataset.  It creates the dataset however, 
> when I try the command again I get the message "print already open".
> To get around it I get out of SDSF and get back in and try the 
> command which works.  Is there a way to bypass this problem instead of 
getting in and out of SDSF?



-
The information contained in this communication (including any
attachments hereto) is confidential and is intended solely for the
personal and confidential use of the individual or entity to whom
it is addressed.  The information may also constitute a legally
privileged confidential communication.  If the reader of this
message is not the intended recipient or an agent responsible for
delivering it to the intended recipient, you are hereby notified
that you have received this communication in error and that any
review, dissemination, copying, or unauthorized use of this
information, or the taking of any action in reliance on the
contents of this information is strictly prohibited.  If you have
received this communication in error, please notify us immediately
by e-mail, and delete the original message.  Thank you

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Mohamed Imam]

Yes, James is right.
Mohammed.



From: James Robinson
Sent: Thu 4/27/2006 11:03 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SDSF Question


Try "XDC" instead of "XD" - XDC closes the dataset after it prints to it.

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of willie bunter
Sent: Thursday, April 27, 2006 11:03 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF Question


Good Day,
   
  I remember that I was able to perform the XD command which would store the 
listing in a dataset.  It creates the dataset however, when I try the command 
again I get the message "print already open".  To get around it I get out of 
SDSF and get back in and try the command which works.  Is there a way to bypass 
this problem instead of getting in and out of SDSF?
   
  Thanks


-
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Mohamed Imam]

I used to get this problem, I remember sometimes back. There is a following 
parameter with command XD which release the file in order for you to not have 
this problem.

Mohammed A Imam
County of Cumberland, NC
(910) 678-7680.



From: willie bunter
Sent: Thu 4/27/2006 11:02 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF Question


Good Day,
   
  I remember that I was able to perform the XD command which would store the 
listing in a dataset.  It creates the dataset however, when I try the command 
again I get the message "print already open".  To get around it I get out of 
SDSF and get back in and try the command which works.  Is there a way to bypass 
this problem instead of getting in and out of SDSF?
   
  Thanks


-
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Chase, John]

> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of willie bunter
> 
> Good Day,
>
>   I remember that I was able to perform the XD command which 
> would store the listing in a dataset.  It creates the dataset 
> however, when I try the command again I get the message 
> "print already open".  To get around it I get out of SDSF and 
> get back in and try the command which works.  Is there a way 
> to bypass this problem instead of getting in and out of SDSF?

XDC line command. 

-jc-

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Ed Finnell]

 
In a message dated 4/27/2006 10:02:57 A.M. Central Standard Time,  
[EMAIL PROTECTED] writes:

"print  already open".  To get around it I get out of SDSF and get back in 
and  try the command which works.  Is there a way to bypass this problem  
instead of getting in and out of SDSF?



>>
The ol' timey way was===>print odsn my.output.listing new
followed by ===>print 1 100(or whatever you were  interesed in
followed by ===>print close
 
So looks like what XD does is the first two but not the close. Exiting SDSF  
does the CLOSE. So you should be able to do the print close and stay in  SDSF.
 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[Jerry Durbin]

On the command line "print close" while in SDSF.
Thanks for the "XD" command - I've always been using the commands for
the same thing
"Print odsn saveit.out.pds(xxx)"
"Print"
"Print close"
Cheers!
JD


-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of willie bunter
Sent: Thursday, April 27, 2006 9:03 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF Question

Good Day,
   
  I remember that I was able to perform the XD command which would store
the listing in a dataset.  It creates the dataset however, when I try
the command again I get the message "print already open".  To get around
it I get out of SDSF and get back in and try the command which works.
Is there a way to bypass this problem instead of getting in and out of
SDSF?
   
  Thanks


-
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low
rates.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: SDSF Question

[James Robinson]

Try "XDC" instead of "XD" - XDC closes the dataset after it prints to it.

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of willie bunter
Sent: Thursday, April 27, 2006 11:03 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF Question


Good Day,
   
  I remember that I was able to perform the XD command which would store the 
listing in a dataset.  It creates the dataset however, when I try the command 
again I get the message "print already open".  To get around it I get out of 
SDSF and get back in and try the command which works.  Is there a way to bypass 
this problem instead of getting in and out of SDSF?
   
  Thanks


-
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

SDSF Question

[willie bunter]

Good Day,
   
  I remember that I was able to perform the XD command which would store the 
listing in a dataset.  It creates the dataset however, when I try the command 
again I get the message "print already open".  To get around it I get out of 
SDSF and get back in and try the command which works.  Is there a way to bypass 
this problem instead of getting in and out of SDSF?
   
  Thanks


-
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: OK... dumb SDSF question

[Mike Liberatore]

yes it does.

>From: "Shmuel Metz (Seymour J.)" <[EMAIL PROTECTED]>
>Date: Sun Feb 26 09:27:21 CST 2006
>To: IBM-MAIN@BAMA.UA.EDU
>Subject: Re: OK... dumb SDSF question

>In
><[EMAIL PROTECTED]>,
>on 02/24/2006
>   at 09:07 AM, "Rugen, Len" <[EMAIL PROTECTED]> said:
>
>>In IOF, I can "edit" a job on the output queue to get the JCL that
>>was submitted and resubmit it even making minor changes.  Is there an
>>equivalent function in SDSF?
>
>SJ?
> 
>-- 
> Shmuel (Seymour J.) Metz, SysProg and JOAT
> ISO position; see <http://patriot.net/~shmuel/resume/brief.html> 
>We don't care. We don't have to care, we're Congress.
>(S877: The Shut up and Eat Your spam act of 2003)
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
>Search the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: OK... dumb SDSF question

[Shmuel Metz (Seymour J.)]

In
<[EMAIL PROTECTED]>,
on 02/24/2006
   at 09:07 AM, "Rugen, Len" <[EMAIL PROTECTED]> said:

>In IOF, I can "edit" a job on the output queue to get the JCL that
>was submitted and resubmit it even making minor changes.  Is there an
>equivalent function in SDSF?

SJ?
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: OK... dumb SDSF question

[Fletcher, Kevin]

Len,

I think you can do an SJ next to the job to get the JCL for
edit/resubmission.

Thanks,
 
Fletch 
 
 


-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Rugen, Len
Sent: Friday, February 24, 2006 10:08 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: OK... dumb SDSF question


Be gentle  I use IOF all the time, but on my freshly installed z/OS
1.7 system, all I have is SDSF.  

 

In IOF, I can "edit" a job on the output queue to get the JCL that was
submitted and resubmit it even making minor changes.  Is there an
equivalent function in SDSF?  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: OK... dumb SDSF question

[Rugen, Len]

Well, SDSF help is a little perverse   

PF1 from the ST panel, then choose "Action Characters", (not Line
Commands).

I got "//" thru "CDA" with PF7 -UP but NOT PF8- Down, so I didn't see
the REST of the action characters.  CUA navigation WAS PF7/PF8, I missed
the Enter key for the next panel.

They are ALWAYS easy to find in the doc if you know their name anyway...

>>
Your PFK1 broke? SJ as line command. To view data from DD *
need ===>INPUT ON

--

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: OK... dumb SDSF question

[Ed Finnell]

 
In a message dated 2/24/2006 9:08:03 A.M. Central Standard Time,  
[EMAIL PROTECTED] writes:

In IOF,  I can "edit" a job on the output queue to get the JCL that was
submitted  and resubmit it even making minor changes.  Is there an
equivalent  function in SDSF?  



>>
Your PFK1 broke? SJ as line command. To view data from DD *
need ===>INPUT ON

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: OK... dumb SDSF question

[Burrell, C. Todd]

You can put SJ beside the job and edit the JCL.   


C. Todd Burrell 
Senior z/OS Systems Programmer
ITSO 
(404) 498-3299
(404) 723-2017 (cell)

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Rugen, Len
Sent: Friday, February 24, 2006 10:08 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: OK... dumb SDSF question

Be gentle  I use IOF all the time, but on my freshly installed z/OS
1.7 system, all I have is SDSF.  

 

In IOF, I can "edit" a job on the output queue to get the JCL that was
submitted and resubmit it even making minor changes.  Is there an
equivalent function in SDSF?  


--
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: OK... dumb SDSF question

[David Petersen]

Use SJ to EDIT the JCL from the hold queu in SDSF.. 


Rugen, Len wrote:


Be gentle  I use IOF all the time, but on my freshly installed z/OS
1.7 system, all I have is SDSF.  




In IOF, I can "edit" a job on the output queue to get the JCL that was
submitted and resubmit it even making minor changes.  Is there an
equivalent function in SDSF?  



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
 



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: OK... dumb SDSF question

[Gary DiPillo]

Try SE as the line command.



On Fri, 24 Feb 2006 09:07:40 -0600, Rugen, Len wrote:

>Be gentle  I use IOF all the time, but on my freshly installed z/OS
>1.7 system, all I have is SDSF.  
>
> 
>
>In IOF, I can "edit" a job on the output queue to get the JCL that was
>submitted and resubmit it even making minor changes.  Is there an
>equivalent function in SDSF?  
>
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
>Search the archives at http://bama.ua.edu/archives/ibm-main.html
>

Axios Products, Inc.
[EMAIL PROTECTED]
631-864-3666 x133

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: OK... dumb SDSF question

[Richards.Bob]

Type *SE* next to the output. SJ for JCL.. Press PF1 for more options.

Bob Richards
VP, Enterprise Technologist
Enterprise Technology Infrastructure
SunTrust Banks, Inc.
(404) 575-2798 

Seeing beyond money (sm)

 -Original Message-
From:   IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]  On Behalf Of 
Rugen, Len
Sent:   Friday, February 24, 2006 10:08 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject:OK... dumb SDSF question

Be gentle  I use IOF all the time, but on my freshly installed z/OS
1.7 system, all I have is SDSF.  

 

In IOF, I can "edit" a job on the output queue to get the JCL that was
submitted and resubmit it even making minor changes.  Is there an
equivalent function in SDSF?  


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html 
  
  
  
LEGAL DISCLAIMER 
The information transmitted is intended solely for the individual or entity to 
which it is addressed and may contain confidential and/or privileged material. 
Any review, retransmission, dissemination or other use of or taking action in 
reliance upon this information by persons or entities other than the intended 
recipient is prohibited. If you have received this email in error please 
contact the sender and delete the material from any computer. 
  
Seeing Beyond Money is a service mark of SunTrust Banks, Inc. 
[ST:XCL] 
 
 
 
 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html