Re: ISeries CICS

[Rebecca.Perdue@xxxxxxxxxxxxx]

Years ago I worked with a company that was going from the mainframe to 
ISeries replacing most applications with packages, but there were no 
packages available for some applications. We used ISeries CICS and it 
worked great. I don't  remember if it was VSAM or not. There can be some 
performance problems as this was not the intended environment for 
AS/400's.

Rebecca Perdue, Systems Programmer
City of Roanoke Department of Technology
215 W. Church Avenue, 4th Floor North
Roanoke, VA 24011
540/853-2942
Fax 540/853-6044



midrange-l-request@xxxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/02/2006 01:00 PM
Please respond to
midrange-l@xxxxxxxxxxxx


To
midrange-l@xxxxxxxxxxxx
cc

Subject
MIDRANGE-L Digest, Vol 5, Issue 1878






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


*** NOTE: When replying to this digest message, PLEASE remove all text 
unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

   1. Re: PDF attachment emailed from InfoPrint (darren@xxxxxxxxx)
   2. Re: PDF attachment emailed from InfoPrint (Mike Cunningham)
   3. RE: Printing to a Windows Print Server using IPP (George Kinney)
   4. Iseries CICS (ldwopt@xxxxxxx)
   5. RE: Impact of QAQQINI setting IGNORE_DERIVED_INDEX=*YES
      (Bruce Barrett)


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

message: 1
date: Mon, 2 Oct 2006 12:07:31 -0400
from: darren@xxxxxxxxx
subject: Re: PDF attachment emailed from InfoPrint

Just a guess, but the ".dat" thing sounds like a virus/spam scanner 
getting
too aggresive.  This could be at the customer's side of things.  That 
makes
troubleshooting a touchy and difficult thing to address.





 
             Pat Mersberger 
             <PMersberger@alum 
             aroll.com>                                                 To 

             Sent by:                  midrange-l@xxxxxxxxxxxx 
             midrange-l-bounce                                          cc 

             s@xxxxxxxxxxxx 
                                                                   Subject 

                                       PDF attachment emailed from 
             10/02/2006 11:45          InfoPrint 
             AM 
 
 
             Please respond to 
             Midrange Systems 
                 Technical 
                Discussion 
             <midrange-l@midra 
                 nge.com> 
 
 




Some InfoPrint email attachments are received by our customers as
filename.pdf     .dat    instead of filename.pdf   It seems this happens
more frequently when the attachment has an overlay in the print file.  One
customer can receive the file named correctly when there is no overlay,
but incorrectly when there is one.   Other customers have no problems. Any
guesses why?


Thanks,
Pat Mersberger
--
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, 02 Oct 2006 12:35:00 -0400
from: "Mike Cunningham" <MCUNNING@xxxxxxx>
subject: Re: PDF attachment emailed from InfoPrint

We send pdf attachments and have never seen this issue

> > > PMersberger@xxxxxxxxxxxxx 10/2/2006 11:45:41 AM >>>
Some InfoPrint email attachments are received by our customers as 
filename.pdf     .dat    instead of filename.pdf   It seems this
happens 
more frequently when the attachment has an overlay in the print file. 
One 
customer can receive the file named correctly when there is no overlay,

but incorrectly when there is one.   Other customers have no problems.
Any 
guesses why? 


Thanks,
Pat Mersberger