Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
S/36 commands 1
- Thread starter quadrapet
- Start date
- Thread starter
- #3
Yes, I know how to do that...
Here's the problem
I was working on a DATE command to display the date in your session window in native environment, and now the DATE command in s/36 mode has stopped working. I can only assume the command I created with the same name in in native mode has somehow affected the date command in 36 mode, so I want to know where on the system the 36 procedures for those commands are actually stored so I can determine if this is true or not.
Oddly enough, I did the same thing with the time command and it caused no problem.
I created a time command in native mode and it works fine, and the time command in 36 mode still does it's thing no problem.
So I'm kind of in a pickle here....
Here's the problem
I was working on a DATE command to display the date in your session window in native environment, and now the DATE command in s/36 mode has stopped working. I can only assume the command I created with the same name in in native mode has somehow affected the date command in 36 mode, so I want to know where on the system the 36 procedures for those commands are actually stored so I can determine if this is true or not.
Oddly enough, I did the same thing with the time command and it caused no problem.
I created a time command in native mode and it works fine, and the time command in 36 mode still does it's thing no problem.
So I'm kind of in a pickle here....
-
1
- #4
I heard a story once about a S/36 guy who created a procedure to dial out for remote support. He named it CALL. Of course, this cause chaos on the AS/400 it was ported to...
You need to rename one of them.
"When once you have tasted flight, you will forever walk the Earth with your eyes turned skyward, for here you have been, and there you will always long to return."
--Leonardo da Vinci
You need to rename one of them.
"When once you have tasted flight, you will forever walk the Earth with your eyes turned skyward, for here you have been, and there you will always long to return."
--Leonardo da Vinci
abacuscorp
Programmer
quadrapet
A work-around may be to create a procedue in #LIBRARY named date that could look like the following:
// * 'today is ?date?'
// pause
Warren
A work-around may be to create a procedue in #LIBRARY named date that could look like the following:
// * 'today is ?date?'
// pause
Warren
- Thread starter
- #6
I solved this problem so here's the answer
I had created a command named 'DATE' to run in native mode and it was stored in the qs36prc lib. Apparently the system checks that library before qsys when running a system command in 36 mode, so it was trying to call my procedure, which I hadn't even finished writing.
I renamed the object and the problem was solved...
LESSON:
Unless you have a great reason to name a command the same as an IBM supplied command, DONT DO IT =)
I had created a command named 'DATE' to run in native mode and it was stored in the qs36prc lib. Apparently the system checks that library before qsys when running a system command in 36 mode, so it was trying to call my procedure, which I hadn't even finished writing.
I renamed the object and the problem was solved...
LESSON:
Unless you have a great reason to name a command the same as an IBM supplied command, DONT DO IT =)
- Status
Similar threads
- Locked
- Question
- Locked
- Question