Return-Path: Delivered-To: louk@transocean.com Received: from vps.transocean.com by vps.transocean.com with LMTP id IMTANwCyplriFgAAInt2oQ for ; Mon, 12 Mar 2018 09:59:44 -0700 Return-path: Envelope-to: louk@transocean.com Delivery-date: Mon, 12 Mar 2018 09:59:44 -0700 Received: from smtp72.ord1c.emailsrvr.com ([108.166.43.72]:33757) by vps.transocean.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1evQnQ-0001W4-8z for louk@transocean.com; Mon, 12 Mar 2018 09:59:44 -0700 Received: from smtp18.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp18.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 1A96BE048F; Mon, 12 Mar 2018 12:58:56 -0400 (EDT) X-Auth-ID: helpdesk@robocom.com Received: by smtp18.relay.ord1c.emailsrvr.com (Authenticated sender: helpdesk-AT-robocom.com) with ESMTPA id 98880E05C3; Mon, 12 Mar 2018 12:58:55 -0400 (EDT) X-Sender-Id: helpdesk@robocom.com Received: from robocom.com ([UNAVAILABLE]. [216.157.93.243]) by 0.0.0.0:25 (trex/5.7.12); Mon, 12 Mar 2018 12:58:56 -0400 Message-ID: <380-220183112165848402@robocom.com> Message-ID: From: "Robocom Support" To: mike@transocean.com Cc: arodriguez@robocom.com, gmuhleisen@robocom.com, louk@transocean.com, zarko@transocean.com Subject: RE: (Incident ID# P24-21112) Another Order with NO EDI Data (2841315)!!!! [161361] Date: Mon, 12 Mar 2018 12:58:48 -0400 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 X-Spam-Status: No, score=0.7 X-Spam-Score: 7 X-Spam-Bar: / X-Ham-Report: Spam detection software, running on the system "vps.transocean.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see root\@localhost for details. Content preview: Mike, UTILS checks and if necessary, repairs the indexes on the tables in the database. I have moved the UTILS program to run at 20:45 on Saturday instead of Sunday. User Sandy appears to be on the system on Sunday's evening. [...] Content analysis details: (0.7 points, 3.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: transocean.com] 1.5 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail) 0.7 MIME_HTML_ONLY BODY: Message only has text/html MIME parts -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 HTML_MESSAGE BODY: HTML included in message 0.4 HTML_MIME_NO_HTML_TAG HTML-only message, but there is no HTML tag X-Spam-Flag: NO Mike,
           UTILS checks and if necessary, repairs the indexes on the tables in the database.
           I have moved the UTILS program to run at 20:45 on Saturday instead of Sunday. User Sandy appears to be on the system on Sunday's evening.

Robocom Support

>>>On 03/12/2018, you wrote:

Hello Robocom Team!


Thanks for your thorough and detailed follow up and resolution. Two questions:


  1. What does “UTILS” do?
  2. Since it appears that UTILS takes just over a half hour to run could we not just reschedule it to run at 20:45hrs thereby avoiding any conflict between it and XAUTOEDI?


We can have our user to time their Sunday night sessions so they do not conflict with the running of either of these CRONS.


Please advise. Thanks!


< p class="MsoNormal">Mike Toone

EDI Coordinator

Trans-Ocean Imports

10 Midland Avenue |Suite M00| Port Chester, NY 10573

914.949.5656 x149 | 914.937.3140 fax

 

Confidentiality Notification: If you are not the intended recipient, please do not disclose, disseminate, copy, distribute or take any action in reliance on the contents of this electronic transmission.  If you have received this electronic transmission in error, please notify us by telephone and immediately delete this message. As E-mail transmissions cannot be guaranteed secure or error-free the sender does not accept any liability for errors or omissions in the contents of this message, which arise because of electronic transmission. Any documents accompanying this electronic transmission and the information contained herein belong to the sender and are privileged and intended only for the use of the individual(s) named above.


From: Robocom Support [mailto:helpdesk@robocom.com]
Sent: Sunday, March 11, 2018 8:01 PM
To: mike@transocean.com
Subject: (Incident ID# P24-21112) Another Order with NO EDI Data (2841315)!!!!


Support has updated the Web Conversation related to your ticket listed above. Click on the link provided below for access to your ticket in the customer portal.
https://robocom.devsuite.net/scripts/texcel/customerwise/clogin.dll?cqedit?%7BEjkykjipxfgfxieedd

[Last Support Response]:

<Support Response>: by Alla n Rodriguez, 3/11/18 20:01:00
[Allan Rodriguez -- 3/11/18 20:01:00]
Allan,

We believe the problem is a conflict between UTIL and the EDI Process that could occur on Sunday evenings when UTIL is scheduled to run.

There was an mis error that occurred during the Order Creation where the ship to table was locked.
***** Following Error From User: zarko *****
Date: 03/04/2018 Time: 21:30:35
Program error at "order3.4gl", line number 148.
SQL statement error number -242.
Could not open database table (infor400.shipto).
SYSTEM error number -113.
ISAM error: the file is locked.

In examining Trans Ocean’s system, util was running at the same time as xautoedi:
Fri Mar 9 2018 TRANS-OCEAN IMPORT CO., INC. Page 1
12:08:36 PROGRAM AUDIT VIEW PGCR
Sort By Start Date

Program Called By C User ID Terminal Start Date/Time End Date/Time
--------------------------------------- ----------------------------------------
xautoedi miscron C miscron 03/04/2018 00:30:00 03/04/2018 00:30:01
xautoedi miscron C miscron 03/04/2018 01:30:01 03/04/2018 01:30:12
xautoedi miscron C miscron 03/04/2018 06:30:00 03/04/2018 06:32:21
xautoedi miscron C miscron 03/04/2018 07:30:01 03/04/2018 07:30:16
xautoedi miscron C miscron 03/04/2018 08:30:01 03/04/2018 08:30:24
xautoedi miscron C miscron 03/04/2018 09:30:01 03/04/2018 09:30:09
xautoedi miscron C miscron 03/04/2018 10:30:00 03/04/2018 10:30:18
xautoedi miscron C miscron 03/04/2018 11:30:00 03/04/2018 11:30:04
xautoedi miscron C miscron 03/04/2018 12:30:01 03/04/2018 12:30:10
xautoedi miscron C miscron 03/04/2018 13:30:00 03/04/2018 13:30:09
xautoedi miscron C miscron 03/04/2018 14:30:00 03/04/2018 14:30:00
xautoedi miscron C miscron 03/04/2018 15:30:00 03/04/2018 15:30:22
xautoedi miscron C miscron 03/04/2018 16:30:00 03/04/2018 16:30:00
xautoed i miscron C miscron 03/04/2018 17:30:00 03/04/2018 17:30:16
xautoedi miscron C miscron 03/04/2018 18:30:00 03/04/2018 18:30:00
xautoedi miscron C miscron 03/04/2018 19:30:00 03/04/2018 19:30:00
xautoedi miscron C miscron 03/04/2018 20:30:00 03/04/2018 20:30:00
util miscron C miscron 03/04/2018 21:00:00 03/04/2018 21:34:19
xautoedi miscron C miscron 03/04/2018 21:30:01 03/04/2018 21:30:55
xautoedi miscron C miscron 03/04/2018 22:30:00 03/04/2018 22:30:17
armeage miscron C miscron 03/04/2018 23:00:00 03/04/2018 23:02:36
xautoedi miscron C miscron 03/04/2018 23:30:00 03/04/2018 23:30:18

Since XAUTOEDI runs every hour, there is no time that we can run util and guarantee it will not impact xautoedi (or other programs being executed since they also had other users running things on Sunday night around the same time where util could cause a problem.
menu W sandy 2 03/04/2018 18:41:12 03/04/2018 20:38:04
xediinm menu W san dy 2 03/04/2018 18:42:30 03/04/2018 19:10:41
im menu W sandy 2 03/04/2018 18:51:12 03/04/2018 18:51:22
xpomntu miscron C miscron 03/04/2018 18:55:00 03/04/2018 18:55:12
cm menu W sandy 2 03/04/2018 18:59:41 03/04/2018 18:59:45
xpomntu miscron C miscron 03/04/2018 19:10:00 03/04/2018 19:21:00
c1 menu W sandy 2 03/04/2018 19:10:33 03/04/2018 19:11:42
xsdte order W sandy 2 03/04/2018 19:11:05 03/04/2018 19:11:05
xediinm menu W sandy 2 03/04/2018 19:11:15 03/04/2018 19:11:27
c8 menu W sandy 2 03/04/2018 19:11:44 03/04/2018 19:12:39
c1 menu W sandy 2 03/04/2018 19:12:41 03/04/2018 19:13:06
xsdte order W sandy 2 03/04/2018 19:13:05 03/04/2018 19:13:05
xediinm menu W sandy 2 03/04/2018 19:13:09 03/04/2018 19:35:19
xautoedi miscron C miscron 03/04/2018 19:30:00 03/04/2018 19:30:00
xediinm menu W sandy 2 03/04/2018 19:35:30 03/04/2018 19:41:42
xpmt menu W sandy 2 03/04/2018 19:40:50 03/04/2018 19:42:16
xediinm menu W sandy 2 03/04/2018 19:42:21 03/04/2018 19:57:33
iqq menu W sandy 2 03/04/2018 19:51:09 03/04/2018 19:55:28
xediinm menu W sandy 2 03/04/2018 19:57:40 03/04/2018 20:06:25
xediin menu W sandy 2 03/04/2018 20:08:45 03/04/2018 20:08:48
xediinm menu W sandy 2 03/04/2018 20:08:50 03/04/2018 20:09:08
c9 menu W sandy 2 03/04/2018 20:10:01 03/04/2018 20:10:33
c1 menu W sandy 2 03/04/2018 20:10:45 03/04/2018 20:20:41
xa order W sandy 2 03/04/2018 20:12:04 03/04/2018 20:12:11
xcpgu order W sandy 2 03/04/2018 20:12:04 03/04/2018 20:12:04
xsdte order W sandy 2 03/04/2018 20:13:23 03/04/2018 20:13:23
xa order W sandy 2 03/04/2018 20:15:50 03/04/2018 20:15:53
xcpgu order W sandy 2 03/04/2018 20:15:50 03/04/2018 20:15:50
xsdte order W sandy 2 03/04/2018 20:16:09 03/04/2018 20:16:09
xa order W sandy 2 03/04/2018 20:17:30 03/04/2018 20:17:37
xcpgu order W sandy 2 03/04/2018 20:17:30 03/04/2018 20:17:30
xsdte or der W sandy 2 03/04/2018 20:18:11 03/04/2018 20:18:11
xa order W sandy 2 03/04/2018 20:19:47 03/04/2018 20:19:50
xcpgu order W sandy 2 03/04/2018 20:19:47 03/04/2018 20:19:47
xsdte order W sandy 2 03/04/2018 20:20:06 03/04/2018 20:20:06
xediinm menu W sandy 2 03/04/2018 20:20:56 03/04/2018 20:35:52
xautoedi miscron C miscron 03/04/2018 20:30:00 03/04/2018 20:30:00
cm menu W sandy 2 03/04/2018 20:33:37 03/04/2018 20:33:41
xediinm menu W sandy 2 03/04/2018 20:35:56 03/04/2018 20:36:01
c1 menu W sandy 2 03/04/2018 20:37:32 03/04/2018 20:38:02
xsdte order W sandy 2 03/04/2018 20:38:00 03/04/2018 20:38:00
util miscron C miscron 03/04/2018 21:00:00 03/04/2018 21:34:19

Gary suggests that util could be turned off so it will not run from miscron.

We executed a script ($CUSTOMPROGS/scripts/xedimiss.sql) to report any trading partner/customer po number combinations with a system date greater than 1/1/18 in XEDINHT where the record exists in INVB (indicating the order was created and billed) but does not exist in XEDINH or XINVC (indicating that the corresponding EDI portion does not exist). The following transactions were reported. All of these occurred on a Sunday during the 9:30 PM execution; we surmise that util may be impacting this without generating an mis_error depending on how the code addresses the issue.

partnrid_xedinht cust_po_xedinht sysdate_xedinht
TGTDVS 1404909133 02/04/2018
Z112084681A CA106302628 02/25/2018
TGTDVS 1412925821 03/04/2018

We also verified that there were no trading partner/customer po number combinations with a system date greater than 1/1/18 in XEDINHT where the record exists in ORDERB (indicating the order was created) but does not exist in XORDERC (indicating that the corresponding EDI portion does not exist). The following transactions were reported but both of them were successfully billed with different order numbers (2831699 and 2831712); these orders (2831729,2831730) must have been manually entered.

partnrid_xedinht cust_po_xedinht sysdate_xedinht Original Order Billed with EDI Exisiting Order Without EDI
TGTDVS 1401993259 01/24/2018 2831699 2831730
TGTDVS 1402147052 01/25/2018 2931712 2831729