× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: System/36 Procedures on AS/400
  • From: MacWheel99@xxxxxxx
  • Date: Mon, 19 Jun 2000 17:09:06 EDT

Where AS/400 output goes is a complicated mixture of user settings, work 
station settings, software settings, and whether the printer really is still 
called P8.  Be sure your configuration is setup so that if it loses 
addresses, which periodically happens to us like when someone is 
disconnecting, reconnecting ... the auto config will create P8 not PRT09 or 
the logical address.

Our user settings for what printer to go to has *WRKSTN which means that 
instead of all reports for a user going to a particular printer irrespective 
of what work station they are using in whatever location in a distant city, 
it goes from where the rules are for where they physically are located for 
this session.  Our software also has some data areas so this can be further 
tuned by software environment - same user - same work station - different 
printer for test environment vs. live production work.

The Job Description is associated with the user's sign on session from a 
particular work station.  In some cases, we do not want the output going to 
the standard location for a work station, so we use the CL over-ride printer 
statement, before the actual program is executed, to say that it should go to 
some other printer, but more often it is a case of on-hold, or save after 
printing, or extra copies.

>  From:    keith.nolan@dubport.ccs.ie
>  
>  Hi all,
>  
>   We have recently migrated from a system/36 to an AS/400 and we have 
brought 
> all our procedures over from the 36.  I have a Query about setting the 
> printer in the OCL Procedure.  When we try to use the same procedures in 
the 
> AS/400 the printouts do not get routed to the right printers...  An example 
> of this is ...
>  
>   //****
>   // LOAD MILESP                             
>   // FILE NAME-MILES,LABEL-P.MILES,DISP-SHR  
>   // PRINTER NAME-PRINT1,DEVICE-L2,PRIORITY-0
>   // PRINTER NAME-PRINT2,DEVICE-P8           
>   // RUN 
>   //*****
>  
>   When this procedure is run both of the printouts go to the printer in the 
> users Job Description and they are not re-routed????  We have mapped our 
> printer names on the AS/400 to printer names in the 36 environment but this 
> procedure still doesn't work....
>  
>  TIA
>  
>  Keith                              


Al Macintyre  ©¿©
http://www.cen-elec.com MIS Manager Programmer & Computer Janitor

Y2K is not the end of my universe, but a re-boot of that old Chinese curse.
This message was written and delivered using 100% post-consumer (recycled) 
data bits
The road to success is always under construction.
Accept that some days you are the pigeon and some days the statue.
Murphy's Mom brought wrong baby home from hospital so it should be Kelly's 
Law.
If consistency is the hobgoblin of little minds, only geniuses work here.
When you want it cheap - you get what you paid for.
When in doubt, read the manual, assuming you can find the right one.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.