Discussion:
WLM?
(too old to reply)
Adams, Anne , DTI
2018-05-03 17:22:30 UTC
Permalink
Question for any WLM/performance geniuses,

Our Inforprint processes suffer when the system gets slow and therefore print slows. The Infoprint manual suggests changing the WLM Service Class for these processes thusly:

* Service Class OMVSDMN - OMVS Print Daemons
Base goal:
CPU Critical = NO I/O Priority Group = NORMAL

# Duration Imp Goal description
- --------- - ----------------------------------------
1 200 3 80% complete within 00:00:00.500
2 600 4 60% complete within 00:00:01.000
3 5 Execution velocity of 40

It's that last period that has us confused. It appears that the first two periods are never attempted and everything falls into the third one (which is not what we want, we want the first one). Should the third one be more like the first two?

Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500

We support the mainframe, it just works.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Gerhard Adam
2018-05-03 18:19:43 UTC
Permalink
The first two periods are ALWAYS used, but the duration limits how long the
work stays there before it transitions into the next period.

So, if most of our work is in period 3, it's because it has exceeded the 800
SU's that have been designated in the previous periods.

Adam

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On
Behalf Of Adams, Anne (DTI)
Sent: Thursday, May 3, 2018 10:24 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: WLM?

Question for any WLM/performance geniuses,

Our Inforprint processes suffer when the system gets slow and therefore
print slows. The Infoprint manual suggests changing the WLM Service Class
for these processes thusly:

* Service Class OMVSDMN - OMVS Print Daemons

Base goal:
CPU Critical = NO I/O Priority Group = NORMAL

# Duration Imp Goal description
- --------- - ----------------------------------------
1 200 3 80% complete within 00:00:00.500
2 600 4 60% complete within 00:00:01.000
3 5 Execution velocity of 40

It's that last period that has us confused. It appears that the first two
periods are never attempted and everything falls into the third one (which
is not what we want, we want the first one). Should the third one be more
like the first two?

Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500

We support the mainframe, it just works.

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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Adams, Anne , DTI
2018-05-03 18:33:36 UTC
Permalink
I understand the words in your response but I still don't understand. How is it possible that it takes over 800 SUs to respond to and Infoprint daemon? What am I missing here?

Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500

We support the mainframe, it just works.



-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Gerhard Adam
Sent: Thursday, May 03, 2018 2:20 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: WLM?

The first two periods are ALWAYS used, but the duration limits how long the work stays there before it transitions into the next period.

So, if most of our work is in period 3, it's because it has exceeded the 800 SU's that have been designated in the previous periods.

Adam

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Adams, Anne (DTI)
Sent: Thursday, May 3, 2018 10:24 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: WLM?

Question for any WLM/performance geniuses,

Our Inforprint processes suffer when the system gets slow and therefore print slows. The Infoprint manual suggests changing the WLM Service Class for these processes thusly:

* Service Class OMVSDMN - OMVS Print Daemons

Base goal:
CPU Critical = NO I/O Priority Group = NORMAL

# Duration Imp Goal description
- --------- - ----------------------------------------
1 200 3 80% complete within 00:00:00.500
2 600 4 60% complete within 00:00:01.000
3 5 Execution velocity of 40

It's that last period that has us confused. It appears that the first two periods are never attempted and everything falls into the third one (which is not what we want, we want the first one). Should the third one be more like the first two?

Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500

We support the mainframe, it just works.

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

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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jackson, Rob
2018-05-03 18:56:25 UTC
Permalink
On our tiny mainframe 800 SUs is still only .03 CPU seconds, which is not insignificant, but is really not that much CPU time. 800 SUs is just not that much CPU.

First Tennessee Bank
Mainframe Technical Support

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Adams, Anne (DTI)
Sent: Thursday, May 03, 2018 2:35 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: WLM?

[External Email]

I understand the words in your response but I still don't understand. How is it possible that it takes over 800 SUs to respond to and Infoprint daemon? What am I missing here?

Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500

We support the mainframe, it just works.



-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Gerhard Adam
Sent: Thursday, May 03, 2018 2:20 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: WLM?

