This is a general warning about using the CHGCMDDFT command to change the default value of command parameters for commands in QSYS.
There are a number of reasons not to change parameter defaults on commands in QSYS…
Any time you upgrade your systems, those default parameter changes will be lost because the commands are completely replaced.
Although you can identify what commands have had parameter defaults changed, there is no indication of WHAT parameter defaults were changed on a command. To identify what commands have had defaults changed display the command objects description (DSPOBJD) with DETAIL(*SERVICE). If an object has had the parameter defaults changed, the APAR ID will show ‘CHGDFT’.
Third party products may be expecting commands to have the IBM provided default values. Because 3rd party products usually have to work on a number of IBM i versions, it’s impossible for vendors to specify a specific value for every parameter. New parameters are added with almost every release.
A Better Approach
A better approach would be to create a library to hold copies of the commands you want to modify …
Create a specific library to hold customized commands
Add that library to the QSYSLIBL system value above QSYS
Duplicate the *CMD objects into that library
Change the default parameter values on the commands in that library.
This way the commands in QSYS are left with the IBM provided default parameter values. Since the custom command library is above QSYS in the system library list, applications that reference those command (that don’t qualify the command to QSYS), will use the modified command.
I like to create a simple CL program that does the work of deleting existing commands from the custom command library, duplicate the command from QSYS, and modifies the command parameter defaults. Not only does this make it easy to recreate the custom command parameter defaults when you do an OS upgrade, it documents what parameter defaults have been made.
You may be tempted to use the CRTPRXCMD to create a ‘proxy command’, that points to the original command, and change the defaults on the proxy command.
DO NOT DO THAT!
A proxy command isn’t a stand alone object that is independent of the actual command. It’s just a pointer to the real command.
Any real changes you make to a proxy command will actually be made on the real command.
Here’s a very simple example of a CL that will repopulate a custom command library with modified default parameter values.
Many of us who manage websites are familiar with Google’s ‘Search Console‘. The search console is a way for webmasters to manage how Google interacts with our web sites. It provides functions to tell Google what parts of the site to search, what parts to ignore, and determine what pages are doing better than others.
One of the functions it provides is a way to see what parts of a web site that Google has indexed and what part it hasn’t. It also can tell what parts of a site it is ignoring and, to a certian extent, why it’s ignoring them.
One of the reasons that Google might be ignoring a page is because it’s been to be determined to be a ‘Soft 404’.
What’s a Soft 404 error?
Well, a REAL 404 error is a page not found. It’s a function of the web server software. Most web servers provide the ability to use a custom page when a 404 error is encountered. You can see an example of one here.
As for a ‘Soft 404’ … according to Google …
A soft 404 means that a URL on your site returns a page telling the user that the page does not exist and also a 200-level (success) code to the browser.
While some sites might actually do that … handle a page not found error with a friendly page but indicate to the browser that it’s a normal page (200 status code) … I suspect it’s actually a minority of sites (granted, it may be a way to game the system).
However … it turns out that pages that contain the words ‘not found’, ‘error’, ‘authorized’, ‘not allowed’, etc., in the title or body are often treated by Google as a soft 404 error … even if the page isn’t a 404 at all. Additionally, the words do not even need to appear on the page at all. The details of what constitutes a ‘soft 404’ are very mysterious.
We all agree that email is crucial to modern life.
But what email should you use?
Everyone gets email when they sign up for high speed internet service … the problem is that you’re tied to that internet service for that email address. If you switch service providers, you could lose the address. Even worse, if your provider goes out of business, you could loose access entirely. Sometimes the email provider charges a fee for better service and/or removing advertising.
Yes, you could use Gmail, Hotmail, Yahoo, or AOL, but you’re still tired to the provider. Plus, you don’t often get to choose the best address (email@example.com just isn’t that sexy).
Wouldn’t it be nice if you could get an email address that belongs to you forever?
As part of my migration to the cloud, I terminated the Comcast Business internet service and switched to Xfinity internet.
When I initially signed up for the Xfinity service, I got their cable modem / router / wifi appliance. My plan was to get my own cable modem eventually because Xfinity charges $13 / month to lease the appliance.
I was at Best Buy and saw that cable modems weren’t expensive, so I decided to purchase a mid-level model (Netgear CM600) so I could save the lease fee. The CM600 would pay for itself in about 8 months.
It took a while to get setup … and there were a few false starts, but eventually I got it working connected directly to my MacBook.
I ran into a problem when I switched the CM600 over to my ASUS RT-5300 wifi router.
I kept getting the message “Your ISP’s DHCP does not function properly” on the ASUS network map page.
Our area has never gotten good cell phone coverage. Doesn’t really mater what carrier we used … AT&T or Verizon.
When AT&T announced that it was going to be making “MicroCells” available, I decided to get one … as it would help our cell phone coverage.
The MicroCell has been working fine for more than a year … but, all of a sudden (or so it seemed), it stopped working correctly.
I contacted AT&T and they tried a few things and asked me to try cycling power (unplugging it and plugging it back in). Nothing worked. I asked them to check to see if it was still under warranty … it wasn’t.