uniWIKI - User contributions [en]

Information Systems:RF Batch Problems

2015-10-22T22:12:04Z

172.30.20.117:

* [[Delete RF Batch]]
* [[RF Gun is Hung]]

Information Systems:Delete RF Batch

2015-10-22T19:30:01Z

172.30.20.117:

If an RF user cannot process a batch, or it gets stuck, they process as much of it as they can, then get IT to delete the batch. Note that history will be lost, as it does not go into the log files.

Use [[Utilities#DFU|DFU]] to delete the batch from these files –

RF1RFI (RF instructions) -- delete the applicable RF transactions (there will probably be two – one for the source and one for the destination).

RFBRFC (RF batches) -- delete the applicable RF batch.

RFBRID (RF instruction details) -- delete the applicable transaction.

WORK WITH DATA IN A FILE Mode . . . . : CHANGE
Format . . . . : RFI File . . . . : RF1RFI

Whse: MAI
Batch number: 5802034
Seq ovr rde: ____
Seq ins typ: _
Seq typ ovr: ____
Seq ovr rde: __
Seq put seq: __________
Seq for zone: __
Sequence location ID: ________
Sequence for item: ___________________________________
Sequence for batch: ____________
Instruction number: __________________

F3=Exit F5=Refresh F6=Select format
F9=Insert F10=Entry F11=Change

Key in the warehouse (must be in upper case), and the batch number (must be right adjusted in the field), and press enter. As only a partial key has been entered (which means values were not keyed for every field on the screen), you will see ‘Record not found in file RF1RFI in library UP1480BFVA’. But you are now positioned to the correct place in the file, so press page down to see the next record.

WORK WITH DATA IN A FILE Mode . . . . : CHANGE
Format . . . . : RFI File . . . . : RF1RFI

Whse: MAI
Batch number: 5802034
Seq ovr rde: ____
Seq ins typ: 1
Seq typ ovr: ____
Seq ovr rde: __
Seq put seq: __________
Seq for zone: H1
Sequence location ID: L437
Sequence for item: 02337277
Sequence for batch: _______________
Instruction number: 32673745
Ins typ: 1
Instruction status: 40
Pck put typ: 7
Pick instruction number: _________________
Item: 02337277

F3=Exit F5=Refresh F6=Select format
F9=Insert F10=Entry F11=Change

Press F23 (uppershift F11) twice to delete the record. Press page down to see the next record. If it is for the same batch, delete it too. Continue until the batch number changes.

Repeat the same process for RFBRFC (RF batches), and RFBRID (RF instruction details).

Information Systems:Delete RF Batch

2015-10-22T19:29:47Z

172.30.20.117: Created page with "If an RF user cannot process a batch, or it gets stuck, they process as much of it as they can, then get IT to delete the batch. Note that history will be lost, as it does no..."

If an RF user cannot process a batch, or it gets stuck, they process as much of it as they can, then get IT to delete the batch. Note that history will be lost, as it does not go into the log files.

Use [[Utilities#DFU\DFU]] to delete the batch from these files –

RF1RFI (RF instructions) -- delete the applicable RF transactions (there will probably be two – one for the source and one for the destination).

RFBRFC (RF batches) -- delete the applicable RF batch.

RFBRID (RF instruction details) -- delete the applicable transaction.

WORK WITH DATA IN A FILE Mode . . . . : CHANGE
Format . . . . : RFI File . . . . : RF1RFI

Whse: MAI
Batch number: 5802034
Seq ovr rde: ____
Seq ins typ: _
Seq typ ovr: ____
Seq ovr rde: __
Seq put seq: __________
Seq for zone: __
Sequence location ID: ________
Sequence for item: ___________________________________
Sequence for batch: ____________
Instruction number: __________________

F3=Exit F5=Refresh F6=Select format
F9=Insert F10=Entry F11=Change

Key in the warehouse (must be in upper case), and the batch number (must be right adjusted in the field), and press enter. As only a partial key has been entered (which means values were not keyed for every field on the screen), you will see ‘Record not found in file RF1RFI in library UP1480BFVA’. But you are now positioned to the correct place in the file, so press page down to see the next record.

WORK WITH DATA IN A FILE Mode . . . . : CHANGE
Format . . . . : RFI File . . . . : RF1RFI

Whse: MAI
Batch number: 5802034
Seq ovr rde: ____
Seq ins typ: 1
Seq typ ovr: ____
Seq ovr rde: __
Seq put seq: __________
Seq for zone: H1
Sequence location ID: L437
Sequence for item: 02337277
Sequence for batch: _______________
Instruction number: 32673745
Ins typ: 1
Instruction status: 40
Pck put typ: 7
Pick instruction number: _________________
Item: 02337277

F3=Exit F5=Refresh F6=Select format
F9=Insert F10=Entry F11=Change

Press F23 (uppershift F11) twice to delete the record. Press page down to see the next record. If it is for the same batch, delete it too. Continue until the batch number changes.

Repeat the same process for RFBRFC (RF batches), and RFBRID (RF instruction details).

Information Systems:RF Batch Problems

2015-10-22T19:26:17Z

172.30.20.117: Created page with "* Delete RF Batch"

* [[Delete RF Batch]]

Information Systems:Cannot Close Inbound Shipment-No Receiving Lines for Shipment

2015-10-22T19:25:23Z

172.30.20.117: Created page with "The receiving process is – 1 – scan the barcode of the shipment ID (which is the PO number, followed by a letter – A is first receipt, B is second, etc) 2 – scan th..."

The receiving process is –

1 – scan the barcode of the shipment ID (which is the PO number, followed by a letter – A is first receipt, B is second, etc)

2 – scan the bar code of the PO number

3 – scan all the items received, and enter each quantity

3 – close the shipment, which will apply the receipts against the PO and close the line (status 60), and make the products available to be picked (change the held flag on WHOLOP (Location occupancy) from ‘Y’ to ‘N’.

It is possible for the receiver to go back to step two for another purchase order without doing step 1 to change the shipment ID. This will combine multiple PO’s in a single shipment. The shipment ID for the second PO will not close as there will be no lines – they will close when the original shipment is closed. This won’t cause any problems; other than perhaps timing if you really want to close one PO without the other.

On the command line, key in WRKQRY and press enter.

Work with Queries

Type choices, press Enter.

Option . . . . . . 1 1=Create, 2=Change, 3=Copy, 4=Delete
5=Display, 6=Print definition
8=Run in batch, 9=Run
Query . . . . . . . Name, F4 for list
Library . . . . . qtemp Name, *LIBL, F4 for list

F3=Exit F4=Prompt F5=Refresh F12=Cancel
(C) COPYRIGHT IBM CORP. 1988

Key in option ‘1’ and library ‘QTEMP’, and press enter again.

Define the Query

Query . . . . . . : Option . . . . . : CREATE
Library . . . . : QTEMP CCSID . . . . . . : 65535

Type options, press Enter. Press F21 to select all.
1=Select

Opt Query Definition Option
1 Specify file selections
_ Define result fields
_ Select and sequence fields
1 Select records
_ Select sort fields
_ Select collating sequence
_ Specify report column formatting
_ Select report summary functions
_ Define report breaks
_ Select output type and output form
_ Specify processing options

F3=Exit F5=Report F12=Cancel
F13=Layout F18=Files F21=Select all

Key option ‘1’ for ‘Specify file selections’ and ‘select records’, and press enter.

Specify File Selections

Type choices, press Enter. Press F9 to specify an additional
file selection.

File . . . . . . . . . srolcl Name, F4 for list
Library . . . . . . UP1480BFVA Name, *LIBL, F4 for list
Member . . . . . . . . *FIRST Name, *FIRST, F4 for list
Format . . . . . . . . *FIRST Name, *FIRST, F4 for list

F3=Exit F4=Prompt F5=Report F9=Add file
F12=Cancel F13=Layout F24=More keys

Key in ‘SROLCL’ (Shipment Lines) for file and ‘UP1480BFVA’ for library, and press enter twice.

Select Records

Type comparisons, press Enter. Specify OR to start each new group.
Tests: EQ, NE, LE, GE, LT, GT, RANGE, LIST, LIKE, IS, ISNOT...

AND/OR Field Test Value (Field, Number, 'Characters', or ...)
CLORNO EQ 8178286_______________________
____ ________________ _____ ______________________________
____ ________________ _____ ______________________________
____ ________________ _____ ______________________________
____ ________________ _____ ______________________________
____ ________________ _____ ______________________________
Bottom

Field Text Len Dec
CLSHPS Shipping Status 2 0
CLSHIP Shipment ID 17
CLSHPA Shipping agent 11
CLORNO Order number 7 0
CLLINE Order line number 5 0
More...
F3=Exit F5=Report F9=Insert F11=Display names only
F12=Cancel F13=Layout F20=Reorganize F24=More keys

Key in ‘CLORNO EQ’ then the PO with the problem, and press F5.

Display Report
Report width . . . . . : 333
Position to line . . . . . Shift to column . . . . . .
Line ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+...10....+...11....+...12.
Shp Shipment ID Shipping Ord no Ord Supplier no Shpmt Item Qty
Sts agent line Line stock un

000001 60 8172890N 8178286 40 20130 500 00359489 10.0
000002 60 8172890N 8178286 260 20130 500 02107167 4.0
000003 60 8172890N 8178286 270 20130 500 02107175 5.0
000004 60 8172890N 8178286 290 20130 500 02113538 3.0
****** ******** End of report ********

Bottom
F3=Exit F12=Cancel F19=Left F20=Right F21=Split F22=Width 80

This shows that four lines for purchase order 8178286 were received under shipment 8172890N. The PO lines will be flagged as received when that shipment is closed. ‘Shp Sts’ of ‘60’ means that it has been closed.

To exit Query, press F3 until you see

Exit this Query

Type choices, press Enter.

Save definition . . . N Y=Yes, N=No

Run option . . . . . . 3 1=Run interactively
2=Run in batch
3=Do not run

For a saved definition:
Query . . . . . . . __________ Name
Library . . . . . QTEMP Name, F4 for list

Text . . . . . . . . __________________________________________________

Authority . . . . . *LIBCRTAUT *LIBCRTAUT, authorization list name,
*CHANGE, *ALL, *EXCLUDE, *USE

F4=Prompt F5=Report F12=Cancel F13=Layout
F14=Define the query

Make sure ‘Save definition’ is ‘N’ and ‘Run option’ is ‘3’, and press enter twice. It is not worthwhile to save this query as by this time you need it again, you will have forgotten where it is and what it’s called. It would be much faster to just create it again.

Information Systems:No Valid Lines for RF Receiving

2015-10-22T17:46:25Z

172.30.20.117:

When this message is received while trying to do RF receiving on a PO with open lines, it means those lines are in status 30 or higher.

PO lines go into status 30 when a reception note is printed. This starts the process for paper or green screen receiving. This is correct for returns and adjustments; but not when product is coming in the door. To do RF receiving, they must be in status 20 (printed) or 25 (confirmed).

It is not normal for an inventory PO to be in this status – somebody has done something wrong. To change the status of the line back to status 20, it has to be [[Zero Receive|zero received and back ordered]].

Information Systems:No Valid Lines for RF Receiving

2015-10-22T17:42:22Z

172.30.20.117: Created page with "When this message is received while trying to do RF receiving on a PO with open lines, it means those lines are in the wrong status. They are in status 30 (reception note has..."

When this message is received while trying to do RF receiving on a PO with open lines, it means those lines are in the wrong status. They are in status 30 (reception note has been printed, which is the first step for green screen receiving), when they should be 20 (printed) or 25 (confirmed).

It is not normal for an inventory PO to be in this status – somebody has done something wrong. To change the status of the line back to status 20, it has to be [[Receiving Problems#Zero Receive|zero received and back ordered]].

Information Systems:Zero Receive

2015-10-22T17:37:48Z

172.30.20.117: Created page with "Go to PO inquiry, and look at the line to get the reception note number. Note that this does not show in '''work with purchase orders''', only '''purchase order inquiry'''...."

Go to PO inquiry, and look at the line to get the reception note number. Note that this does not show in '''work with purchase orders''', only '''purchase order inquiry'''.

*VA/480B* Purchase order enquiry 9/10/14 14:22:43 DMR11907
Detailed order line 1
-------------------------------------------------------------------------------
Supplier.... 20409 BOWERS MEDICAL SUPPLY Order value. 145.05
Order type.. PO Regular Purchase Order Ord val CAD 145.05
Order number 8178055
-------------------------------------------------------------------------------
Line 90 Orig status. 10 Act status.. 30
Item........ 00685651
MESORB ABSORBENT PAD
Supp item cd SANC677701
Warehouse... MAI Purch unit.. EA '''Rec note. 4308432'''
Contract no. Promised dat 09/03/14 Rec line.... 1
Primary qty. 5.00 Request date 09/03/14 Backlog..... Y
Order qty... 5.00 Disp date... 09/03/14 Backlogged.. N
Received qty Arrival date 09/07/14 Prev rec qty
Approved qty Rec date.... Trpt time... 4
Prc unit qty 5.00 Price unit.. EA FOC......... N
Price....... 29.01 Price code..
Order disc.. Y Disc amount. Currency.... CAD
Discount %..
Shipment mrk BASE Notify del.. N
F6=Pre-accounting F8=Addresses F9=Header

Then go to ‘Supply chain processes’ / ‘Warehouse’ / ‘Reception tasks’ / ‘Confirm purchase order reception notes’.

*VA/480B* Reception note confirmation 9/10/14 14:23:49 DMR53001
-------------------------------------------------------------------------------
'''Reception note...... 4308432'''

Reception date...... 091014

Transport note......
Actual dispatch date

Key in the reception note number and press enter.

*VA/480B* Location confirmation 9/10/14 14:24:23 WMR91001
Put-Away
-------------------------------------------------------------------------------
List number 4308432 Warehouse MAI
-------------------------------------------------------------------------------
Line Item Sugg. qty
Batch Disp date Zn Location PA SN +
1 00685651 5.00
090314 N2 C029

-------------------------------------------------------------------------------
Line

F1=Change batch,loc. F8=Blank; sugg. qty F9=Blank; zero F10=Order

The line(s) for that reception note will show. To do a zero receipt, press F9.

*VA/480B* Reception note confirmation 9/10/14 14:25:06 DMR53002
-------------------------------------------------------------------------------
Order number 8178055 Reception note 4308432
Supplier 20409 BOWERS MEDICAL SUPPLY Order type PO
-------------------------------------------------------------------------------
Line Item Qty ord. Qty rec. B/S B R
Order Description Disp date Unit Bin loc
1 00685651 5.00 0.00 '''Y'''
8178055 MESORB ABSORBENT PAD 090314 EA

F1=Create shipment F7=Discrete costs

Make sure that the line is set to back order, and press enter again. The effect of this is that the line will change from status 30 to 20. If you were to do this for a partial quantity instead of zero, the line would be changed to status 60, and a new line for the balance will be created, as status 30.

Information Systems:Receiving Problems

2015-10-22T17:33:05Z

172.30.20.117:

* [[No Valid Lines for RF Receiving]]
* [[No Valid Lines for RF Receiving|PO Lines at Status 30]]
* [[Cannot Close Inbound Shipment-No Receiving Lines for Shipment]]
* [[Cannot Close Inbound Shipment-Shipment in Use]]
* [[Cannot Close Inbound Shipment-Purchase Order Locked by Another User]]
* [[Inbound Shipment Closed, but P.O. Lines Still in Status 30]]
* [[Zero Receive]]

Information Systems:Receiving Problems

2015-10-22T17:32:48Z

172.30.20.117: Created page with "* []No Valid Lines for RF Receiving]] * []No Valid Lines for RF Receiving|PO Lines at Status 30]] * Cannot Close Inbound Shipment-No Receiving Lines for Shipment * Canno..."

* []No Valid Lines for RF Receiving]]
* []No Valid Lines for RF Receiving|PO Lines at Status 30]]
* [[Cannot Close Inbound Shipment-No Receiving Lines for Shipment]]
* [[Cannot Close Inbound Shipment-Shipment in Use]]
* [[Cannot Close Inbound Shipment-Purchase Order Locked by Another User]]
* [[Inbound Shipment Closed, but P.O. Lines Still in Status 30]]
* [[Zero Receive]]

Information Systems:FIN03FPMG Does Not Balance to FIN03

2015-10-22T16:54:00Z

172.30.20.117:

=FIN03KFMG Does not Balance to FIN03=

The problem is that the net earnings on FIN03 (Detail Statement of Income) and on FIN03-KPMG (KPMG Summary Income Statement) don't agree.

So far, the issue has always been the 'Out of Balance' G/L account. When an out of balance journal is forced to update, it creates a balancing record into the out of balance account, or 730200. When this transaction is added to ANOBAL, for some reason it does not set the proper keys.

Use [[Utilities#QUERY|Query]] to look at records in ANOSTK that have

KESUTA = A11
KEMK01 = 730200

Look at field KEMK14. It should be MISC for all records. If it is not, it must be changed.

Account number 730200 is set up in the chart of accounts to have a second summary identity of MISC, so why is it updated to a summary ID of blank?

Use [[Utilities#DFU|DFU]] or [[Utilities#EZVIEW|EZVIEW]] on file AN1STK to make the key fields (11 to 14) the same as the other records that match this account number (parts 1 to 6).

==Rebuild the ‘KPMG statement section’==

Only ASW administrators can do this, so sign on as FINADMIN.

On a command line in ASW, key in GO GLPER and press enter. Select the option ‘Rebuild summary identities’.

*VA/480B* G/L summary identity rebuild 5/26/15 18:25:09 FMR22201
-------------------------------------------------------------------------------
Summary identity Changed Summary identity Changed
Statement Section... N
Cost Center Group 1. N
Cost Center Group 2. N
KPMG stmt section... N

NO SUMMARY IDENTITY HAVE BEEN CHANGED

THIS JOB WILL BE CANCELLED

If this process will not run, because no changes have been made, you can force it by setting the changed flag to ‘Y’ in G/L Control File Maintenance.

Key in GO GLSET and press enter. Select the option ‘Work with G/L control file’.

Press Enter until this screen shows.

*VA/480B* G/L control file maintenance 5/26/15 18:27:42 GDMD0922
-------------------------------------------------------------------------------
Related to
account part Changed
Summary id part 1... Statement Section 1 N
Summary id part 2... Cost Center Group 1 4 N
Summary id part 3... Cost Center Group 2 4 N
Summary id part 4... KPMG stmt section 1 N

F7=Translate

Change the column ‘Changed’ to Y for the section you want to rebuild (in this case ‘KPMG stmt section’), then go back to ‘Rebuild Summary Identities’.

Check results by running the report. Go to ASW / business reporting / work with reports. Print (option 6) FIN03-KPMG for the appropriate year and period .

Information Systems:FIN03FPMG Does Not Balance to FIN03

2015-10-22T16:52:24Z

172.30.20.117:

=FIN03KFMG Does not Balance to FIN03=

The problem is that the net earnings on FIN03 (Detail Statement of Income) and on FIN03-KPMG (KPMG Summary Income Statement) don't agree.

So far, the issue has always been the 'Out of Balance' G/L account. When an out of balance journal is forced to update, it creates a balancing record into the out of balance account, or 730200. When this transaction is added to ANOBAL, for some reason it does not set the proper keys.

Use [[Utilities#QUERY|Query]] to look at records in ANOSTK that have

KESUTA = A11
KEMK01 = 730200

Look at field KEMK14. It should be MISC for all records. If it is not, it must be changed.

Account number 730200 is set up in the chart of accounts to have a second summary identity of MISC, so why is it updated to a summary ID of blank?

Use [[DFU]] or [[EZVIEW]] on file AN1STK to make the key fields (11 to 14) the same as the other records that match this account number (parts 1 to 6).

==Rebuild the ‘KPMG statement section’==

Only ASW administrators can do this, so sign on as FINADMIN.

On a command line in ASW, key in GO GLPER and press enter. Select the option ‘Rebuild summary identities’.

*VA/480B* G/L summary identity rebuild 5/26/15 18:25:09 FMR22201
-------------------------------------------------------------------------------
Summary identity Changed Summary identity Changed
Statement Section... N
Cost Center Group 1. N
Cost Center Group 2. N
KPMG stmt section... N

NO SUMMARY IDENTITY HAVE BEEN CHANGED

THIS JOB WILL BE CANCELLED

If this process will not run, because no changes have been made, you can force it by setting the changed flag to ‘Y’ in G/L Control File Maintenance.

Key in GO GLSET and press enter. Select the option ‘Work with G/L control file’.

Press Enter until this screen shows.

*VA/480B* G/L control file maintenance 5/26/15 18:27:42 GDMD0922
-------------------------------------------------------------------------------
Related to
account part Changed
Summary id part 1... Statement Section 1 N
Summary id part 2... Cost Center Group 1 4 N
Summary id part 3... Cost Center Group 2 4 N
Summary id part 4... KPMG stmt section 1 N

F7=Translate

Change the column ‘Changed’ to Y for the section you want to rebuild (in this case ‘KPMG stmt section’), then go back to ‘Rebuild Summary Identities’.

Check results by running the report. Go to ASW / business reporting / work with reports. Print (option 6) FIN03-KPMG for the appropriate year and period .

Information Systems:FIN03FPMG Does Not Balance to FIN03

2015-10-22T16:51:26Z

172.30.20.117:

=FIN03KFMG Does not Balance to FIN03=

The problem is that the net earnings on FIN03 (Detail Statement of Income) and on FIN03-KPMG (KPMG Summary Income Statement) don't agree.

So far, the issue has always been the 'Out of Balance' G/L account. When an out of balance journal is forced to update, it creates a balancing record into the out of balance account, or 730200. When this transaction is added to ANOBAL, for some reason it does not set the proper keys.

Use [[Query]] to look at records in ANOSTK that have

KESUTA = A11
KEMK01 = 730200

Look at field KEMK14. It should be MISC for all records. If it is not, it must be changed.

Account number 730200 is set up in the chart of accounts to have a second summary identity of MISC, so why is it updated to a summary ID of blank?

Use [[DFU]] or [[EZVIEW]] on file AN1STK to make the key fields (11 to 14) the same as the other records that match this account number (parts 1 to 6).

==Rebuild the ‘KPMG statement section’==

Only ASW administrators can do this, so sign on as FINADMIN.

On a command line in ASW, key in GO GLPER and press enter. Select the option ‘Rebuild summary identities’.

*VA/480B* G/L summary identity rebuild 5/26/15 18:25:09 FMR22201
-------------------------------------------------------------------------------
Summary identity Changed Summary identity Changed
Statement Section... N
Cost Center Group 1. N
Cost Center Group 2. N
KPMG stmt section... N

NO SUMMARY IDENTITY HAVE BEEN CHANGED

THIS JOB WILL BE CANCELLED

If this process will not run, because no changes have been made, you can force it by setting the changed flag to ‘Y’ in G/L Control File Maintenance.

Key in GO GLSET and press enter. Select the option ‘Work with G/L control file’.

Press Enter until this screen shows.

*VA/480B* G/L control file maintenance 5/26/15 18:27:42 GDMD0922
-------------------------------------------------------------------------------
Related to
account part Changed
Summary id part 1... Statement Section 1 N
Summary id part 2... Cost Center Group 1 4 N
Summary id part 3... Cost Center Group 2 4 N
Summary id part 4... KPMG stmt section 1 N

F7=Translate

Change the column ‘Changed’ to Y for the section you want to rebuild (in this case ‘KPMG stmt section’), then go back to ‘Rebuild Summary Identities’.

Check results by running the report. Go to ASW / business reporting / work with reports. Print (option 6) FIN03-KPMG for the appropriate year and period .

Information Systems:Infonet User Security

2015-10-22T16:30:01Z

172.30.20.117:

=User=

InfoNet uses System i user IDs and passwords to validate users. After a successful logon using the i security, InfoNet has a file that contains authority levels, access rights, and defaults. When a login fails, we do not tell the user which of the ID and password was incorrect – so someone trying to break in won’t know if they hit upon a valid user ID. After an unsuccessful signon attempt, InfoNet will add a record to the user file, which gives the date, and the number of attempts. After five failed attempts, the user ID will be disabled, and the person will have to try a different ID. So by looking at the list of users we will be able to tell if anyone has tried to break in. If someone trying to break in happens upon a valid user ID, it will be disabled after 5 invalid passwords, so no one can break in with a program that tries every possible password.

[[File:websmart-1.jpg]]

This list shows three people trying to sign on with the incorrect ID – ‘TEST’, ‘BCD’ and ‘VIVIANB’ (one was an example, one was a typo, and one was just wrong). One was tried 5 times then disabled, the other two were only tried once, then apparently the correct ID was used. We know these three ID’s were added by the login program, as the records are incomplete – no authority level. ‘TIFFANYW’ has been disabled manually; not because of 5 failed login attempts.

None of the programs are storing cookies on the user’s PC – server side cookies (called SMURFS) are used.

InfoNet and Web Orders have been made invulnerable to SQL injection attacks. This is done by looking at every selection field a user keys in, and removing all single quotes. This makes it impossible to, for example, search for BOB’S within a partner name; but it also makes it impossible for a malicious user to hijack the SQL statement that is constructed by the program based requests from the user.

=User Authorities=

Once a user signs on, the functions they are allowed to use, and the information they can see, is controlled by file WEBPRDD/INUSERP. This file is maintained in InfoNet / Admin / User Authorities. The user doing the maintenance must have an authority level of 8 or higher (8-administrator, 9-IT).

[[File:websmart-2.jpg]]

Each check box on this screen is a field on INUSERP (as well as each check box in 'User Defaults'). This file has 299 fields; as of October 2015, 140 are in use.

Information Systems:Infonet User Security

2015-10-22T16:03:00Z

172.30.20.117: Created page with "=User= InfoNet uses System i user IDs and passwords to validate users. After a successful logon using the i security, InfoNet has a file that contains authority levels, acce..."

Information Systems:InfoNet Security

2015-10-22T15:54:30Z

172.30.20.117: Blanked the page

Information Systems:IMS - Inbound Message System

2015-10-21T22:43:03Z

172.30.20.117:

* [[IMS Description]]
* [[EDI Control Panel]]

Information Systems:EDI Control Panel for IMS/IMP/IOP/OMS

2015-10-21T22:42:14Z

172.30.20.117: /* Start */

IMS (Inbound Mail System), IMP (Inbound Mail Parsing), IOP (Inbound Order Posting), OMS (Outbound Mail System), and EMA (Error Messages & Alerts) are controlled by subsystems and jobs that are started and ended by over night processing, and run all day long.

Work with Active Jobs BART
10/21/15 10:36:59
CPU %: 12.1 Elapsed time: 00:00:29 Active jobs: 513

Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...
Current
Opt Subsystem/Job User Type CPU % Function Status

EMASUBPRD QSYS SBS .0 DEQW
EMAIOPPRD QPGMR BCH .0 DLY-10:59:50 DLYW
IMPSUBPRD QSYS SBS .0 DEQW
IMPPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IMSSUBPRD QSYS SBS .0 DEQW
IMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IOPSUBPRD QSYS SBS .0 DEQW
IOPPOSTPRD QPGMR BCH 2.0 DLY-120 DLYW
OMSSUBPRD QSYS SBS .0 DEQW
OMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW

Parameters or command
===>
F3=Exit F5=Refresh F7=Find F10=Restart statistics
F11=Display elapsed data F12=Cancel F23=More options F24=More keys

It may be necessary to stop and/or restart them during the day - if there are errors, or to recompile programs. To do this, go to Unity / Start uniPharm Extensions / VA Company / UWD Extensions / EDI - IMS, IMP, etc / EDI Control Panel.

10/21/15 10:49:24 uniPHARM -- PRODUCTION EDRIQ100/CONTROL
EDI -- Main Control Panel PRODUCTION 1.00

Action Sub System
System Status Switch
__ IMS Inbound Mail Receiving 20 Fully Active START
__ IMP Inbound Mail Parsing 20 Fully Active START
__ IOP Inbound Order Posting 20 Fully Active START

__ OMS Outbound Mail Send 20 Fully Active START
__ EMA Alerts 20 Fully Active START

Actions
ES End Subsystem SP=Start Monitor Program
SS Start Subsystem EP=End Monitor Program
OF Switch System Activity OFF
ON Switch System Activity ON

F3=Exit F5=Refresh F8=Details F10=Active F12=Previous
F14=IOP Exc Msgs On F15=IOP Exc Msgs Off

=Stop=

Set system activity off with action OF.

End monitor program with action EP.

If necessary, End subsystem with action ES.

=Start=

If necessary, start subsystem with SS.

Set system activity on with ON.

Start monitor program with SP.

Note - program will run under the user that starts it. Best to run this under user EODJOB

Information Systems:EDI Control Panel for IMS/IMP/IOP/OMS

2015-10-21T22:41:57Z

172.30.20.117: /* Stop */

IMS (Inbound Mail System), IMP (Inbound Mail Parsing), IOP (Inbound Order Posting), OMS (Outbound Mail System), and EMA (Error Messages & Alerts) are controlled by subsystems and jobs that are started and ended by over night processing, and run all day long.

Work with Active Jobs BART
10/21/15 10:36:59
CPU %: 12.1 Elapsed time: 00:00:29 Active jobs: 513

Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...
Current
Opt Subsystem/Job User Type CPU % Function Status

EMASUBPRD QSYS SBS .0 DEQW
EMAIOPPRD QPGMR BCH .0 DLY-10:59:50 DLYW
IMPSUBPRD QSYS SBS .0 DEQW
IMPPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IMSSUBPRD QSYS SBS .0 DEQW
IMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IOPSUBPRD QSYS SBS .0 DEQW
IOPPOSTPRD QPGMR BCH 2.0 DLY-120 DLYW
OMSSUBPRD QSYS SBS .0 DEQW
OMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW

Parameters or command
===>
F3=Exit F5=Refresh F7=Find F10=Restart statistics
F11=Display elapsed data F12=Cancel F23=More options F24=More keys

It may be necessary to stop and/or restart them during the day - if there are errors, or to recompile programs. To do this, go to Unity / Start uniPharm Extensions / VA Company / UWD Extensions / EDI - IMS, IMP, etc / EDI Control Panel.

10/21/15 10:49:24 uniPHARM -- PRODUCTION EDRIQ100/CONTROL
EDI -- Main Control Panel PRODUCTION 1.00

Action Sub System
System Status Switch
__ IMS Inbound Mail Receiving 20 Fully Active START
__ IMP Inbound Mail Parsing 20 Fully Active START
__ IOP Inbound Order Posting 20 Fully Active START

__ OMS Outbound Mail Send 20 Fully Active START
__ EMA Alerts 20 Fully Active START

Actions
ES End Subsystem SP=Start Monitor Program
SS Start Subsystem EP=End Monitor Program
OF Switch System Activity OFF
ON Switch System Activity ON

F3=Exit F5=Refresh F8=Details F10=Active F12=Previous
F14=IOP Exc Msgs On F15=IOP Exc Msgs Off

=Stop=

Set system activity off with action OF.

End monitor program with action EP.

If necessary, End subsystem with action ES.

=Start=

If necessary, start subsystem with SS.
Set system activity on with ON.
Start monitor program with SP.

Note - program will run under the user that starts it. Best to run this under user EODJOB

Information Systems:EDI Control Panel for IMS/IMP/IOP/OMS

2015-10-21T22:41:42Z

172.30.20.117: /* Start */

IMS (Inbound Mail System), IMP (Inbound Mail Parsing), IOP (Inbound Order Posting), OMS (Outbound Mail System), and EMA (Error Messages & Alerts) are controlled by subsystems and jobs that are started and ended by over night processing, and run all day long.

Work with Active Jobs BART
10/21/15 10:36:59
CPU %: 12.1 Elapsed time: 00:00:29 Active jobs: 513

Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...
Current
Opt Subsystem/Job User Type CPU % Function Status

EMASUBPRD QSYS SBS .0 DEQW
EMAIOPPRD QPGMR BCH .0 DLY-10:59:50 DLYW
IMPSUBPRD QSYS SBS .0 DEQW
IMPPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IMSSUBPRD QSYS SBS .0 DEQW
IMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IOPSUBPRD QSYS SBS .0 DEQW
IOPPOSTPRD QPGMR BCH 2.0 DLY-120 DLYW
OMSSUBPRD QSYS SBS .0 DEQW
OMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW

Parameters or command
===>
F3=Exit F5=Refresh F7=Find F10=Restart statistics
F11=Display elapsed data F12=Cancel F23=More options F24=More keys

It may be necessary to stop and/or restart them during the day - if there are errors, or to recompile programs. To do this, go to Unity / Start uniPharm Extensions / VA Company / UWD Extensions / EDI - IMS, IMP, etc / EDI Control Panel.

10/21/15 10:49:24 uniPHARM -- PRODUCTION EDRIQ100/CONTROL
EDI -- Main Control Panel PRODUCTION 1.00

Action Sub System
System Status Switch
__ IMS Inbound Mail Receiving 20 Fully Active START
__ IMP Inbound Mail Parsing 20 Fully Active START
__ IOP Inbound Order Posting 20 Fully Active START

__ OMS Outbound Mail Send 20 Fully Active START
__ EMA Alerts 20 Fully Active START

Actions
ES End Subsystem SP=Start Monitor Program
SS Start Subsystem EP=End Monitor Program
OF Switch System Activity OFF
ON Switch System Activity ON

F3=Exit F5=Refresh F8=Details F10=Active F12=Previous
F14=IOP Exc Msgs On F15=IOP Exc Msgs Off

=Stop=

Set system activity off with action OF.
End monitor program with action EP.
If necessary, End subsystem with action ES.

=Start=

If necessary, start subsystem with SS.
Set system activity on with ON.
Start monitor program with SP.

Note - program will run under the user that starts it. Best to run this under user EODJOB

Information Systems:EDI Control Panel for IMS/IMP/IOP/OMS

2015-10-21T22:41:26Z

172.30.20.117:

IMS (Inbound Mail System), IMP (Inbound Mail Parsing), IOP (Inbound Order Posting), OMS (Outbound Mail System), and EMA (Error Messages & Alerts) are controlled by subsystems and jobs that are started and ended by over night processing, and run all day long.

Work with Active Jobs BART
10/21/15 10:36:59
CPU %: 12.1 Elapsed time: 00:00:29 Active jobs: 513

Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...
Current
Opt Subsystem/Job User Type CPU % Function Status

EMASUBPRD QSYS SBS .0 DEQW
EMAIOPPRD QPGMR BCH .0 DLY-10:59:50 DLYW
IMPSUBPRD QSYS SBS .0 DEQW
IMPPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IMSSUBPRD QSYS SBS .0 DEQW
IMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IOPSUBPRD QSYS SBS .0 DEQW
IOPPOSTPRD QPGMR BCH 2.0 DLY-120 DLYW
OMSSUBPRD QSYS SBS .0 DEQW
OMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW

Parameters or command
===>
F3=Exit F5=Refresh F7=Find F10=Restart statistics
F11=Display elapsed data F12=Cancel F23=More options F24=More keys

It may be necessary to stop and/or restart them during the day - if there are errors, or to recompile programs. To do this, go to Unity / Start uniPharm Extensions / VA Company / UWD Extensions / EDI - IMS, IMP, etc / EDI Control Panel.

10/21/15 10:49:24 uniPHARM -- PRODUCTION EDRIQ100/CONTROL
EDI -- Main Control Panel PRODUCTION 1.00

Action Sub System
System Status Switch
__ IMS Inbound Mail Receiving 20 Fully Active START
__ IMP Inbound Mail Parsing 20 Fully Active START
__ IOP Inbound Order Posting 20 Fully Active START

__ OMS Outbound Mail Send 20 Fully Active START
__ EMA Alerts 20 Fully Active START

Actions
ES End Subsystem SP=Start Monitor Program
SS Start Subsystem EP=End Monitor Program
OF Switch System Activity OFF
ON Switch System Activity ON

F3=Exit F5=Refresh F8=Details F10=Active F12=Previous
F14=IOP Exc Msgs On F15=IOP Exc Msgs Off

=Stop=

Set system activity off with action OF.
End monitor program with action EP.
If necessary, End subsystem with action ES.

=Start=

If necessary, start subsystem with SS.
Set system activity on with ON.
Start monitor program with SP.

Note - program will run under the user that starts it. Best to run this under user EODJOB

Information Systems:EDI Control Panel for IMS/IMP/IOP/OMS

2015-10-21T20:55:47Z

172.30.20.117: /* Stop */

IMS (Inbound Mail System), IMP (Inbound Mail Parsing), IOP (Inbound Order Posting), OMS (Outbound Mail System), and EMA (Error Messages & Alerts) are controlled by subsystems and jobs that are started and ended by over night processing, and run all day long.

Work with Active Jobs BART
10/21/15 10:36:59
CPU %: 12.1 Elapsed time: 00:00:29 Active jobs: 513

Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...
Current
Opt Subsystem/Job User Type CPU % Function Status

EMASUBPRD QSYS SBS .0 DEQW
EMAIOPPRD QPGMR BCH .0 DLY-10:59:50 DLYW
IMPSUBPRD QSYS SBS .0 DEQW
IMPPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IMSSUBPRD QSYS SBS .0 DEQW
IMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IOPSUBPRD QSYS SBS .0 DEQW
IOPPOSTPRD QPGMR BCH 2.0 DLY-120 DLYW
OMSSUBPRD QSYS SBS .0 DEQW
OMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW

Parameters or command
===>
F3=Exit F5=Refresh F7=Find F10=Restart statistics
F11=Display elapsed data F12=Cancel F23=More options F24=More keys

It may be necessary to stop and/or restart them during the day - if there are errors, or to recompile programs. To do this, go to Unity / Start uniPharm Extensions / VA Company / UWD Extensions / EDI - IMS, IMP, etc / EDI Control Panel.

10/21/15 10:49:24 uniPHARM -- PRODUCTION EDRIQ100/CONTROL
EDI -- Main Control Panel PRODUCTION 1.00

Action Sub System
System Status Switch
__ IMS Inbound Mail Receiving 20 Fully Active START
__ IMP Inbound Mail Parsing 20 Fully Active START
__ IOP Inbound Order Posting 20 Fully Active START

__ OMS Outbound Mail Send 20 Fully Active START
__ EMA Alerts 20 Fully Active START

Actions
ES End Subsystem SP=Start Monitor Program
SS Start Subsystem EP=End Monitor Program
OF Switch System Activity OFF
ON Switch System Activity ON

F3=Exit F5=Refresh F8=Details F10=Active F12=Previous
F14=IOP Exc Msgs On F15=IOP Exc Msgs Off

=Stop=

Set system activity off with action OF.
End monitor program with action EP.
If necessary, End subsystem with action ES.

=Start=

ss
on
sp
Note - program will run under the user that starts it. best to run this under user EODJOB

Information Systems:EDI Control Panel for IMS/IMP/IOP/OMS

2015-10-21T18:05:35Z

172.30.20.117:

IMS (Inbound Mail System), IMP (Inbound Mail Parsing), IOP (Inbound Order Posting), OMS (Outbound Mail System), and EMA (Error Messages & Alerts) are controlled by subsystems and jobs that are started and ended by over night processing, and run all day long.

Work with Active Jobs BART
10/21/15 10:36:59
CPU %: 12.1 Elapsed time: 00:00:29 Active jobs: 513

Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...
Current
Opt Subsystem/Job User Type CPU % Function Status

EMASUBPRD QSYS SBS .0 DEQW
EMAIOPPRD QPGMR BCH .0 DLY-10:59:50 DLYW
IMPSUBPRD QSYS SBS .0 DEQW
IMPPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IMSSUBPRD QSYS SBS .0 DEQW
IMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW
IOPSUBPRD QSYS SBS .0 DEQW
IOPPOSTPRD QPGMR BCH 2.0 DLY-120 DLYW
OMSSUBPRD QSYS SBS .0 DEQW
OMSPOSTPRD QPGMR BCH .0 DLY-120 DLYW

Parameters or command
===>
F3=Exit F5=Refresh F7=Find F10=Restart statistics
F11=Display elapsed data F12=Cancel F23=More options F24=More keys

It may be necessary to stop and/or restart them during the day - if there are errors, or to recompile programs. To do this, go to Unity / Start uniPharm Extensions / VA Company / UWD Extensions / EDI - IMS, IMP, etc / EDI Control Panel.

10/21/15 10:49:24 uniPHARM -- PRODUCTION EDRIQ100/CONTROL
EDI -- Main Control Panel PRODUCTION 1.00

Action Sub System
System Status Switch
__ IMS Inbound Mail Receiving 20 Fully Active START
__ IMP Inbound Mail Parsing 20 Fully Active START
__ IOP Inbound Order Posting 20 Fully Active START

__ OMS Outbound Mail Send 20 Fully Active START
__ EMA Alerts 20 Fully Active START

Actions
ES End Subsystem SP=Start Monitor Program
SS Start Subsystem EP=End Monitor Program
OF Switch System Activity OFF
ON Switch System Activity ON

F3=Exit F5=Refresh F8=Details F10=Active F12=Previous
F14=IOP Exc Msgs On F15=IOP Exc Msgs Off

=Stop=

Set system activity off with action OF.
End monitor program with action EP.
If necessary, End subsystem with action ES.

=Start

ss
on
sp
Note - program will run under the user that starts it. best to run this under user EODJOB

Information Systems:EDI Control Panel for IMS/IMP/IOP/OMS

2015-10-21T17:54:01Z

172.30.20.117: Created page with "IMS (Inbound Mail System), IMP (Inbound Mail Parsing), IOP (Inbound Order Posting), OMS (Outbound Mail System), and EMA (Error Messages & Alerts) are controlled by subsystems..."

Information Systems:WebSmart Overview

2015-10-21T00:22:07Z

172.30.20.117: Created page with "WebSmart is a development tool for creating RPG desktop and mobile web applications. Excel Systems (ESDI) is the name of the company in Sidney, Vancouver Island that wrote..."

WebSmart is a development tool for creating RPG desktop and mobile web applications.

Excel Systems (ESDI) is the name of the company in Sidney, Vancouver Island that wrote it.

Website - http://www.excelsystems.com/
Email - excel@excelsystems.com
Phone - 250-655-1766

BCD is the company that markets it.

Website - http://www.bcdsoftware.com/
Phone – 508-594-2700

A client (IDE – interrated development environment) runs on your PC, where you code in PML and HTML. When you compile, the code is translated to free form RPG on the i.

We have multiple Apache web servers on the i; ADMIN (administration – we don’t use this, but starting Domino now starts all servers), WEBINTER (InfoNet), WEBSMART (Web Orders), and WEBTEST (obviously the testing environment).

In WRKACTJOB –

Work with Active Jobs BART
12/16/14 12:12:18
CPU %: .0 Elapsed time: 00:00:00 Active jobs: 541

Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...
Current
Opt Subsystem/Job User Type CPU % Function Status
__ QHTTPSVR QSYS SBS .0 DEQW
__ WEBTEST QTMHHTTP BCH .0 PGM-QZHBMAIN SIGW
__ WEBTEST QTMHHTTP BCI .0 PGM-QZSRLOG SIGW
__ WEBTEST QTMHHTTP BCI .0 PGM-QZSRHTTP SIGW
__ WEBTEST QTMHHTTP BCI .0 PGM-QZSRHTTP DEQW
__ WEBTEST QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW

Parameters or command
===> _______________________________________________

F3=Exit F5=Refresh F7=Find F10=Restart statistics
F11=Display elapsed data F12=Cancel F23=More options F24=More keys

CGI (Common Gateway Interface) is a standard method to generate dynamic content on web pages and web applications. When implemented on a web server, provides an interface between it and programs that generate the web content. These programs are known as CGI scripts or simply CGIs; they are usually written in a scripting language, but can be written in any programming language (from Wikipedia). Multiple iterations of these programs will be started; depending on the volume of requests received.

Information Systems:InfoNet Data Analyser

2015-10-21T00:14:39Z

172.30.20.117: Created page with "=Data Analyser= We called it this because we planned on using ASW’s Analyser files. Then we found it was better to use the transaction files that Analyser is based on inst..."

=Data Analyser=

We called it this because we planned on using ASW’s Analyser files. Then we found it was better to use the transaction files that Analyser is based on instead. However, the name stuck. So keep in mind this is not ASW Analyser.

==Sales Order Fill Rates==

There are two versions of fill rate analysis; one uses all orders and all picking for a particular day, and the other starts with all orders on a day and follows them right through to picking. (One difference between these is that orders received after afternoon cut off are typically picked the next day.)

Early every morning, as part of the End of Day, WEBPRDP/BLDDAYLINE is run to accumulate all order and picking data write to files WEBPRDD/DAYLINEP and DAYLIN2P. This program can be run for any day by calling it manually, with the date in the parameters, ie CALL BLDDAYLINE ‘20140801’.

This process only includes customer orders that are picked by the warehouse. Orders that will be picked at a future date (future orders, promos, and special orders) are handled differently than orders that will drop for picking right away. They will not be included in any totals based on the order date, but on the picked date.

As a regular order can be picked up to three days after it is ordered (ordered Friday evening, picked on a statutory holiday Monday), and orders under the customer’s daily order minimum can be held for up to four days, BLDDAYLINF is called, which will rebuild the previous 4 days.

Included Order Types

Orders that are available for picking when ordered –

DO – Detail Order
EO – Electronic Order
OR – Price Override
SO – Sales Order (Manual)
WO – Web Order

Returns –

RT – Return from Store (non-web)
WR – Web Return from Store
** these are credits, and will subtract from all totals instead of adding

Future dated orders (added to all totals based on date picked)

EP – Electronic Promo Order
FO – Future Order (Manual)
PR – Promotional Order (Manual)
SP – Special Order (Cat 900 only)
WF – Web Future Order
WP – Web Promo Order

In the text below, I will call these current orders (includes returns), and future orders.

* Sometimes electronic orders (EO), and very rarely Web Orders (WO) can act like future orders; when a customer is below their daily order minimum their orders will be held until they are over it. These orders will be held for up to 4 days, then cancelled.

==Summary Data File (DAYLINEP)==

Two sets of totals are calculated; one based on order date and the other on picked date. Except for future dated orders; which are included in both set of totals based on picked date. The values are broken down by warehouse / buyer / item account group.

DLDATE Date (YYYYMMDD)
DLYYMM Year/Month (YYYYMM)
DLFISC Fiscal Period
DLYEAR Year
DLDAYNUM Day number (from SROCLD)
DLDAY Day of Week (Monday, Tuesday, etc)
DLWHSE Warehouse
DLRESP Buyer
DLAGRP Item account group
DLONHAND Onhand at cost

Sales Summary by Order Date

DLSALESO Sales Amount/Order Date
DLSHPLNO Lines Shipped/Order Date
DLSQTYO Quantity Shipped/Order Date

Sales Summary by Pick Date

DLSALESP Sales Amount/Pick Date
DLSHPLNP Lines Shipped/Pick Date
DLSQTYP Quantity Shipped/Pick Date

Order Summary

DLORDLN Lines Ordered (include cancelled lines and future orders)
DLORDCHG Quantity Changes
DLORDCAN1 Lines cancelled because invalid
DLORDCAN2 Lines cancelled because item is discontinued
DLORDCAN3 Lines cancelled because out of stock
DLORDCAN4 Lines cancelled by CPR (restricted or limited qty)
DLORDCAN5 Lines cancelled because special order or promo item
DLFUTURA Future Dated Lines Accepted
DLFUTURD Future Dated Lines Picked
DLACCLN Lines Accepted
DLORDERS Accepted Order Amount
DLNOTPCK Order lines that have been dropped for picking, but have not
yet been picked. If this does not clear after a few days, it
could mean that a current order line was accepted, but by the
time it was ready to drop for picking the stock was not available,
or that a customer is on credit hold.

Fill Rates by Order Date

DLFFILLO Fully Filled/Order Date
DLPFILLO Partially Filled/Order Date
DLZFILLO Zero Filled/Order Date
DLCFILLO Lines that were accepted then cancelled

Fill Rates by Pick Date

DLFFILLP Fully Filled/Pick Date
DLPFILLP Partially Filled/Pick Date
DLZFILLP Zero Filled/Pick Date
DLCFILLP Lines that were accepted then cancelled

Summary of all Order Lines by Order Source

DLWEB Web
DLTRIRX TRI-RX
DLTRIP TRI-POS
DLARI ARI
DLKROLL Kroll
DLMANUAL Manual
DLSIMP Simplicity
DLTREX T-Rex
DLPOSIT Positec
DLEDISO EDI-SO

Summary of accepted Order Lines by Order Source

DLAWEB Web/Accepted
DLATRIRX TRI-RX/Accepted
DLATRIP TRI-POS/Accepted
DLAARI ARI/Accepted
DLAKROLL Kroll/Accepted
DLAMANUAL Manual/Accepted
DLASIMP Simplicity/Accepted
DLATREX T-Rex/Accepted
DLAPOSIT Positec/Accepted
DLAEDISO EDI-SO/Accepted

==Detail Data File (DAYLIN2P)==

This file gives counts by reason code for order lines being cancelled or zero picked. The difference between the two, is that ‘zero picked’ is what we have some control over; out of stock, expired, can’t fine. ‘Cancelled’ is things that we can’t effect, like errors on the stores part (duplicate PO, bad item numbers).

D2DATE Date (YYYYMMDD)
D2YYMM Year/Month (YYYYMM)
D2FISC Fiscal Period
D2YEAR Year
D2DAYNUM Day number (from SROCLD)
D2DAY Day of Week (Monday, Tuesday, etc)
D2WHSE Warehouse
D2RESP Buyer
D2AGRP Item account group
D2TYPE Type – ‘CA’ for cancelled or ‘ZP’ for zero picked
D2SUBT Sub Type – ‘ORD’ for lines not accepted at ordering, or
‘PCK’ for cancelled or zero picked after order line was accepted
D2LSRN Lost sales reason code
D2COUNT Count of order lines

==RPG program BLDDAYLINE==

Files used –

SROISDPL – Invoice Lines
SROSRO – Warehouse balances
SROORSHE – Sales order header
SROORSPL – Sales order line
IOPHDRP – IOP order header
IOPLINP – IOP order line

Totals are summarized by date / warehouse / buyer / item account group.

===Total onhand===

Read warehouse file and calculate total on hand value at average cost.

SQL –
select srsrom, itresp, itagrp, sum(srsthq * srapco)
from srosro, xxitemp
where srprdc = itprdc and srsthq <> 0
group by srsrom, itresp, itagrp
order by srsrom, itresp, itagrp

Result moved to DLONHAND.

===Sales Summary by order date===

Link invoice lines to the sales order header, and summarize amount and line count by debit/credit flag and order type. The invoice file includes the item account group, so only include records for inventory items (item account group starts with ‘I’), by order date (from the sales order header).

SQL –
select idsrom, idresp, idpagr, idtypp, idordt, sum(idamou), count(*), sum(idqty)
from sroisdpl, sroorshe
where idorno = ohorno and ohoush = 'Y' and idpagr < 'I999' and ohodat = 20140702
group by idsrom, idresp, idpagr, idtypp, idordt
order by idsrom, idresp, idpagr, idtypp, idordt

When idtypp (debit/credit flag) is ‘2’, reverse accumulators.

Current orders are added to DLSALESO, DLSHPLNO, AND DLSQTYO.

Future orders are not added here, as they are added based on date picked.

===Sales summary by pick date===

Read invoice file, and summarize amount and line count by debit/credit flag and order type. TThe invoice file includes the item account group, so only include records for inventory items (item account group starts with ‘I’), by invoice date (which is the date picked).

SQL –
select idsrom, idresp, idpagr, idtypp, idordt, sum(idamou), count(*), sum(idqty)
from sroisdpl
where ididat = 20140702 and idpagr < 'I999'
group by idsrom, idresp, idpagr, idtypp, idordt
order by idsrom, idresp, idpagr, idtypp, idordt

When idtypp (debit/credit flag) is ‘2’, reverse accumulators.

Current and future orders are added to DLSALESP, DLSHPLNP, AND DLSQTYP.

Future orders are also added to sales by order date (DLSALESO, DLSHPLNO, DKSQTYO), future orders picked (DLFUTURD), and accepted orders (DLORDERS, DLACCLN).

===Get accepted order lines===

Link the sales order headers to sales order lines, and summarize the order value and line count by order type and handler.

SQL –
select ohsrom, itresp, itagrp, ohordt, ohhand, sum(oloqts*olsalp), count(*)
from sroorshe, sroorspl, xxitemp
where ohorno = olorno and olprdc = itprdc and olprdc <> '02000040' and ohodat = 20140702 and ohoush = 'Y'
group by ohsrom, itresp, itagrp, ohordt, ohhand
order by ohsrom, itresp, itagrp, ohordt, ohhand

All orders add to DLORDLN.

All current orders add to DLORDERS and DLACCLN.

All future orders add to DLFUTURA.

WO, WP, WR, and WF add to DLWEB and DLAWEB.

EO and EP are accumulated by source –

EDI-ARI adds to DLAARI and DLARI.
EDI-KROLL adds to DLAKROLL and DLKROLL.
EDI-POSITE adds to DLAPOSIT and DLPOSIT.
EDI-SIMPLI adds to DLASIMP and DLSIMP.
EDI-TREX adds to DLATREX and DLTREX.
EDI-TRIPOS adds to DLATRIP and DLTRIP.
EDI-TRIRX adds to DLATRIRX and DLREIRX.
Anything else (there shouldn’t be) adds to DLAEDISO and DLEDISO.

DO, FO, OR, PR, RA, RT, SO, and SP add to DLAMANUAL and DLMANUAL.

===Get cancelled and changed order lines===

Link the IOP header and line files together, and count number of lines per various error flags.

SQL –
select itresp, itagrp, ihsrce, idlspo, idcpqt, idlsre, idstat, idpafi, idnofi, count(*)
from iophdrp left outer join ioplinp on iophdrp.ihunin = ioplinp.ihunin left outer join xxitemp on iditem = itprdc
where ihcryr = 14 and ihcrce = 20 and (idpafi = 'Y' or idaswo = 0) and ihcrmo = 07 and ihsrce <> 'MISCBIL' and ihcrdy = 02
group by itresp, itagrp, ihsrce, idlspo, idcpqt, idlsre, idstat, idpafi, idnofi
order by itresp, itagrp, ihsrce, idlspo, idcpqt, idlsre, idstat, idpafi, idnofi

This will return counts of order lines that have either had the quantity changed, or have not posted to ASW.

If IDPAFI (partially filled) is ‘Y’, add lines to DLORDCHG.

Otherwise, add lines to DLORDLN, and by source (IDSRCE) add lines to the applicable summary of order lines field (ie DLARI, DLSIMP).

If IDPAFI (partially filled) is not ‘Y’, and IDCPQT (quantity changed by CPR) is ‘Y’ add lines to DLORDCAN4 (cancelled by CPR).

If IDPAFI (partially filled) is not ‘Y’, IDCPQT (quantity changed by CPR) is not ‘Y’, IDLSPO (posted to lost sales) is ‘Y’, and IDLSRE (lost sales reason code) is ‘S’ add lines to DLORDCAN5 (special order or promo item).

If IDPAFI (partially filled) is not ‘Y’, IDCPQT (quantity changed by CPR) is not ‘Y’, IDLSPO (posted to lost sales) is ‘Y’, and IDLSRE (lost sales reason code) is ‘A’ or ‘B’ add lines to DLORDCAN3 (out of stock).

If IDPAFI (partially filled) is not ‘Y’, IDCPQT (quantity changed by CPR) is not ‘Y’, IDLSPO (posted to lost sales) is ‘Y’, and IDLSRE (lost sales reason code) is ‘P’ or ‘R’ add lines to DLORDCAN4 (cancelled by CPR).

If IDPAFI (partially filled) is not ‘Y’, IDCPQT (quantity changed by CPR) is not ‘Y’, IDLSPO (posted to lost sales) is ‘Y’, and IDLSRE (lost sales reason code) is not ‘A’, ‘B’, ‘P’, or ‘R’ add lines to DLORDCAN2 (discontinued).

If IDPAFI (partially filled) is not ‘Y’, IDCPQT (quantity changed by CPR) is not ‘Y’, IDLSPO (posted to lost sales) is not ‘Y’, and IDSTAT (status code) is ‘50’ add lines to DLORDCAN5 (special order or promo item).

If IDPAFI (partially filled) is not ‘Y’, but record does not fit into any of the above categories, add lines to DLORDCAN4 (error).

===Get fully filled by order date===

Get count of lines where the sales order quantity equals the invoice quantity.

SQL –
select idsrom, idresp, idpagr, idtypp, idordt, count(*) from sroisdpl, sroorspl, sroorshe
where idorno = olorno and idolin = olline and idorno = ohorno and idqty = oloqts and ohodat = 20140702 and idpagr < 'I999'
group by idsrom, idresp, idpagr, idtypp, idordt
order by idsrom, idresp, idpagr, idtypp, idordt

When idtypp is ‘2’, subtract instead of adding.

Current orders are added to DLFFILLO. Future orders will be added based on picked date.

===Get partially filled by order date===

Get count of lines where the sales order quantity does not equal the invoice quantity.

SQL –
select idsrom, idresp, idpagr, idtypp, idordt, count(*)
from sroisdpl, sroorspl, sroorshe
where idorno = olorno and idolin = olline and idorno = ohorno and idqty <> oloqts and ohodat = 20140702 and idpagr < 'I999'
group by idsrom, idresp, idpagr, idtypp, idordt
order by idsrom, idresp, idpagr, idtypp, idordt

When idtypp is ‘2’, subtract instead of adding.

Current orders are added to DLPFILLO. Future orders will be added based on picked date.

===Get zero filled and cancelled by order date===

Get lines from the lost sales file linked to the sales order line, and based on the sales order date.

SQL –
select lssrom, itresp, lspagr, lsordt, lsplno, lslsrn, olcqts, olstat, olords
from srolstsl, sroorspl, xxitemp
where lsorno = olorno and lsline = olline and lsprdc = itprdc and olrddt = 20140702

Include current orders only; future orders will be added based on picked date.

Returns (LSORDT equals ‘RT’ or ‘WR’) subtract instead of add.

If OLCQTS (confirmed quantity from sales order line) is not zero, this line was a partial pick, which has already been counted, so ignore it here.

If LSLSRN (lost sales reason code) is ‘A’, ‘B’, ‘1’, ‘2’, ‘3’, or ‘5’ add to DLZFILLO (zero filled by order date. Otherwise add to DLCFILLO (cancelled after being accepted as order).

===Get fully filled by picked date===

Get count of lines where the sales order quantity equals the invoice quantity.

SQL –
select idsrom, idresp, idpagr, idtypp, idordt, count(*)
from sroisdpl, sroorspl
where idorno = olorno and idolin = olline and idpagr < 'I999' and idqty = oloqts and ididat = 20140702
group by idsrom, idresp, idpagr, idtypp, idordt
order by idsrom, idresp, idpagr, idtypp, idordt

When idtypp is ‘2’, subtract instead of adding.

Current and future orders are added to DLFFILLP. Future orders are also added to DLFFILLO.

===Get partially filled by picked date===

Get count of lines where the sales order quantity does not equal the invoice quantity.

SQL –
select idsrom, idresp, idpagr, idtypp, idordt, count(*)
from sroisdpl, sroorspl
where idorno = olorno and idolin = olline and idpagr < 'I999' and idqty <> oloqts and ididat = 20140702
group by idsrom, idresp, idpagr, idtypp, idordt
order by idsrom, idresp, idpagr, idtypp, idordt

When idtypp is ‘2’, subtract instead of adding.

Current and future orders are added to DLPFILLP. Future orders are also added to DLPFILLO.

===Get zero filled and cancelled by picked date===

Get lines from the lost sales file linked to the sales order line, and based on the lost sales date.

SQL –
select lssrom, itresp, lspagr, lsordt, lsplno, lslsrn, olcqts, olstat, olords
from srolstsl, sroorspl, xxitemp
where lsorno = olorno and lsline = olline and lsprdc = itprdc and lslsdt = 20140702

Current and future orders are included.

Returns (LSORDT equals ‘RT’ or ‘WR’) subtract instead of add.

If OLCQTS (confirmed quantity from sales order line) is not zero, this line was a partial pick, which has already been counted, so ignore it here.

If LSLSRN (lost sales reason code) is ‘A’, ‘B’, ‘1’, ‘2’, ‘3’, or ‘5’ add to DLZFILLP (zero filled by order date. Otherwise add to DLCFILLP (cancelled after being accepted as order).

===Get Current Orders Not Picked by Order Date===

From the ASW sales order files, read active order lines that have not yet been picked but were ordered on the requested date.

SQL –
select ohsrom, itresp, itagrp, ohordt, count(*)
from sroorshe, sroorspl, xxitemp
where ohorno = olorno and olprdc = itprdc and ohstat = ' ' and olstat = ' ' and olords <= 30 and ohodat = 20170702
group by ohsrom, itresp, itagrp, ohordt
order by ohsrom, itresp, itagrp, ohordt

Returns (OHORDT equals ‘RT’ or ‘WR’) subtract instead of add.

Add lines for current orders to DLNOTPCK.

===Get Future Order Not Picked by Expected Dispatch Date===

From the ASW sales order files, read active order lines that have not yet been picked but had a dispatch date of the requested date.

SQL –
select ohsrom, itresp, itagrp, ohordt, count(*)
from sroorshe, sroorspl, xxitemp
where ohorno = olorno and olprdc = itprdc and ohstat = ' ' and olstat = ' ' and olords <= 30 and oldelt = 20140702
group by ohsrom, itresp, itagrp, ohordt
order by ohsrom, itresp, itagrp, ohordt

Add lines for future orders to DLNOTPCK.

Information Systems:WebSmart Problems

2015-10-21T00:10:04Z

172.30.20.117:

Note that there has been a little issue since the upgrade to V6R1. When Domino is started, it starts all the HTTP servers – including all the ones we use for the WebSmart programs. Normally, we wouldn’t have the administrator web server running, but it starts anyway.

* [[WebSmart CGI Job Takes Lots of CPU]]
* [[WebSmart CGI Job Takes Lots of CPU|Customer has Problem with cart]]
* [[WebSmart Can't Upload File]]

Information Systems:Work with Apache Server

2015-10-21T00:09:14Z

172.30.20.117: Created page with "From wikipedia - Apache is the world’s most widely used web server software. It is the most popular HTTP server, as was the first to serve more than 100 million websites...."

From wikipedia - Apache is the world’s most widely used web server software. It is the most popular HTTP server, as was the first to serve more than 100 million websites. Apache is free and open source software, and typically runs on Unix-like systems.

On a command line, key in WRKLNK and press enter. Press page down until you see Object Link ‘WWW’.

Work with Object Links

Directory . . . . : /

Type options, press Enter.
2=Edit 3=Copy 4=Remove 5=Display 7=Rename 8=Display attributes
11=Change current directory ...

Opt Object link Type Attribute Text
_ u480bp SYMLNK
_ var DIR
_ webroot DIR
6 www DIR
_ BankEDI DIR
_ BankEDI2 DIR
_ ChqMaster DIR
_ DOMINO DIR
_ EFT DIR
More...
Parameters or command
===>
F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel F17=Position to
F22=Display entire field F23=More options

Use option 5 to display the contents of WWW. Then use option 5 to display one of the servers; WEBINTER (InfoNet), WEBSMART (Web Orders), or WEBTEST (development). Use option 5 to display the configuration file(s) in CONF. There could be copies or backups; the current configuration file is HTTPD.CONF. Use option 2 to edit it.

I don’t know much about the code in this. A line with # in the first character is a comment, or a commented out line. ‘LISTEN’ obviously defines the IP address and port the server is working on. See the section ‘WebSmart / Security’ for a description of the ‘DIRECTORY’ statements.

To get the Apache servers to run on a different server (for example when we are testing a replacement i), change all the IP addresses, and DNS names.

Information Systems:WebSmart Can't Upload File

2015-10-21T00:08:05Z

172.30.20.117: Created page with "If a WebSmart program won’t upload a file, use option 5 to work with the first CGI job of the affected web server. Then option 10 to display the job log, F10 to display d..."

If a WebSmart program won’t upload a file, use option 5 to work with the first CGI job of the affected web server. Then option 10 to display the job log, F10 to display detail, and F18 to go to the bottom. Page back to find an error message. There are a lot of messages in the log, so this could be difficult. Get the user to try the operation again, then look at the log immediately.

On March 26, 2015 we had the messages 'SQL system error' and 'Error occurred in SQL Call Level Interface'. This made no sense, as the line in the CL program where the error occurred (press F9 on the message to see this) was CPYFRMIMPF (copy from import file). When I googled the error code (SQL0901), I found that the problem was with the ODBC driver (according to Wikipedia; ‘ODBC (Open DataBase Connectivity) is a standard programming language middleware API for accessing database management systems (DBMS)’). As Web Orders was successfully uploading orders from the hand held units, I figured that the driver loaded into the InfoNet web server had been corrupted; not the facility itself. I didn’t think it was worth ending and restarting the server and disrupting everyone, so waited for it to happen as part of the overnight jobs. The next day the upload worked fine.

Information Systems:WebSmart CGI Job Takes Lots of CPU

2015-10-21T00:07:32Z

172.30.20.117: Created page with "This is both for 'WebSmart CGI Job Takes Lots of CPU' and for 'Customer has Problem with Cart'. Look at ‘work with active jobs’ (WRKACTJOB), subsystem QHTTPSVR. The ‘j..."

This is both for 'WebSmart CGI Job Takes Lots of CPU' and for 'Customer has Problem with Cart'.

Look at ‘work with active jobs’ (WRKACTJOB), subsystem QHTTPSVR. The ‘job’ is the server name – WEBINTER (for InfoNet), WEBSMART (for Web Orders), and WEBTEST (for testing). The ‘functions’ we are interested in are ‘PGM-QZSRCGI’. (CGI stands for ‘Common Gateway Interface’, which is the interface between the web server and programs that generate web content. The more requests there are from users, the more of these jobs will be running.)

If the WEBSMART CGI jobs are taking up a lot of CPU%, and are staying that way, it could mean there are duplicate lines in the cart. To check this, go to

UWD Extensions
60 Web Interface
52 Miscellaneous Menu
3 Find Duplicate Lines in Cart

Display Report
Report width . . . . . : 134
Position to line . . . . . Shift to column . . . . . .
Line ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+...10....+...11....+...12....
use EZ to delete dup Subtrans Trans Seq ITEM Customer Store Last name First
from file pw_trnf in Name Number Num COUNT
library xl_webspt
000001 claim 299 4 2 11005 TEST TEST
000002 claim 299 5 2 11005 TEST TEST
000003 claim 299 6 2 11005 TEST TEST

F3=Exit F12=Cancel F19=Left F20=Right F21=Split F22=Width 80

If nothing shows up in this report, you have another issue. If something does, the duplicates have to be deleted to fix the problem with the server programs (CGI’s).

The way to fix this is shown in red. On the command line, key in EZ and press enter.

Easy View a File (EZVIEW)

Type choices, press Enter.

File Name: . . . . . . . . . . . pw_trnf Name, *PRV, *SELECT
Library Name: . . . . . . . . xl_webspt Name, *LIBL
Member Name: . . . . . . . . . . Character value
Access Method . . . . . . . . . *KEY *KEY, *ARRIVAL

F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

Key in the file and library names, and press enter twice.

Rec. Length.: 32742 File: PW_TRNF Library: XL_WEBSPT Member: PW_TRNF
Rec. Count..: 2404 Access.: *KEY Mode..: INQUIRY
SCAN........: to -OR- *EQ
Field number: 1 field/text locate:
Lower Limits. 00000299 0000 US

Transacti Subtrans Name TXSEQN TXLIFE
35 _ 299 0 30
9892 _ 299 claim 1 0
9893 _ 299 claim 2 0
9903 _ 299 claim 3 0
9923 _ 299 claim 4 0
9928 D 299 claim 4 0
9927 _ 299 claim 5 0
9929 _ 299 claim 5 0
5838 _ 299 claim 6 0
9930 _ 299 claim 6 0
291 _ 305 0 30
4508 _ 305 regular 1 0
4641 _ 305 regular 2 0
557 _ 319 0 30
F2=Previous Files F3=Exit F4=Select Mode F24=More Keys

Use the ‘lower Limits’ field to position to the cart that needs to be fixed. The cart number is eight digits, so be sure to put in enough leading zeroes. There can be multiple cart types (regular, promo, claim), so be sure you are looking at the correct one. You have may have to page down to get to the duplicate cart type (‘Subtrans Name’) and line number (‘TXSEQN’). When you find the duplicate, key a D in front of it, and press enter. (I usually delete the one with the highest record number (left column).

Rec. Length.: 32742 File: PW_TRNF Library: XL_WEBSPT Member: PW_TRNF
Rec. Count..: 2422 Mode..: DELETE
Format......: RTRNF
RRN.........: 9928

Transaction Number......: 299
Subtrans Name...........: claim
Sequence Number.........: 4
Life in days............: 0
Life in hours...........: 0
Extend Each access......:
Date/Time Trans Set will: 0001-01-01-00.00.00.000000
Transaction Data........: 00895201 ?OOD

Press Enter to Delete Record Bottom
F3=Exit F4=Switch Modes F9=Paste Record F10=Paste Field F24=More Keys

Press enter again to confirm that you really do want to delete this record.

Repeat for all duplicate lines, then press F3 to exit.

This should fix the problem with the CGI jobs. If it doesn’t, you can use the disaster menu to end Web Servers, then restart them. Note that if you do that, it is possible for a user (InfoNet or Web Orders, as this will end all WebSmart servers) to lose what they are working on.

Information Systems:WebSmart Problems

2015-10-21T00:06:11Z

172.30.20.117: Created page with "* WebSmart CGI Job Takes Lots of CPU * Customer has Problem with cart * WebSmart Can't Upload File"

* [[WebSmart CGI Job Takes Lots of CPU]]
* [[WebSmart CGI Job Takes Lots of CPU|Customer has Problem with cart]]
* [[WebSmart Can't Upload File]]

Information Systems:InfoNet User Authorities

2015-10-21T00:03:08Z

172.30.20.117: Created page with "InfoNet runs in a browser, which means it can be accessed from anywhere that has an internet connection. The user signs on with their System i user ID and password (which i..."

InfoNet runs in a browser, which means it can be accessed from anywhere that has an internet connection.

The user signs on with their System i user ID and password (which is validated against the i user profiles), but what they can see in InfoNet is controlled by the file WEBPRDD / INUSERP.

This controls the functions the user is allowed to do, and the information they can see.

[[File:websmart-2.jpg]]

This allows the user to configure their own displays.

[[File:websmart-3.jpg]]

[[File:websmart-4.jpg]]

File INUSERP has 299 flags; 141 of which are used by the two programs above (Change User Authorities, and Change Web User). The fields are named INFLAG001 to INFLAG299. To keep track of what each does, I go into the source of this file, and change the text; but I do NOT compile it – if I did, every InfoNet program would have to be recompiled.

Information Systems:InfoNet Overview

2015-10-21T00:02:42Z

172.30.20.117: Created page with "This was written in WebSmart PML and html, instead of RPG and DDS. Screen design is much easier in html - you don’t have to count field lengths and screen positions; the br..."

This was written in WebSmart PML and html, instead of RPG and DDS. Screen design is much easier in html - you don’t have to count field lengths and screen positions; the browser will dynamically just make everything fit.

The first programs in InfoNet were item and partner maintenance. There is just one program for each, instead of the previous dozens in both base ASW and the extensions. Because you can have a very long page in html (unlike the 24 row green screen), in maintenance all data fields can be keyed and validated at the same time.

We then started using it for inquiry programs. RPG inquiry programs in ASW and most of the extensions use SET and READ commands, then test to see if each record fits the search criteria. This was fine in the beginning, but now we have transaction files with record counts in the tens of millions. We had two options – rewrite these programs to use SQL instead, or write them in WebSmart – also using SQL. (For an explanation of why SQL is faster, see ‘SQL – Structured Query Language’ in the ‘Programming’ section of this manual.) We realized that development would be faster and easier in WebSmart, the resulting programs would be easier for the users, and the browser based screens would look better and be able to show much more information. (Instead of being restricted to 24 rows of 80 characters, the display is only restricted by how small the characters the user could read – which on a large display is a lot.)

Then we started thinking about replacing InfoManger, our business intelligence package. (It was expensive, inflexible, slow, and support was almost non-existent. See the WebSmart / History section above for details.) Again, because the WebSmart programs are all using SQL, the user can select from a broad range of select, sort, and summary options, and the optimizer finds the fast access path.

Information Systems:InfoNet

2015-10-21T00:02:14Z

172.30.20.117: Created page with "* InfoNet Overview * InfoNet User Authorities * InfoNet Data Analyser * InfoNet Problems"

* [[InfoNet Overview]]
* [[InfoNet User Authorities]]
* [[InfoNet Data Analyser]]
* [[InfoNet Problems]]

Information Systems:Developing programs in WebSmart

2015-10-20T23:59:18Z

172.30.20.117:

==WebSmart Program Development==

===Drop Down Menus===

Both InfoNet and Web Orders have a header HTML defined, which is included in all programs. Web Orders has a banner and a drop down menu; InfoNet just has a drop down menu (it’s for internal use – we know who we are, and we need that extra real estate to display data). Because the include statement contains the entire path to the header –

include("/webroot/unipharm/internal/header.html");

– the same one is used in both development and production. Therefore it cannot be updated until the new programs are moved to production.

===File Access===

Files are not explicitly defined as input or output, but implicitly based on their use. This means that you could add a record update to a working program, and find that it no longer works. If the update you added is the first update of that file, the file use is changed from input to update, so then all the reads will hold the records and cause record locks. It would be best to always use *NO in the third parameter of GETRCD and GETNXTRCD – unless you are actually reading the record in order to update it.

Information Systems:Developing programs in WebSmart

2015-10-20T23:58:59Z

172.30.20.117: Created page with "=WebSmart Program Development= ==Drop Down Menus== Both InfoNet and Web Orders have a header HTML defined, which is included in all programs. Web Orders has a banner and a..."

=WebSmart Program Development=

==Drop Down Menus==

Both InfoNet and Web Orders have a header HTML defined, which is included in all programs. Web Orders has a banner and a drop down menu; InfoNet just has a drop down menu (it’s for internal use – we know who we are, and we need that extra real estate to display data). Because the include statement contains the entire path to the header –

include("/webroot/unipharm/internal/header.html");

– the same one is used in both development and production. Therefore it cannot be updated until the new programs are moved to production.

==File Access==

Files are not explicitly defined as input or output, but implicitly based on their use. This means that you could add a record update to a working program, and find that it no longer works. If the update you added is the first update of that file, the file use is changed from input to update, so then all the reads will hold the records and cause record locks. It would be best to always use *NO in the third parameter of GETRCD and GETNXTRCD – unless you are actually reading the record in order to update it.

Information Systems:WebSmart History

2015-10-20T23:56:39Z

172.30.20.117: Created page with "A replacement was needed for the EOB (Electronic Order Book), which was a program installed on shareholder and customer PC’s. More functionality was wanted, and it would no..."

A replacement was needed for the EOB (Electronic Order Book), which was a program installed on shareholder and customer PC’s. More functionality was wanted, and it would no longer function after 999 weeks of use (‘week’ was a three digit field).

Web Orders went live June 29, 2005; week 999 was February 19, 2011. Excel wrote it, and did a major update in late 2009 / early 2010. We can make changes and additions to it ourselves; but don’t have Excel’s experience, and knowledge of new tools and innovations.

In November 2006 we started developing item and partner maintenance in WebSmart. The purpose was to have a single program for each that would do all maintenance – instead of the existing multiple menu options in both ASW and Extensions to add a single item or partner. As it was to be a single program writing and reading a single browser page that included all information, full editing and validation could be done.

Previously, uniPHARM had a simple web portal called ‘InfoNet’ – the name stuck when we replaced it with the new programs.

We realized that WebSmart was an ideal tool for data analysis. We could prompt the user for various selection, summary, and sort criteria, build a SQL statement to extract the requested information, then display it. After this program had been developed once, we then used it as a template to give us more and more varied information. Sometimes the SQL took too long to give the user the required information, or the data extract was too complicated; so we came up with two other methods. As part of our overnight process, we build several of the files used by InfoNet. For example, XXSTATSP, which for each item gives totals by the last twelve months for sales, lost sales, and forecasts. Another method used is to build a work file when the user presses ‘search’, then have the program use that work file.

Using sample code from Excel’s web site, we were able to add graphs, and the ability to export a file to Excel (the spreadsheet – not the company).

In about 2005, we had installed a business intelligence tool call InfoManager. Every night the data warehouse would be updated with the day’s transactions, and every Saturday the entire day was spent recalculating all the summaries. Those summaries had been updated every night, but started getting out of sync immediately. We wanted shareholders to be able to use InfoManager to look at summaries of their purchases from us, but it would not have been feasible to add them all as users on the i; both because of the increased cost of the license, and the load on the system of the extra users. So instead, we used the option to send the information in an email every month. It was an image only, not something shareholders could load into a spreadsheet.

It has a big job to keep this going. The process had to be babysat on the first of every month – no matter what the day. Then an update to InfoManger broke it, and the vendor was not able to fix it. We were able to limp along, but in September 2012 replaced it with a WebSmart program in Web Orders that the user could run themselves, and export the data to a spreadsheet.

In October 2014, we had Excel (the company this time) create the frame work for a dashboard, into which we put programs that we had developed to replace InfoManager. (Support had dwindled to practically nothing, and charts took a very long time to call up – users would call a dashboard then go for coffee. For all this, we paid $25,000 a year.) The replacement analytical programs we wrote with WebSmart are completely flexible, and take seconds to run.

Information Systems:ASW User Security

2015-10-20T23:51:02Z

172.30.20.117:

=ASW User Security=

Only ASW FIN is secured. All finance options are secured by ‘Group Profile’, which is on the user’s profile.

*VA/480B* User profile table maintenance 12/02/14 13:38:37 ASGD9604
-------------------------------------------------------------------------------
User profile........ KELSEYT
Description......... temp - Kelsey Tran
Templates
Name maintenance.... ALL Name enquiry........ GENERAL
Item maintenance.... ALL Item enquiry........ ALL
A/R invoice entry... CVM A/R payment entry... SYSTEM
A/P invoice entry... SYSTEM A/P payment entry... SYSTEM
G/L entry........... SYSTEM

Interactive process. N User language....... EN
Allow change period. N

Group profile....... FIN4 Valid as group prf.. N
RF warehouse........ MAI RF handler.......... KELSEYT
GUI activated....... Y Handler............. KELSEYT
Default SO type..... AR Engineer............ _______
Default PO type..... BE Max. support level.. 9
Orders in desc. seq. Y

F2=Client F8=Maintain HELP options F10=Copy record

The group profiles are –

CSRGRP Customer Service Rep Group
FIN1 Finance Supervisor
FIN2 Finance A/P G/L
FIN3 Finance A/P A/R G/L
FIN4 Finance A/P A/R
FIN5 Finance A/P

When a new person is added to the finance department, they will need to be attached to one of these FIN profiles. A new person in Customer Serve needs to be attached to CSRGRP.

==Authorize New User==

Before a user profile can be added (the ASW profile; not for the i), you must first add a ‘signature’.

On an ASW command line, key in 81 and press enter. Find ‘Signatures’ using the search argument.

*VA/480B* Table maintenance program selection 12/01/14 11:49:19 ASGD0181
-------------------------------------------------------------------------------
Appl Table
_ AAC Acquisition accounts
_ AAC Acquisition types
_ AAC Responsibles
_ DIS Cust. commission groups
_ DIS Item commission groups
_ DIS Sales tax classification
_ DIS Salesman commissions
_ GEN Divisions
X GEN Signatures
_ HLN Disposition codes
_ WHM Location sizes

-------------------------------------------------------------------------------
Appl Search argument
___ SI______________________________________

Select ‘Signatures’.

*VA/480B* Signature table maintenance 12/01/14 11:51:45 GDMD1111
-------------------------------------------------------------------------------
_ Signature Name
_ CHARANS AD Charanpreet Sidhu
_ CHARLENEH AD Charlene Huang
_ CHARLESN AD Charles Ng
_ CHARLIEC AD Charlie Chen
_ CHELSEAK Chelsea Kramer
_ CHELSEAM AD Chelsea Manansala
_ CHENC AD Chen Chen
_ CHENGY AD Cheng Yi
_ CHERIZAA AD Cheriza Adano
_ CHERYLC Cheryl Corkum CSR
_ CHERYLCB Cheryl Corkum Buyer
_ CHHONK AD Chhon Kheav
_ CHOOSY AD Choo Sang Yong
_ CHRISC AD Chris Chan
_ CHRISCH AD Chris Chow
-------------------------------------------------------------------------------
Signature
__________

Press F6 to add.

*VA/480B* Signature table maintenance 12/01/14 11:52:44 GDMD1113
-------------------------------------------------------------------------------
Signature........... KELSEYT
Name................ temp - Kelsey Tran

Security code....... ____
Common attest limit. ___________
Next level authority _________

Salesman............ N
Sales manager....... __________

Direct print
Printer queue....... QPRINT
Number of copies.... 1
Hold on spool file.. Y

F2=Assign users

Fill in the blanks as shown – the ‘signature’ must be the same as the i user ID. The default printer queue is set to QPRINT, which isn’t attached to a printer. ASW generates a lot of reports; most of which we don’t print. When the user wants to actually print something, they override the output queue to the closest printer.

Then go back to ‘Table maintenance program selection’, and find user profiles.

*VA/480B* Table maintenance program selection 12/01/14 12:04:10 ASGD0181
-------------------------------------------------------------------------------
Appl Table
_ AMT Work with AMT users
_ GEN User def. statistics identity
X GEN User profiles
-------------------------------------------------------------------------------
Appl Search argument
___ USER________________________________

Select ‘User profiles’.

*VA/480B* User profile table maintenance 12/01/14 12:17:18 ASGD9601
-------------------------------------------------------------------------------
User Description
_ CELIAS AD Celia Salas
_ CELSOC AD Celso Canlas
_ CHARANS AD Charanpreet Sidhu
_ CHARLENEH AD Charlene Huang
_ CHARLESN AD Charles Ng
_ CHARLIEC AD Charlie Chen
_ CHELSEAK Chelsea Kramer
X CHELSEAM Chelsea Manansala
_ CHENC AD Chen Chen
_ CHENGY AD Cheng Yi
_ CHERIZAA AD Cheriza Adano
_ CHERYLC Cheryl Corkum CSR
_ CHERYLCB Cheryl Corkum Buyer
_ CHHONK AD Chhon Kheav
_ CHOOSY AD Choo Sang Yong
-------------------------------------------------------------------------------
User
__________

F8=Maintain General HELP options

Select someone with the same accesses that the person you are adding will need.

*VA/480B* User profile table maintenance 12/01/14 11:40:58 ASGD9604
-------------------------------------------------------------------------------
User profile........ CHELSEAM
Description......... Chelsea Manansala
Templates
Name maintenance.... ALL Name enquiry........ GENERAL
Item maintenance.... ALL Item enquiry........ ALL
A/R invoice entry... CVM A/R payment entry... SYSTEM
A/P invoice entry... SYSTEM A/P payment entry... SYSTEM
G/L entry........... SYSTEM

Interactive process. N User language....... EN
Allow change period. N

Group profile....... FIN4 Valid as group prf.. N
RF warehouse........ MAI RF handler.......... CHELSEAM
GUI activated....... Y Handler............. CHELSEAM
Default SO type..... AR Engineer............ ________
Default PO type..... BE Max. support level.. 9
Orders in desc. seq. Y

F2=Client F8=Maintain HELP options F10=Copy record

Press F10 to copy this user profile.

*VA/480B* User profile table maintenance 12/01/14 11:40:58 ASGD9604
-------------------------------------------------------------------------------
User profile........ KELSEYT
Description......... temp - Kelsey Tran
Templates
Name maintenance.... ALL Name enquiry........ GENERAL
Item maintenance.... ALL Item enquiry........ ALL
A/R invoice entry... CVM A/R payment entry... SYSTEM
A/P invoice entry... SYSTEM A/P payment entry... SYSTEM
G/L entry........... SYSTEM

Interactive process. N User language....... EN
Allow change period. N

Group profile....... FIN4 Valid as group prf.. N
RF warehouse........ MAI RF handler.......... KELSEYT
GUI activated....... Y Handler............. KELSEYT
Default SO type..... AR Engineer............ _______
Default PO type..... BE Max. support level.. 9
Orders in desc. seq. Y

F2=Client F8=Maintain HELP options F10=Copy record

Key in user profile, description, RF handler, and handler, then press enter.

*VA/480B* User profile table maintenance 12/01/14 11:57:17 ASGD9611
Enquiry program templates
-------------------------------------------------------------------------------
User profile........ CHELSEAM
-------------------------------------------------------------------------------
Template Description
X FIN ASW Financial
_ RFH ASW Radio Frequency
-------------------------------------------------------------------------------
Template
___

Select the FIN inquiry program template.

*VA/480B* User profile table maintenance 12/01/14 11:57:56 ASGD9614
Enquiry program templates
-------------------------------------------------------------------------------
User profile........ CHELSEAM
Template............ FIN
Description......... ASW Financial

F13 enquiry......... HLR126 Hotline incident enquiry
F14 enquiry......... DMC119A Purchase orders
F15 enquiry......... FKR015 A/R balance/stat/agreem/trans
F16 enquiry......... FKC090 A/R credit time axis
F17 enquiry......... DMC120 Sales orders
F18 enquiry......... DMR121 Invoices
F19 enquiry......... DMR122 Customer service
F20 enquiry......... GDMR273 Credit stop codes
F21 enquiry......... FLR015 A/P balance/stat/agreem/trans
F22 enquiry......... FMR015 Account file
F23 enquiry......... GDMR201 Names
F24 enquiry......... ASGR012 Enquiries

F10=Copy record

Press F10 to copy the template to the new user profile.

*VA/480B* User profile table maintenance 12/01/14 11:57:56 ASGD9614
Enquiry program templates
-------------------------------------------------------------------------------
User profile........ KELSEYT
Template............ FIN
Description......... ASW Financial

F13 enquiry......... HLR126 Hotline incident enquiry
F14 enquiry......... DMC119A Purchase orders
F15 enquiry......... FKR015 A/R balance/stat/agreem/trans
F16 enquiry......... FKC090 A/R credit time axis
F17 enquiry......... DMC120 Sales orders
F18 enquiry......... DMR121 Invoices
F19 enquiry......... DMR122 Customer service
F20 enquiry......... GDMR273 Credit stop codes
F21 enquiry......... FLR015 A/P balance/stat/agreem/trans
F22 enquiry......... FMR015 Account file
F23 enquiry......... GDMR201 Names
F24 enquiry......... ASGR012 Enquiries

Key in the user profile, and press enter.

==Give User Additional Authority==

A manager can request extra access for their staff. For example, a secured option that people outside of finance need access to is invoice printing (for example, customer service and returns). There is a group profile for customer service, but other people have to be authorized individually.

Find the required option on a menu, and make note of the menu name, and option number (in this case, INVOICE and 1).

*VA/480B* Invoicing Tasks 1/16/15 14:51:09 INVOICE

Select one of the following: Application SoftWare
Release: XX1:480
1. Print invoices
2. Print invoice journal
3. Print cash sales journal
4. Release orders held for invoicing
5. Transfer logistic accounting transactions

Selection or command (C) IBS 1989-2002
===> ____________________________________________________________________

F3=Exit F4=Prompt F9=Retrieve F12=Cancel
F13=Information Assistant F16=System main menu

To find the name of the job, key in GO MEDEA and press enter.

*VA/480B* Menu Handling Tasks 1/16/15 14:23:47 MEDEA

Select one of the following: Application SoftWare
Release: XX1:480
1. Work with menu items
2. Work with menus
3. Display menu option

Selection or command (C) IBS 1989-2002
===> ____________________________________________________________________

F3=Exit F4=Prompt F9=Retrieve F12=Cancel
F13=Information Assistant F16=System main menu

Selection option 2 ‘Work with menus’, and position to the menu you want.

Work with Menus ASGD4501
Subset . . . . . . . . *ALL
Position to . . . . . INVOICE Starting characters

Type option (and Menu), press Enter.
1=Create 2=Revise 3=Copy 4=Delete 5=View 6=DW-Document 7=Rename
11=Move menu 14=Create Menu 15=Translate

Opt Menu Library Subset Description MEDEA

5 INVOICE *APP *STANDARD Invoicing Tasks YES
__ INVPER *APP *STANDARD Inventory Contol Periodical Tasks YES
__ INVREO *APP *STANDARD Inventory Control Reorganisation Ta YES
__ INVSET *APP *STANDARD Inventory Control Setup Tasks YES
__ INVSUPP *APP *STANDARD Internal Replenishment Tasks YES
__ ITEM *APP *STDDELTA Item Tasks YES
__ ITEM *APP *STANDARD Item Tasks YES
__ ITEMDEL *APP *STANDARD Item File Reorganisation Tasks YES
__ ITEMPRC *APP *STANDARD Item Pricing Tasks YES
__ ITEMTRAN *APP *STANDARD Item Information Transfer Tasks YES

F1=Shift info F3=Exit F5=Refresh F6=Create DW-document F8=Select subset
F9=Menu items - Where used F11=Display by desc F12=Cancel F13=Repeat

Use option 5 to view the menu, and press enter until you get to ‘View Menu Options’.

View Menu Options ASGD4522

Menu . . . . . . . . . . . . . . INVOICE
Library. . . . . . . . . . . . *APP
Subset . . . . . . . . . . . . . *STANDARD
Menu Description . . . . . . . . Invoicing Tasks
Type option, press Enter.
5=View 6=Print 8=X-ref

Op MO Menu item Subset Description
_ 1 DM340 *STANDARD Print invoices
_ 2 DM350 *STANDARD Print invoice journal
_ 3 DM365 *STANDARD Print cash sales journal
_ 4 DM308 *STANDARD Release orders held for invoicing
_ 5 CF750 *STANDARD Transfer logistic accounting transactions

F3=Exit F5=Refresh F12=Cancel

Make note of the job name DM340.

On an ASW command line, key in GO SECUR and press enter. Select menu option 3 – Work with authority groups. Select *MNUITM – Menu item control.

*PL/480B* Authority group table maintenance 12/02/14 16:20:09 ASGD2514
-------------------------------------------------------------------------------
Authority group..... *MNUITM
Description......... Menu item control
Active group........ Y

Object control pgm.. ASGR281

Default value....... 1

F7=Users F8=Routines F9=Objects F10=Details

Press F8 for objects.

*VA/480B* Authority group table maintenance 1/21/15 10:59:42 ASGD2531
Secured routines
-------------------------------------------------------------------------------
Authority group..... *MNUITM Menu item control
-------------------------------------------------------------------------------
Routine Description Secured
5 ASGR995 Check Menu item/Application Y

-------------------------------------------------------------------------------
Routine
___________

Select ‘ASGR995’, and press enter.

*VA/480B* Authority group table maintenance 1/21/15 11:00:48 ASGD2534
Secured routines
-------------------------------------------------------------------------------
Authority group..... *MNUITM Menu item control
-------------------------------------------------------------------------------
Routine............. ASGR995

Description......... Check Menu item/Application

Secured............. Y

F8=Routine aut per usr and obj

Press F8.

*VA/480B* Authority group table maintenance 1/21/15 11:02:05 ASGD2561
Routine authority per User and Object
-------------------------------------------------------------------------------
Authority group..... *MNUITM Menu item control
Routine............. ASGR995 Check Menu item/Application
-------------------------------------------------------------------------------
User Object Authority
_ ABDIE DM001 Y
_ AMANDAN DM340 Y
_ AMANDAY DM001 Y
_ ANGELAC GD001 Y
_ ANGELAC GL040 Y
_ BOBW DM340 Y
_ BRANDONS DM340 Y
_ CAMILLED DM340 Y
_ CARLOSD DM340 Y
_ CELSOC DM340 Y
_ CHARLENEH DM340 Y
_ CHARLESN AP410 Y
-------------------------------------------------------------------------------
User Object Authority
__________ ______________________________ _

You can press F6 to add.

*VA/480B* Authority group table maintenance 1/21/15 11:45:32 ASGD2564
User authority per routine and object
-------------------------------------------------------------------------------
Authority group..... *MNUITM Menu item control
Routine............. ASGR995 Check Menu item/Application
-------------------------------------------------------------------------------
User................ KELSEYT
Object.............. DM340
Authority........... Y

* Don’t forget ‘Y’ for authority.

Or you can position to either a ‘user’ or an ‘object’.

*VA/480B* Authority group table maintenance 1/21/15 11:47:52 ASGD2561
Routine authority per User and Object
-------------------------------------------------------------------------------
Authority group..... *MNUITM Menu item control
Routine............. ASGR995 Check Menu item/Application
-------------------------------------------------------------------------------
User Object Authority
AMANDAN DM340 Y
BOBW DM340 Y
BRANDONS DM340 Y
CAMILLED DM340 Y
CARLOSD DM340 Y
CELSOC DM340 Y
CHARLENEH DM340 Y
CHRISCH DM340 Y
CSRGRP DM340 Y
DOMERL DM340 Y
FIN1 DM340 Y
FIN2 DM340 Y
-------------------------------------------------------------------------------
User Object Authority
__________ DM340_________________________ _

*VA/480B* Authority group table maintenance 1/21/15 11:47:52 ASGD2561
Routine authority per User and Object
-------------------------------------------------------------------------------
Authority group..... *MNUITM Menu item control
Routine............. ASGR995 Check Menu item/Application
-------------------------------------------------------------------------------
User Object Authority
CHRISTINED AP410 Y
CHRISTINED CF400 Y
CHRISTINED GF460 Y
CHRISTINET AP410 Y
CHRISTINET CF400 Y
CHRISTINET DM001 Y
CHRISTINET GF457 Y
CHRISTINET GL030 Y
CHRISTINET GL032 Y
CHRISTINET GL040 Y
CSRGRP DM340 Y
-------------------------------------------------------------------------------
User Object Authority
CHRISTINED _________________________________________ U

Information Systems:ASW User Security

2015-10-20T23:49:51Z

172.30.20.117:

Information Systems:ECU - Description

2015-10-20T23:47:08Z

172.30.20.117: Blanked the page

Information Systems:ECU - Electronic Catalog Update

2015-10-20T23:47:04Z

172.30.20.117: Created page with "uniPHARM used to supply a PC program called EOB (Electronic Order Book) to customers. Every week, ECU would build a file of changes to the item master file (one for each pric..."

uniPHARM used to supply a PC program called EOB (Electronic Order Book) to customers. Every week, ECU would build a file of changes to the item master file (one for each price list, as the prices would be different for each), and email them to ?. We no longer have the EOB, but we continue building change files and full catalogues every week for the POS systems, and for Web Orders.

- CL program ECUWEEKLY (weekly Electronic Catalog Update) runs from the Job Scheduler every Thursday at 9:30PM. It runs –

- Command ECUREGULAR calling auto run ‘WEEKLYCAT’. It builds a file of changes the item file in the last week, for each price list (because they will each have different prices). These files are emailed to pre-set addresses, and sent to our FTP server. It also builds a change file that can be accessed by Web Orders.

- Command ECUFULLCAT calling auto run ‘ECUFULLCAT’ for each price list.

- Program ECRUP385 (ECU -- Generate and send full catalog files) calls ECCUP380 for each catalogue built by ECUFULLCAT. ECCUP380 send these catalogues to the FTP server.

- File ECUIBAP (ECU -- Item Base File) contains all the fields (except prices) included in the catalogue and change files, for every week this is run.

- File ECUIBPP (ECU -- Item Base Price File) contains all the item prices for every week this is run.

- File ECUCHGP (ECU -- Catalog Changes File) contains all the items that have had any changes in ECUIBAP, from one week to the next.

- File ECUCHPP (ECU -- Catalog Price Changes File) contains all the items that have had any changes in ECUIBPP, from one week to the next.

- File ECUOMDP (ECU -- Message Lines File) are the change and full catalogue files reformatted.

- File ECUOMHP (ECU -- Message Headers) header for each change and full catalogue file that has been add to ECUOMDP.

Information Systems:EMS - Description

2015-10-20T23:46:15Z

172.30.20.117: Blanked the page

Information Systems:EMS - Error Management System

2015-10-20T23:46:12Z

172.30.20.117: Created page with "These are custom messages used by the extensions. - File EMSMSGP (EMS - Message Control Header) is the error code, description, text, and list of parameters. - File EMSAC..."

These are custom messages used by the extensions.

- File EMSMSGP (EMS - Message Control Header) is the error code, description, text, and list of parameters.

- File EMSACTP (EMS - Message Actions) tells whether the response to an error is to send an email, or add a record to the alert file (EMSALRP).

- File EMSADDP (EMS - Email Addresses) contains the addresses if the action in EMSACTP is to send an email.

- File EMSALRP (EMS - User Alert History) is written if the action in EMSACTP is to write to the alert file.

- Program EMRUP010 (EMS - Handle an Error API) is called by any program needing to send an alert. Based on the error code and parameters received, it will perform the actions defined in the EMS files.

Information Systems:ECU - Description

2015-10-20T23:44:19Z

Information Systems:EMS - Description

2015-10-20T23:43:10Z

Information Systems:STM - Statements

2015-10-20T23:40:56Z

172.30.20.117: Created page with "ASW does open item statements; we wanted to do balance forward as well. Also we do statements twice a month. The statement files keep history, so any statement can be reprin..."

ASW does open item statements; we wanted to do balance forward as well. Also we do statements twice a month.

The statement files keep history, so any statement can be reprinted. Statements can also be regenerated at any time. The program uses the settlement file to determine transaction balances as of any statement date. The opening balance of a statement is the closing balance of the previous statement. If a transactions is entered that should have printed on a previous statement (or a date is changed), then the opening balance will be incorrect. We will know this, because after the statement file is generated, but before it is printed we compare the totals to ASW. The fix for this is to regenerate the statement that should have had the new or changed transaction, and every statement since.

It was taking longer and longer to generate the statement file – up to three hours. The reason was that the balance forward statement generation program (ARRST002) was calculating the remaining balance of each transaction (all the way back to January 29, 2005) before deciding whether or not to show it on the statement (transactions due to be settled within the next 15 days). November 2013 this was changed to determine the remaining balance only for transactions to be included on the statement.

The open item statement generation program (ARRST003) was also calculating the remaining balance of each transaction back to January 29, 2005 to determine whether or not it should be on the statement (which is every transaction with an outstanding balance). In November 2013, this program was changed to start looking at January 2009, as the oldest outstanding transaction was in 2009.

Now it takes about 10 to 20 minutes for balance forward statements, and 5 to 10 minutes for open item; depending on how busy the system is. The change to the balance forward statements made the biggest impact, as they include all shareholders, and so is by far the largest volume of transactions.

- File ARSTTYP (STM - Customer Statement Format Types) tells which type if statement each customer gets.

- File ARSTHDP (STM - Statement Header File) is the name, address, date, and totals for each statement created.

- File ARSTBAP (STM - Statement Balances File) contains statement section totals, ie. for Invoices, credit notes, payments, etc).

- File ARSTLIP (STM - Statement Lines File) is the information for every transaction on the statement. (Note that for ‘open item’ it will contain all open transactions as of the statement date. For ‘balance forward’ it will be all transactions due within the next statement period – if they were due in the current statement period they would already be overdue.)

- Program ARRST002 (STM - Create Statement Records - Balance Forward).

- Program ARRST003 (STM - Create Statement Records - Open Item).

- Program ARRST051 (STM - Print Statement).

Information Systems:System i Operations

2015-10-20T20:36:44Z

172.30.20.117:

This computer has had several different names. They may be used interchangeably here, and when looking up information on the internet. The names are AS/400, iSeries, System i, and just plain i.

* [[Command Line]]
* [[Library List]]
* [[Menus]]
* [[Commands]]
* [[Print (or Spool) Files]]
* [[Jobs]]
* [[Data Files]]
* [[HMC HardWare Management Console]]
* [[System Messages]]