|
We have most of our lasers for JBA set up like this. Display Device Description Page 1 Device description . . . . . . . . : DEVD PRT01 Option . . . . . . . . . . . . . . : OPTION *ALL Category of device . . . . . . . . : *PRT Device class . . . . . . . . . . . : DEVCLS *LAN Device type . . . . . . . . . . . : TYPE *IPDS Device model . . . . . . . . . . . : MODEL 0 LAN attachment . . . . . . . . . . : LANATTACH *IP Advanced function printing . . . . : AFP *YES Port number . . . . . . . . . . . : PORT 5001 Online at IPL . . . . . . . . . . : ONLINE *YES Font . . . . . . . . . . . . . . . : FONT Identifier . . . . . . . . . . . : 011 Point size . . . . . . . . . . . : *NONE Form feed . . . . . . . . . . . . : FORMFEED *AUTOCUT Separator drawer . . . . . . . . . : SEPDRAWER *FILE Separator program . . . . . . . . : SEPPGM *NONE Library . . . . . . . . . . . . : Printer error message . . . . . . : PRTERRMSG *INQ Message queue . . . . . . . . . . : MSGQ *SYSOPR Current message queue . . . . . . : QSYSOPR Library . . . . . . . . . . . . : QSYS Activation timer . . . . . . . . . : ACTTMR 170 Image configuration . . . . . . . : IMGCFG *NONE Maximum pending requests . . . . . : MAXPNDRQS 6 Print while converting . . . . . . : PRTCVT *YES Form definition . . . . . . . . . : FORMDF F1C10110 Library . . . . . . . . . . . . : *LIBL Character identifier . . . . . . . : CHRID *SYSVAL Remote location . . . . . . . . . : RMTLOCNAME Name or address . . . . . . . . : xx.x.xx.xxx (IP address) User-defined object . . . . . . . : USRDFNOBJ PRT01 Library . . . . . . . . . . . . : QGPL Object type . . . . . . . . . . : *PSFCFG Data transform program . . . . . . : USRDTATFM *NONE User-defined driver program . . . : USRDRVPGM *NONE Dependent location name . . . . . : DEPLOCNAME *NONE Allocated to: Job name . . . . . . . . . . . . . : PRT01 User . . . . . . . . . . . . . . : QSPLJOB Number . . . . . . . . . . . . . : 042137 Published . . . . . . . . . . . . : *NO Publishing information . . . . . . : PUBLISHINF Support duplex . . . . . . . . . : *UNKNOWN Support color . . . . . . . . . : *UNKNOWN Pages per minute black . . . . . : *UNKNOWN Pages per minute color . . . . . : *UNKNOWN Location . . . . . . . . . . . . : *BLANK Text . . . . . . . . . . . . . . . : TEXT Computer Room Laser Printer User-defined options . . . . . . . : USRDFNOPT Device description . . . . . . . . : DEVD PRT01 Option . . . . . . . . . . . . . . : OPTION *ALL Category of device . . . . . . . . : *PRT -----------------User-defined options------------------ Lorri Wojcik AS/400 Administrator Production Tool Supply 586-755-7770 x280 -----Original Message----- From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx] On Behalf Of Kincer, Alan Sent: Monday, February 16, 2004 8:58 AM To: System 21 Users Subject: [SYSTEM21] RE: Laser Printing from System 21 I've often wondered how this was accomplished. When I arrived here I noticed that our laser printers were set up as regular writers. When I began adding others the advice I received was to set them up as remote writers. I would rather do the first since it has been tricky getting my users in the habit of adding *ALL to their WRKWTR commands and it muckys up soup a bit more as far as consistency goes. Alan -----Original Message----- From: Roy Cox [mailto:rcox@xxxxxxxxxxxxxxx] Sent: Monday, February 16, 2004 8:29 AM To: 'System 21 Users' Subject: RE: [SYSTEM21] Laser Printing from System 21 Are you talking about hooking printers up via TCP/IP through your network? You will have no problem, we have HP lasers, Konica copiers, Xerox copiers, IBM printers, and EPSON impact (dot matrix). Create the printer with the CRTOUTQ command and assign them an IP address and a connection type "*IP". You also have to pay attention to the remote printer queue parameter depending on the printer you buy and if the printer's hooked up to a print server. Xerox copiers and HP lasers can also be created as a device printer with command CRTDEVPRT. Look on IBM's website for command CRTOUTQ and CRTDEVPRT (sometimes, the printer manufacturer has documentation for this). -----Original Message----- From: Kate Healy [mailto:Kate.Healy@xxxxxxxx] Sent: Monday, February 16, 2004 3:41 AM To: 'system21@xxxxxxxxxxxx' Subject: [SYSTEM21] Laser Printing from System 21 We have had to change printers as a printer has broken down. However, we have opened a can of worms. It appears when we first implemented System 21, our only modifications were to do with printing. We could not get an appropriate skip on our new dot matrix printer, and we could solve this by playing around with the print file. However, if we had to change the printer again, we would have the same problem. We have been told that a HP or IBM laser printer would not have any of these problems. However, we are nervous of buying one now without some indication that it would work. Does anyone have the spec of a currently available HP or IBM laser printer that appears to work with System 21 without any difficult set up problems? Thanks, Kate Healy EI Electronics. -----Original Message----- From: system21-request@xxxxxxxxxxxx [mailto:system21-request@xxxxxxxxxxxx] Sent: 12 February 2004 18:01 To: system21@xxxxxxxxxxxx Subject: SYSTEM21 Digest, Vol 2, Issue 37 Send SYSTEM21 mailing list submissions to system21@xxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit http://lists.midrange.com/mailman/listinfo/system21 or, via email, send a message with subject or body 'help' to system21-request@xxxxxxxxxxxx You can reach the person managing the list at system21-owner@xxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of SYSTEM21 digest..." Today's Topics: 1. RE: [SYSTEM21] Sales orders posted into the wrong period (Michael Berman) ---------------------------------------------------------------------- message: 1 date: Thu, 12 Feb 2004 10:18:50 +1100 from: "Michael Berman" <berman@xxxxxxxxxxxxxx> subject: RE: [SYSTEM21] Sales orders posted into the wrong period Yes, The flow on effect can be very dramatic. Sometimes it may be better living with the problem for a month than spend 2-3 months cleaning up after it. I would recommend having a reconciling figure when trying to reconcile Inventory to GL and wait out the month. Adding appropriate documentation so that the auditors don't complain too much. Please remember the AR Statements will also show the original Debit and correcting Credit then the Debit again! You Customers will certainly become aware that something amiss had occurred. You may need to consider a short note to go with the statements saying that there was a System Glitch. If we were to use words from the message file for the note on the statement, would it say, "A Problem Has Occurred - contact JBA/GEAC/someone who cares". Did we mention sales analysis, or the Debtor Average Days to pay etc?? I always demanded a chocolate cake as a reward for correcting problems was caused by a User. It helped morale, especially for those people spending valuable time cleaning up afterwards. Regards Michael Berman (m) 0419 324 558 -----Original Message----- From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx]On Behalf Of Jeff Klipa Sent: Thursday, 12 February 2004 1:35 AM To: system21@xxxxxxxxxxxx Subject: RE: [SYSTEM21] Sales orders posted into the wrong period Oh the tangled web we weave... Let this be a warning to all of us out there... This could happen to anyone of us at any time. If you've ever had this particular mess to clean up then you will appreciate where Gary is coming from right now... Mike hit the nail squarely on the head... Since the period number for all SOP -> A/R invoice postings are based on the current Inventory calendar period, that means that all of Gary's Inventory movements and G/L valuations after week one of 10402 are posted to 10403...!!! Doh...!!! So INP95, INP96 and PCP01 and the explosion of files that the OSLMJ background job proliferates into (to name only a few) are 'infected' with the wrong period... Talk about a domino effect...! Assuming your using AFI the G/L will be carrying these valuations in the wrong period as well... So once you fix the A/R side as you have suggested your G/L will be thrown off again... The accountants will not be able to balance the A/R with the Inventory... Ouch, what an ugly mess...!!! I suffered a similar event in 1997 when unbeknownst to me a user had actually closed the Inventory period twice...!!! It took a while to realize the error but by then the damage was widespread throughout the database... I attempted to clean everything up but I was left with the nagging feeling that I never did find all of the files to fix... Needless to say I don't let the users populate the calendars or close the Inventory Period any more... And, even though we have successfully automated the Inventory monthend close I still always log in and check the Inventory and Sales Analysis calendars to make sure the current period is set correctly before any users are allowed to post anything... An ounce of prevention IS better than a pound of cure for sure in this case... It's a good thing we have users to blame these kinds of things on... ;8<) Have you audited your security for the Calendar Maintenance options lately...? Good luck Gary... ----Original Message Follows---- From: MLemon@xxxxxxxxxxx Reply-To: System 21 Users <system21@xxxxxxxxxxxx> To: system21@xxxxxxxxxxxx Subject: RE: [SYSTEM21] Sales orders posted into the wrong period Date: Wed, 11 Feb 2004 08:25:20 -0500 Did all of your inventory movements post to the correct period? Each invoice/credit is almost guaranteed to be accompanied by some inventory movements in GL? If you are correcting this via JE, then you may want to SQL the period in INP95/INP96. I'm certain that there are inventory reports that look at the period in these files. -----Original Message----- From: Gary Shipp [mailto:gary.shipp@xxxxxxxxx] Sent: Wednesday, February 11, 2004 5:49 AM To: SYSTEM21@xxxxxxxxxxxx Subject: [SYSTEM21] Sales orders posted into the wrong period A user at our company made an error when creating our calendar file for 2004, entering dates so that period 2 was only effectively only 1 week long and period 3 7 weeks. Several sales invoice posting sessions were performed before anyone noticed the error. As a result, we now have a few thousand invoices in period 4/3 instead of 4/2. The calendar has now been corrected, however, the accountants want the items moved into the right period. What I was intending to do is as follows; 1) Use the SL Interface to firstly credit each invoice currently in period 3, than create new invoices in period 2. We realise that new invoice numbers will be created and are happy to put up with this. 2) SQL OEP65 and OEP70 to correct the period number from 10403 to 10402. Are there any other issues that I need to consider addressing? Is simply SQL'ing OEP65 and OEP70 an acceptable solution to resolving the incorrect periods on the SOP side of things? Thanks for any help. -- ________________________ Gary Shipp (iSeries Development Project Manager) System Three Technology Ltd Tel: 01553 636792 Fax: 01553 636414 Mob: 07974 328454 URL: <www.s3t.co.uk> << <http://www.s3t.co.uk/> http://www.s3t.co.uk>> _________________________________________________________________ Create your own personal Web page with the info you use most, at My MSN. http://click.atdmt.com/AVE/go/onm00200364ave/direct/01/ _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. ------------------------------ _______________________________________________ This is the System 21 Users (SYSTEM21) digest list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. End of SYSTEM21 Digest, Vol 2, Issue 37 *************************************** _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. === [ KI (USA) Corporation - http://www.kiusa.com ] ====================================== Tel. 859.986.1420 -- Fax. 859.986.1485 This e-mail, including any attachments, contains information from KI (USA) Corporation that may be confidential or privileged. Mail is intended only for those to whom it is addressed. If you are not the intended recipient do not copy, distribute, or take any action in reliance on the contents of this message. If you have received this e-mail in error notify the sender immediately then delete or destroy all electronic and hard copies of this communication, including attachments. KI (USA) Corporation's anti-virus system checks for known viruses. However you are advised to run your own virus check before opening any attachments received. KI (USA) Corporation will not accept any liability once an e-mail and/or any attachment is received. Views expressed in the e-mail are those of the author and not necessarily those of KI (USA) Corporation. ============================================================================ _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. ------------------------------------------------------- Notice: All email sent to or from the Production Tool Supply corporate email system may be retained, monitored and/or reviewed by PTS personnel. The views expressed in this email may not necessarily reflect the views of Production Tool Supply.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
