Messages

1771

Report Indexing / Re: Help! Moving Field

« on: November 01, 2011, 12:47:06 PM »

Please excuse my ignorance, but what do you mean by ?building a utility??

I'd write some software to correct the problem with Perl, sed, awk, or any other available scripting/programming language.  That obviously depends on your platform, and what tools are available to you.

Having said that, Larry's solution is probably best - defining a wider-than-necessary field, then stripping additional spaces from before or after the value you want.

1772

Report Indexing / Re: Help! Moving Field

« on: November 01, 2011, 04:48:40 AM »

Hi Douglas.

In situations where there are data-quality issues, I normally push back to the provider of the data to correct their problem.  Where that isn't possible, I usually end up building a utility to correct the issue.

I'd simply search for "Claim Number:  " (with two spaces) and replace it with the same string, minus the rightmost space.

-JD.

1773

Announcements & News / Re: Should we create a LinkedIn Group?

« on: October 30, 2011, 12:58:42 PM »

It will likely just be in addition to the forums.  The Forums here will always be the official ones -- but some members may find using the LinkedIn system more convenient.

1774

Announcements & News / Should we create a LinkedIn Group?

« on: October 27, 2011, 09:50:28 AM »

We're considering creating and maintaining a LinkedIn Group, which may be more convenient for some users.  What do you think?

1775

Other / Re: Misssing Tapes in TSM

« on: October 22, 2011, 08:27:35 AM »

Audit the library, followed by a checkin libvol.  Tape operations will be slow during this process, obviously.

1776

MP Server / Re: I can not delete a document using the unload command

« on: October 07, 2011, 05:52:54 AM »

Is your default instance name 'archive'?

If you've changed the default instance name, you must use the -I option with the name of the instance.

-JD.

1777

Other / Re: Deleting documents in specific load using search

« on: September 15, 2011, 06:17:53 AM »

Hi.

You can use SQL to specify a portion of the load ID.  If you get a load ID that includes an object ID of 1234FAA, then you can include it in your SQL selection criteria (along with, say, customer number) like this:
   doc_name like '1234FAA%' and cust_num = 987654321

I know that sounds brief and cryptic, but it's a push in the right direction.  Let us know if you have more questions.

1778

MP Server / Re: Problem when performing online backup

« on: September 08, 2011, 06:09:57 AM »

Sounds like your database is still very busy at the time you're backing up.  Stopping user access and loading is recommended.

Here's the documentation for an SQLCODE -912:

The maximum number of lock requests has been reached for the database.
Explanation:

The maximum number of locks for the database was reached because insufficient memory was allocated to the lock list.

The statement cannot be processed.
User response:

The application should submit a COMMIT or ROLLBACK statement before submitting other SQL statements. Consider increasing the database configuration parameter ( locklist) to allow more lock list space.

1779

z/OS Server / Re: PDF problem

« on: August 25, 2011, 04:13:14 PM »

Try expanding the borders of your triggers and fields by 0.1.

-JD.

1780

Other / Re: Creating a Copygroup

« on: August 24, 2011, 06:35:25 AM »

Hi Russell.

I fail to see where the disparity is.  You didn't provide the output of the q copygroup command from the second server.

Without getting too deep into TSM, a policyset (of which copygroup is a component), once defined, needs to be activated.  Once activated, it appears as 'active', as you can see in your output.  If none of the components of the policyset have changed, then the policyset is identical to the activated one.

-JD.

1781

MP Server / Re: ACIF Input Exit to insert new data in an AFP file

« on: August 22, 2011, 07:45:53 PM »

You may be able to use new features of arsload to use the name of the file (or portions of it) as index values.  Can you achieve what you need with this?

-JD.

1782

MP Server / Re: Archive Retention (Grace Period):

« on: August 17, 2011, 03:24:00 PM »

If the archive retention in TSM is set for 365 days, you're not storing stuff for 7 years, you're storing for 1 year.

Rule of thumb, 7 year retention is 2557 days, 10 year retention is 3653 days.  Both numbers include the maximum number of leap-days possible.

-JD.

1783

Other / Re: ARS1128E during arsdoc get & arsload in AIX

« on: August 17, 2011, 03:19:57 PM »

The problem is that the column you're extracting has a delimiter in it -- likely an invisible tab character that you can't see in your favourite text editor. 

Also, extracting all these documents at once is a Bad Idea.  If your AG is configured to expire by load (the default), the earlier documents won't expire until the LAST document expires.

-JD.

1784

z/OS Server / Re: EoS Announced for CMOD 8.4.0 and 8.4.1: April 30, 2013

« on: August 03, 2011, 10:10:34 AM »

To our multiplatform users, I haven't seen an EoS announcement for 8.4.x or 8.4.1 yet.

1785

Other / Re: Does OD support storing encryted documents?

« on: July 26, 2011, 08:55:58 AM »

Hi Curtis.

Just as a follow up, data in the cache and TSM is stored with a proprietary compression method.  Even an advanced user with non-CMOD-specific knowledge would have difficulty in successfully decompressing an entire stream of data.  (Heck, even I have trouble with it some days.)

Now, this is not truly secure, as there is no authentication or encryption, but you don't have to worry so much about the data being stored 'in the clear'.

The database information, however, IS stored in a format that could be parsed by an advanced-level adversary.  There is a database encryption product (formerly known as "Vormetric") that encrypts data at the filesystem level.

While application security is important, more straightforward methods at other levels (strict firewalls, restricting available network services, hardening the operating system) will work as far more effectiveness against hackers.