[[{“value”:”Key Takeaways: In the face of ransomware attacks, a resilience strategy for IBM i systems must include measures for prevention, detection, and recovery. Built-in security features and enterprise-wide security operations help create a robust defense against ransomware. AI-driven tools are emerging to help you combat these attacks more efficiently and effectively. Ransomware attacks have become … Continued
The post Ransomware Attacks: 3 Keys to Resilience for Your IBM i Systems appeared first on Precisely.”}]] Read More
APG and Northstar-backed Fresche Solutions snaps up Redbourn – PE Hub
Redbourn is a specialist in bespoke development, application support, consultancy and training for IBM Power Server (AS/400). Irien Joseph -. 16 … Read More
Webinar iSecurity for DORA Compliance
Webinar iSecurity for DORA Compliance – Nov 20th 2024 Probably you already have documented security policies in place for GDPR, but these will need to be supplemented and updated for DORA. Raz-Lee’s iSecurity Suite makes it easy to secure your IBM i systems and meet DORA compliance standards. Join our upcoming webinar to learn how Read More
Fresche Solutions Acquires Redbourn Business Systems to Expand IBM i Synon/CA 2E Services in the UK and Europe
Fresche Solutions Acquires Redbourn Business Systems to Expand IBM i Synon/CA 2E Services in the UK and Europe Read More
Learning about active queries [email protected] (Simon Hutchinson)
[[{“value”:”Have you ever wanted to know what is going on within an active SQL Query Engine, SQE, query?
If, like me, you do there is a table function that shows all kinds of interesting information.
The table function ACTIVE_QUERY_INFO has been around since IBM i 7.3 . It has four parameters that allow you to select the results you want returned.
JOB_NAME: This is the parameter I have found the most useful. Rather than it using the qualified job name it uses the job name part of the job name. Therefore I can just search for jobs with wildcards, for example ‘DSP1*’. I can also use ‘*’ to return results for the current job only, and ‘*ALL’, or blank, to return the results for all active jobs.
JOB_USER: The user name from the job name. A wildcard can be used here too.
JOB_NUMBER: The job number part of the job name. ‘*ALL’ can be used here.
USER_NAME: The user name for the job, which may not be the same as the job user name.
Read more »”}]] Read More