The first two periods are ALWAYS used, but the duration limits how long the work stays there before it transitions into the next period.

So, if most of our work is in period 3, it's because it has exceeded the 800 SU's that have been designated in the previous periods.

Adam

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Adams, Anne (DTI)
Sent: Thursday, May 3, 2018 10:24 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: WLM?

Question for any WLM/performance geniuses,

Our Inforprint processes suffer when the system gets slow and therefore print slows. The Infoprint manual suggests changing the WLM Service Class for these processes thusly:

* Service Class OMVSDMN - OMVS Print Daemons

Base goal:
CPU Critical = NO I/O Priority Group = NORMAL

# Duration Imp Goal description
- --------- - ----------------------------------------
1 200 3 80% complete within 00:00:00.500
2 600 4 60% complete within 00:00:01.000
3 5 Execution velocity of 40

It's that last period that has us confused. It appears that the first two periods are never attempted and everything falls into the third one (which is not what we want, we want the first one). Should the third one be more like the first two?

Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500

We support the mainframe, it just works.

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

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

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

Confidentiality notice:
This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Adams, Anne , DTI
2018-05-03 19:13:23 UTC
Permalink
Omg ... my bad. I get it now. I'll just go over and stand by the truck. Thanks.

Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500

We support the mainframe, it just works.



-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Jackson, Rob
Sent: Thursday, May 03, 2018 2:58 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: WLM?

On our tiny mainframe 800 SUs is still only .03 CPU seconds, which is not insignificant, but is really not that much CPU time. 800 SUs is just not that much CPU.

First Tennessee Bank
Mainframe Technical Support

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Adams, Anne (DTI)
Sent: Thursday, May 03, 2018 2:35 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: WLM?

[External Email]

I understand the words in your response but I still don't understand. How is it possible that it takes over 800 SUs to respond to and Infoprint daemon? What am I missing here?

Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500

We support the mainframe, it just works.



-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Gerhard Adam
Sent: Thursday, May 03, 2018 2:20 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: WLM?

The first two periods are ALWAYS used, but the duration limits how long the work stays there before it transitions into the next period.

So, if most of our work is in period 3, it's because it has exceeded the 800 SU's that have been designated in the previous periods.

Adam

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Adams, Anne (DTI)
Sent: Thursday, May 3, 2018 10:24 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: WLM?

Question for any WLM/performance geniuses,

Our Inforprint processes suffer when the system gets slow and therefore print slows. The Infoprint manual suggests changing the WLM Service Class for these processes thusly:

* Service Class OMVSDMN - OMVS Print Daemons

Base goal:
CPU Critical = NO I/O Priority Group = NORMAL

# Duration Imp Goal description
- --------- - ----------------------------------------
1 200 3 80% complete within 00:00:00.500
2 600 4 60% complete within 00:00:01.000
3 5 Execution velocity of 40

It's that last period that has us confused. It appears that the first two periods are never attempted and everything falls into the third one (which is not what we want, we want the first one). Should the third one be more like the first two?

Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500

We support the mainframe, it just works.

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

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

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

Confidentiality notice:
This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer.

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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
David Betten
2018-05-03 19:26:14 UTC
Permalink
I would suggest looking at an RMF workload activity report to see what the
workload is doing now rather than arbitrarily changing period durations and
goals. The workload activity report can tell you the average response time
and transactions rates, along with the service units and velocity as it's
performing now. Based on that, you should then be able to set some
reasonable period durations and goals.


