Well, if you've found out anything while being an EnterpriseOne CNC person, it's that E1 is confusing. Oh, maybe if you have a really simplified install, it might not be too bad. But, overall it is confusing.
The problem is it isn't just confusing for us tech-types but also for the end users and implementation teams. In order to relieve the confusion of not knowing which environment you are in I did a little bit of image editing:
The image is located at ..\webclient.war\share\images\jdelogo-onwhite.gif
[+/-] Read More...
[+/-] Summary only...
I am not an iSeries expert...
However, since we use the iSeries for our E1 Enterprise Server I am required to use it more than I ever wanted to. Anyway, I have been doing some experimenting with the XML Kernel jobs that get started up, when one of the kernel jobs did not end when I issued the endnet command. So, I used wrkactjob and issued an endjob command with *IMMED. Well, after waiting a while it didn't end. After about 30 minutes of trying other things and talking to our resident iSeries guru, I gave up and left for the day.
I got in this morning to find the jobs still "ending". So, I did some looking through Google and found another command that I could try ENDJOBABN (End Job Abnormal).
Info from an article on ITJungle.com:
ENDJOBABN JOB(999999/USER/JOBNAME)ENDJOBABN has been known to take down jobs that are too stubborn for ENDJOB. But it has a few limitations that you need to be aware of. Specifically, the following things affect ENDJOBABN use:
ENDJOBABN cannot be run against a job before you've attempted to end the job through the ENDJOB command, with *IMMED specified in the "how to end" parameter. OS/400 is also hard-coded to ignore an ENDJOBABN statement until 10 minutes have passed since you ran an ENDJOB *IMMED command on the same job. So not only do you have to run ENDJOB for a problem job before using ENDJOBABN, you also have to give ENDJOB time to work.
ENDJOBABN is shipped with *PUBLIC *EXCLUDE authority. And to run ENDJOBABN, you need job control (*JOBCTL) authority in your user profile.
ENDJOBABN can be run against a job only once. Additional ENDJOBABN commands can't be run.
[+/-] Read More...
[+/-] Summary only...
Well, maybe not nice...but "Fine".
In working with our users we have found that they take advantage of the menu filtering, which is referred to as "Fine Cut". Moving these from one environment to the next can be done through OMW or by copying some files. For us, it has been easier just to copy the files.
Here they are:
F9000-Task Manager
F9001-Task Relationships
F9002-Task Alternate Descriptions
F9005-Variant Description
F9006-Variant Detail
Have Fun!
[+/-] Read More...
[+/-] Summary only...
Now these are AWESOME!
We have been using just 2 of the tools that Alexander Pastuhov has available.
What are those 2 products?
- Boomerang
- We have 2 separate instances for 2 different business units so we use Boomerang to quickly and easily transfer objects from one to the other. It's a VERY slick product. In a previous installation of OneWorld Xe we created data sources and transfer activity rules to accommodate this need, but with Boomerang we were able to keep our installation as vanilla as possible.
- Update Queue Names In Versions
- Yeah, it's a long name, but man is it a time saver. When you consider the time that it would take you to change the job queue in the hundreds of versions that we had to split up our batch processing, it probably saved a good week of tech time.
Thanks Alex for providing such easy to use specialized products!
[+/-] Read More...
[+/-] Summary only...
I ran into an issue the other day...
One of our developers had a few objects that he wanted deleted. So, I went to OMW and was able to delete all of the objects...except one (a "P" object). I did everything:
- I deleted it locally
- I deleted it from the SAVE location
- I marked it to delete from transfer locations and then promoted it all the way to a 38 and back to a 21
Finally, I figured maybe I could just delete it from the database...
NOT A GOOD IDEA!!!!
After a bunch of digging in all our developer's projects, I found that there were 3 versions of that object that had been created. I deleted the versions and was then able to delete the object.
How FRUSTRATING!!!!!! You would think that that would be a fairly simple error message to display:
[+/-] Read More...
[+/-] Summary only...
Don't worry, this still is not a dating service!
My last post dealt with dates in E1. Well, there is another way that dates are stored...
The number of seconds since January 1, 1970.
This isn't too uncommon in programming languages such as C++, but it sure is a pain in the rear-end when looking in a database.
I have included a conversion tool on my
E1 Dates page.
***NOTE: the dates calculation page has been updated***
[+/-] Read More...
[+/-] Summary only...
No this is not a dating service!
Today we will cover the proprietary date format that is used in most of the files in E1.
Well, let's just dive in...
Today's date is 4-5-2007. In E1-land that is 107095.
Here's the breakdown:
- E1 Date: 107095
- Year: 1900 + 107 = 2007
- Date: 095
- The 95th day of the year (2007) = April 5th
- Complete Date: April 5th 2007
Hey! What about the time?
- E1 Time: 90154
- E1 Time: 210154
Here is a page I put together that uses javascript to retrieve the dates.
[+/-] Read More...
[+/-] Summary only...
(Atom)