Two weeks ago, I posted a question about
VM giving incorrect information about disks.
> I did:
> Q DASD DETAILS 400
> 0400 CUTYPE = 3990-E9, DEVTYPE = 3390-0C, VOLSER =, CYLS = 10017
> CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY
>-SUBSYSTEM YY Y -N N
>
On Fri, 23 Mar 2007 09:55:05 -0400, Alan Altmark <[EMAIL PROTECTED]
>
wrote:
>It is also my
>recommendation that you do not share an OSA in use by a VSWITCH,
>*especially* if it is VLAN-aware. The last thing you want is a fight
>between two VSWITCHes about whether a VLAN is in use. Yes it is, n
> Is there documentation that discusses this package from the security
> perspective? The benefits of having it in place are obvious. What I
> require is documentation that says no one can modify the configuration
> because it has not been assigned an IP address or something of that
> nature.
As
I am also trying to find any documentation that describes this issue. The
lpar that we are setting up will eventually be shared with a 2nd lpar with
a similar configuration. If I cannot share the OSA I may have a problem.
Can someone, maybe IBM, describe in more detail what can or cannot be done
> Does this include firewall routers or guest lan (or another internal
> vswitch) between these servers ? Is there any information about this
I
> can
> read about this, is this something a LAN administrator would know ?
This is typically called a "router on a stick" or "lollipop"
configuration i
On Monday, 03/26/2007 at 09:53 EST, Brian Nielsen <[EMAIL PROTECTED]>
wrote:
> On Fri, 23 Mar 2007 09:55:05 -0400, Alan Altmark
<[EMAIL PROTECTED]>
> wrote:
>
> >It is also my
> >recommendation that you do not share an OSA in use by a VSWITCH,
> >*especially* if it is VLAN-aware. The last thing
As noted by the entire universe, that is true. Our VM LPAR normally has
5 shared cpus. The normal TPF guest has no more than 3 virtual cpus. If
special functional tests are being run, a user may go higher than 5.
This requires our complicity as we have to update the directory to allow
it, and there
I am sending files via RSCS to be printed on
an LPR link, without any carriage control.
The link is defined with EXIT=LPRXONE.
The printed output (on portrait mode paper)
is only 60 lines per page.
How can I control the page size (in lines) of
an LPR link? I would like to increase it
conside
Hi Shimon,
If you are printing from CMS to a printer on RSCS (LPR or otherwise)
and the CMS file doesn't contain carriage control, isn't CMS the one
that is breaking it up into 60 line pieces? You would have to tell CMS
it has an 80 line (or whatever) printer when it formats its output.
On 3/26/
Shimon,
Would the LINECOUNT parameter for the CMS PRINT command do what you want to do?
On 3/26/07, Ron Schmiedge <[EMAIL PROTECTED]> wrote:
Hi Shimon,
If you are printing from CMS to a printer on RSCS (LPR or otherwise)
and the CMS file doesn't contain carriage control, isn't CMS the one
that
Alan Altmark wrote:
[snip of some interesting comments]
In z/VM 5.3 we announced support for IBM System z9 IEEE 802.1ad Link
Aggregation ("channel bonding", "etherchannel"), providing additional
bandwidth with each OSA you add to the "aggregation group". In this
configuration, the OSAs ar
I recently converted our IODF file via z/os to V5 format. Z/VM has not
been IPL'd since the change. Is there any reason I should be concerned
about this?
Anne D. Crabtree
System Programmer
WV Dept of Administration - OT
304-558-5914 ext 8885
Fax 304-558-1351
Anne,
We use z/OS 1.8 in one LPAR to create our IOCDS/IODF files. We also have two
LPARs running z/VM (5.1 and 5.2). The z/VM LPARs have no problem coexisting
with the z/OS produced configuration files. Of note, the z/VM LPARs seldom have
their configurations changed. But, bottom line, there ar
I appreciate the elaboration and its relevance to link aggregation. My
next question would be how to move toward non-shared OSAs and maintain no
n-
VLAN-aware guests connected to multiple VLANs through the OSA. The two
seem to be incompatible. Either the guests need to become VLAN-aware to
On Monday, 03/26/2007 at 10:53 AST, David Boyes <[EMAIL PROTECTED]>
wrote:
> As far as I know, no one has conducted a formal evaluation of the SSL
> Enabler appliance system yet, and I don't remember any explicit
> commentary in the IBM security reviews on SSLSERV (but my memory is not
> what it u
On Monday, 03/26/2007 at 02:00 EST, Brian Nielsen <[EMAIL PROTECTED]>
wrote:
> I appreciate the elaboration and its relevance to link aggregation. My
> next question would be how to move toward non-shared OSAs and maintain
non-
> VLAN-aware guests connected to multiple VLANs through the OSA. Th
> If you are printing from CMS to a printer on RSCS
But I am not. My output is being generated on VSE
and going via NJE to RSCS to be printed, using a
"DEST=" parameter on the LST card.
The printing itself is being done with NO page size control
in the application, just keep spewing out the line
>> If you are printing from CMS to a printer on RSCS
>
>But I am not. My output is being generated on VSE
>and going via NJE to RSCS to be printed, using a
>"DEST=" parameter on the LST card.
>
>The printing itself is being done with NO page size control
>in the application, just keep spewing out t
> >
> >The printing itself is being done with NO page size control
> >in the application, just keep spewing out the lines till it's done.
>
> You need to define a PCL command (via the link PREFIX string) to tell
> the printer how many lines/page for the print output. Remember to
> use the suffix
Hi Shimon,
You've tried using
// STDOPT LINES=nn
in your job to change the default number of lines on the page for your job?
On 3/26/07, Shimon Lebowitz <[EMAIL PROTECTED]> wrote:
> >
> >The printing itself is being done with NO page size control
> >in the application, just keep spewing out t
From what's been written, I presume that the carriage control that
VSE uses would be preserved if it existed. Using // STDOPT LINES=
is a way to influence VSE's production of carriage control
characters. However, printouts can be produced in VSE in two
different ways - via SYSLST (system log
>> >
>> >The printing itself is being done with NO page size control
>> >in the application, just keep spewing out the lines till it's done.
>>
>> You need to define a PCL command (via the link PREFIX string) to tell
>> the printer how many lines/page for the print output. Remember to
>> use the s
22 matches
Mail list logo