Have a nice day,
Dave Betten
z/OS Performance Specialist
Cloud and Systems Performance
IBM Corporation
email: ***@us.ibm.com
1-720-396-3882
Date: 05/03/2018 03:15 PM
Subject: Re: WLM?
Omg ... my bad. I get it now. I'll just go over and stand by the truck. Thanks.
Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500
We support the mainframe, it just works.
-----Original Message-----
Sent: Thursday, May 03, 2018 2:58 PM
Subject: Re: WLM?
On our tiny mainframe 800 SUs is still only .03 CPU seconds, which
is not insignificant, but is really not that much CPU time. 800 SUs
is just not that much CPU.
First Tennessee Bank
Mainframe Technical Support
-----Original Message-----
Behalf Of Adams, Anne (DTI)
Sent: Thursday, May 03, 2018 2:35 PM
Subject: Re: WLM?
[External Email]
I understand the words in your response but I still don't
understand. How is it possible that it takes over 800 SUs to respond
to and Infoprint daemon? What am I missing here?
Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500
We support the mainframe, it just works.
-----Original Message-----
Sent: Thursday, May 03, 2018 2:20 PM
Subject: Re: WLM?
The first two periods are ALWAYS used, but the duration limits how
long the work stays there before it transitions into the next period.
So, if most of our work is in period 3, it's because it has exceeded
the 800 SU's that have been designated in the previous periods.
Adam
-----Original Message-----
] On Behalf Of Adams, Anne (DTI)
Sent: Thursday, May 3, 2018 10:24 AM
Subject: WLM?
Question for any WLM/performance geniuses,
Our Inforprint processes suffer when the system gets slow and
therefore print slows. The Infoprint manual suggests changing the
* Service Class OMVSDMN - OMVS Print Daemons
CPU Critical = NO I/O Priority Group = NORMAL
# Duration Imp Goal description
- --------- - ----------------------------------------
1 200 3 80% complete within 00:00:00.500
2 600 4 60% complete within 00:00:01.000
3 5 Execution velocity of 40
It's that last period that has us confused. It appears that the
first two periods are never attempted and everything falls into the
third one (which is not what we want, we want the first one). Should
the third one be more like the first two?
Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500
We support the mainframe, it just works.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
FIRST TENNESSEE
This e-mail message, including any attachments, may contain legally
privileged and/or confidential information. If you are not the
intended recipient(s), or the employee or agent responsible for
delivery of this message to the intended recipient(s), you are
hereby notified that any dissemination, distribution, or copying of
this e-mail message is strictly prohibited. If you have received
this message in error, please immediately notify the sender and
delete this e-mail message from your computer.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Gerhard Adam
2018-05-04 00:21:00 UTC
Permalink
Bear in mind that regardless of the goals (in other words you don't know that a velocity of 40% won't give you a response time of .5 seconds).

The essential metric is the importance level. In period 3, you are essentially saying that when your system gets busy, Infoprint simply isn't that important to help meet its goals. The change from Importance 3 to Importance 5 shifts the degree to which WLM will help the service class period in meetings its goals.

Adam

Sent from my iPhone
Post by David Betten
I would suggest looking at an RMF workload activity report to see what the
workload is doing now rather than arbitrarily changing period durations and
goals. The workload activity report can tell you the average response time
and transactions rates, along with the service units and velocity as it's
performing now. Based on that, you should then be able to set some
reasonable period durations and goals.
Have a nice day,
Dave Betten
z/OS Performance Specialist
Cloud and Systems Performance
IBM Corporation
1-720-396-3882
Date: 05/03/2018 03:15 PM
Subject: Re: WLM?
Omg ... my bad. I get it now. I'll just go over and stand by the truck. Thanks.
Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500
We support the mainframe, it just works.
-----Original Message-----
Sent: Thursday, May 03, 2018 2:58 PM
Subject: Re: WLM?
On our tiny mainframe 800 SUs is still only .03 CPU seconds, which
is not insignificant, but is really not that much CPU time. 800 SUs
is just not that much CPU.
First Tennessee Bank
Mainframe Technical Support
-----Original Message-----
Behalf Of Adams, Anne (DTI)
Sent: Thursday, May 03, 2018 2:35 PM
Subject: Re: WLM?
[External Email]
I understand the words in your response but I still don't
understand. How is it possible that it takes over 800 SUs to respond
to and Infoprint daemon? What am I missing here?
Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500
We support the mainframe, it just works.
-----Original Message-----
Sent: Thursday, May 03, 2018 2:20 PM
Subject: Re: WLM?
The first two periods are ALWAYS used, but the duration limits how
long the work stays there before it transitions into the next period.
So, if most of our work is in period 3, it's because it has exceeded
the 800 SU's that have been designated in the previous periods.
Adam
-----Original Message-----
] On Behalf Of Adams, Anne (DTI)
Sent: Thursday, May 3, 2018 10:24 AM
Subject: WLM?
Question for any WLM/performance geniuses,
Our Inforprint processes suffer when the system gets slow and
therefore print slows. The Infoprint manual suggests changing the
* Service Class OMVSDMN - OMVS Print Daemons
CPU Critical = NO I/O Priority Group = NORMAL
# Duration Imp Goal description
- --------- - ----------------------------------------
1 200 3 80% complete within 00:00:00.500
2 600 4 60% complete within 00:00:01.000
3 5 Execution velocity of 40
It's that last period that has us confused. It appears that the
first two periods are never attempted and everything falls into the
third one (which is not what we want, we want the first one). Should
the third one be more like the first two?
Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500
We support the mainframe, it just works.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
FIRST TENNESSEE
This e-mail message, including any attachments, may contain legally
privileged and/or confidential information. If you are not the
intended recipient(s), or the employee or agent responsible for
delivery of this message to the intended recipient(s), you are
hereby notified that any dissemination, distribution, or copying of
this e-mail message is strictly prohibited. If you have received
this message in error, please immediately notify the sender and
delete this e-mail message from your computer.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Gerhard Adam
2018-05-03 18:20:39 UTC
Permalink
BTW, the reason your Infoprint work suffers is most likely due to it having
an Importance level of 5. If you make that higher, then it should ensure
that Infoprint gets serviced by WLM to ensure its goals are being met
[regardless of the velocity or response time settings].

