Failed 7855-10 modem

Folks --

We do EDI on our 820 with a 7855-10 modem, which is now DEAD.  IBM is
giving me a bit of the run around with respect to
maintenance/replacement etc.

I am hoping you all can help me with some alternatives.

1> Our 820 has an internal modem.  Can that modem be used for this?  My
read of the documentation suggests that it will not work, but I am not
certain of that.

2> For some reason I think we can use a "normal" PC modem for this
stuff.  We connected one, and got nowhere; I am guessing that the line
description must be configured differently.  Can anyone enlighten me?

Any other ideas?

Thanks in advance!

>>> midrange-l-request@xxxxxxxxxxxx 06/23/03 10:00AM >>>
Send MIDRANGE-L mailing list submissions to
        midrange-l@xxxxxxxxxxxx 

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midrange.com/mailman/listinfo/midrange-l 
or, via email, send a message with subject or body 'help' to
        midrange-l-request@xxxxxxxxxxxx 

You can reach the person managing the list at
        midrange-l-owner@xxxxxxxxxxxx 

When replying, please edit your Subject line so it is more specific
than "Re: Contents of MIDRANGE-L digest..."


Today's Topics:

   1. Re: HTML GOTO (Shannon O'Donnell)
   2. RE: Securing an outq (John Earl)
   3. Re: Securing an outq (Vern Hamberg)


----------------------------------------------------------------------

message: 1
date: Mon, 23 Jun 2003 10:35:38 -0500
from: "Shannon O'Donnell" <shannono@xxxxxxxxxxxxxxx>
subject: Re: HTML GOTO

Please check on Web400....I'm going to repost the question there along
with
a code sample of what I'm trying to do.  That should make it clearer
what
I'm shooting for.

Thanks!

Shannon O'Donnell


----- Original Message -----
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, June 23, 2003 10:26 AM
Subject: RE: HTML GOTO


> > From: Shannon O'Donnell
> >
> > What I want to do is throw some JavaScript onto a page, and if
certain
> > conditions are not true...I want to close the page/and/or jump
around a
> > block of HTML code (code that is NOT part of the JavaScript).
>
> This is a lot easier in a JSP.  Is this in response to an external
user
> event, or based on something you know when the server is generating
the
> code?
>
> If it's definitely required at runtime, you can probably use the
> document.write() method to output the HTML comment start tag (what is
it,
> something like "<!--") and then after the block, write out the HTML
comment
> end tag ("--!>").  Don't quote me on the tag syntax <grin>. 
Remember,
> IANAWD (I am not a web designer!).
>
> Joe
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>



------------------------------

message: 2
date: Mon, 23 Jun 2003 09:44:59 -0700
from: "John Earl" <john.earl@xxxxxxxxxxxxxxxxxx>
subject: RE: Securing an outq

Take either *JOBCTL or *SPLCTL special authority away from the user.

Please search the archives fro keywords such as *JOBCTL and OPRCTL for
several more detailed explanation.

jte

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> bounces@xxxxxxxxxxxx] On Behalf Of MWalter@xxxxxxxxxxxxxxx 
> Sent: Monday, June 23, 2003 7:52 AM
> To: midrange-l@xxxxxxxxxxxx 
> Subject: Securing an outq
> 
> Is there a way, short of running a third part application
> to secure an
> outq. I've tried giving *public *exclude authority to the
> outq, but users
> can still see the outq and its contents. Maybe an exit
> point or something.
> 
> Thanks,
> 
> Mark
> 
> Mark D. Walter
> Senior Programmer/Analyst
> CCX, Inc.
> mwalter@xxxxxxxxxx 
> http://www.ccxinc.com 
> 
> _______________________________________________
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options,
> visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/midrange-l.



------------------------------

message: 3
date: Mon, 23 Jun 2003 11:46:13 -0500
from: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
subject: Re: Securing an outq

Look in the archives for SPLCTL and JOBCTL. OUTQ security is a little 
weird. You should probably refer tot he Tips and Tools for Securing
Your 
iSeries. To quote,

>A user with *SPLCTL special authority can see any spooled file on the

>system, no matter what efforts you make to secure your output queues.

There is a section in the Security manual on Printing in the Work 
Management chapter (near page 186). Read until you understand it well.

Clearly you need to check for users with *SPLCTL special authority. 
There're reports in GO SECTOOLS that'll show this, including mismatches

between user class and special authorities. There's also a PRTQAUT
command 
that can be called from that menu.

HTH

Vern

At 10:51 AM 6/23/2003 -0400, you wrote:
>Is there a way, short of running a third part application to secure
an
>outq. I've tried giving *public *exclude authority to the outq, but
users
>can still see the outq and its contents. Maybe an exit point or
something.
>
>Thanks,
>
>Mark
>
>Mark D. Walter
>Senior Programmer/Analyst
>CCX, Inc.
>mwalter@xxxxxxxxxx 
>http://www.ccxinc.com 



------------------------------

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
or email: MIDRANGE-L-request@xxxxxxxxxxxx 
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

e------------

message

End of MIDRANGE-L Digest, Vol 2, Issue 972
******************************************
THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH 
IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL 
AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the reader of this message 
is not the intended recipient, or the employee or agent responsible for 
delivering the message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, downloading, storing or forwarding of 
this communication is prohibited.  If you have received this communication in 
error, please notify us immediately via email and delete the message from your 
computer files and/or data base.  Thank you.