Adam

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On
Behalf Of Adams, Anne (DTI)
Sent: Thursday, May 3, 2018 10:24 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: WLM?

Question for any WLM/performance geniuses,

Our Inforprint processes suffer when the system gets slow and therefore
print slows. The Infoprint manual suggests changing the WLM Service Class
for these processes thusly:

* Service Class OMVSDMN - OMVS Print Daemons

Base goal:
CPU Critical = NO I/O Priority Group = NORMAL

# Duration Imp Goal description
- --------- - ----------------------------------------
1 200 3 80% complete within 00:00:00.500
2 600 4 60% complete within 00:00:01.000
3 5 Execution velocity of 40

It's that last period that has us confused. It appears that the first two
periods are never attempted and everything falls into the third one (which
is not what we want, we want the first one). Should the third one be more
like the first two?

Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500

We support the mainframe, it just works.

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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Tom Marchant
2018-05-03 18:24:59 UTC
Permalink
Post by Adams, Anne , DTI
Our Inforprint processes suffer when the system gets slow and therefore
print slows. The Infoprint manual suggests changing the WLM Service Class
* Service Class OMVSDMN - OMVS Print Daemons
CPU Critical = NO I/O Priority Group = NORMAL
# Duration Imp Goal description
- --------- - ----------------------------------------
1 200 3 80% complete within 00:00:00.500
2 600 4 60% complete within 00:00:01.000
3 5 Execution velocity of 40
200 or 800 service units isn't very much, so you drop quickly to period 3.
You might want to play with those durations, and perhaps adjust the response
time goal as well. If you increase the durations to 2000 and 6000, those
response times might not be reasonable.
--
Tom Marchant

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Horst Sinram
2018-05-04 17:17:51 UTC
Permalink
Anne,
a daemon is a long running task, like an STC. It makes very little sense to use multi period goals (with short durations) because it will eventually fall through to later periods. A single period velocity goal is the preferred goal type for a daemon.
Only if the daemon would be at risk to loop you would consider a multi period goal using a *really huge* duration value. Even in that latter case a resource group would be a better safety net.
Horst Sinram - STSM, IBM z/OS Workload and Capacity Management

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Tom Marchant
2018-05-04 18:10:09 UTC
Permalink
Post by Horst Sinram
a daemon is a long running task, like an STC.
I wondered about that, but noticed that the Infoprint manual suggests
using what Anne had described.
Post by Horst Sinram
A single period velocity goal is the preferred goal type for a daemon.
It might make sense to use SYSSTC if it is known to use few resources.
--
Tom Marchant

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